Something that i know some larger teams do after a release (they have long release cycles) is an iteration 0, were they work on improving their processes and pay off technical debt.
On Wed, Dec 22, 2010 at 8:16 AM, Bobby Johnson <[email protected]>wrote: > I agree with Ade. Quality is not something you ensure at the end of the > process in an agile team. That is a waterfall mindset. Quality is something > you have to strive for throughout the development effort. > > Having a productive retrospective is a great starting place, but there are > some caveats: > > 1. The team needs to be empowered to make change. > 2. The team needs to make commitments to implement changes that are > identified and agreed on by the team. > 3. Management has to support the teams effort to improve quality possibly > at the sacrifice of new feature velocity. > > Also trying to parse practices into "real life" and "the ideal" is giving > up before you even try. What I hear in this sentiment is, "I will pay lip > service to Agile practices, but when the rubber meets the road I will > abandon the practices and pump out whatever crap gets me over the immediate > goal line." > > And Hi, Anne! Good to see you posting on the mailing list. Hope things are > going well down in Olympia. > > Bobby > > Trying to parse things into "real life" > > > On Wed, Dec 22, 2010 at 7:39 AM, Anne Wax <[email protected]> wrote: > >> What do you do at the end of a sprint or a release cycle to ensure >> quality? >> >> We've seen some blogs that talk about stop-reflect-adapt and >> review-reflect-repeat. What do you all do when you have completed an >> interation or a release cycle to ensure your product's excellence? Do you >> step back to review and improve before moving on to the next cycle or >> project? >> >> What happens in "real life" and what is the ideal? >> >> Thank you, >> >> Anne >> >> >> >> >> http://www.agileweboperations.com/stop-reflect-adapt-the-3-steps-to-stop-writing-bad-code >> >> >> >> >> http://www.agilejournal.com/blogs/blogs/all-about-agile/704-how-to-implement-scrum-in-10-easy-steps-step-10-review-reflect-repeat >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Seattle area Alt.Net" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<altnetseattle%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/altnetseattle?hl=en. >> > > > > -- > "The explanation requiring the fewest assumptions is most likely to be > correct." > > - Occam’s Razor > http://en.wikipedia.org/wiki/Occam's_Razor<http://en.wikipedia.org/wiki/Occam%27s_Razor> > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<altnetseattle%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
