Hi Anthony, Thanks a lot for the detailed information. I think my students would love to hear about how OAE dev team manages the development.
Harry On Tue, May 29, 2012 at 9:41 PM, Anthony Whyte <[email protected]> wrote: > Harry--the core team at present is not employing a particular agile > methodology such as scrum to manage our work. Instead we have chosen to > adapt particular agile practices as well as modify others in ways that we > think work well for us as a team. > > Our release cycles are iterative in nature and relatively short in length. > We do plan sprints although for our upcoming release, OAE 1.3.0, we did > not engage in formal sprint planning but instead scoped the release very > tightly for a short time development/release timeline. > > We do not hold daily scrum meetings as we have found the frequency of such > calls both unproductive and a bit disruptive for a team distributed across > three continents. Instead, we hold two 20-25 minute standup calls per week > that mimic the daily scrum meeting (i.e., "what did you do over the last > two days", "what did you plan to do over the next couple of days", "do you > face any impediments?"). Once a week the front-end group (UI-Dev), > back-end group (Server-Dev) and QA group each hold an hour long meeting to > discuss current issues, highlight new work and explore new technologies. > We don't use burndown charts. > > We have no designated "scrum master" tasked with helping eliminate sprint > impediments. Instead, we employ a small set of senior "leads" who work > together in an effort to remove blockers and, when necessary (which is not > often), ensure that individual team members stay focused on the right > tasks. The leads meet a minimum twice a week in order to review/report on > current work, triage tickets and plan upcoming work. > > As for a "Product Owner" the team works in partnership with both the OAE > User Reference Group (URG) and increasingly, the OAE Technical Reference > Group (TRG), groups who in a real sense represent for us "the voice of the > community." > > In sum our practices are hardly pure or conform to the type of "real case" > that you seek. Still, we'd be happy to talk to your students about how we > organize ourselves in order to get work done if you think it would be of > interest to them. > > Cheers, > > Anthony > > > On May 29, 2012, at 12:04 PM, Harry Wang wrote: > > > Hi All, > > > > I hope this is a relevant question for this listing :) > > > > I will teach agile development with scrum at the University of Delaware > in the fall and would like to find a good case study for my students. I > remember Alan Marks implemented agile for OAE a few years ago and I saw a > list of product backlogs, some notes for sprint planning meetings, etc. > (which I cannot find anymore). Is the OAE development team still using > agile methodology? If yes, any pointers to things, such as product > backlogs, sprint planning notes, daily scrum meeting notes, sprint/release > burndown charts? I hope to show my students a real case of agile product > management. Any help is greatly appreciated. > > > > Thanks! > > > > Harry > > _______________________________________________ > > oae-dev mailing list > > [email protected] > > http://collab.sakaiproject.org/mailman/listinfo/oae-dev > >
_______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
