Perl: the Markov chain saw | |
PerlMonks |
Re: Thoughts on the Agile Impositionby eyepopslikeamosquito (Archbishop) |
on Dec 11, 2010 at 23:52 UTC ( [id://876650]=note: print w/replies, xml ) | Need Help?? |
Don't try to cram in some half-baked code and hope to catch the problem in staging.Indeed. This should be covered by your Definition of Done. I strongly recommend that your team tape their "Definition of Done" to their Scrum board -- and get buy-in from the Product Owner. Now comes the tricky bit though. In many organizations, the ScrumMaster and the team come under intense pressure to ship from the stakeholders, the product owner and upper management. Do they buckle and distort the meaning of "Definition of Done" to save face, please the stakeholders, and perhaps even save their jobs? Or do they have the integrity to openly admit that they mis-estimated, hit unforeseen problems, and no, they are not done yet -- and that it is not sustainable and not in the company's best interests to keep accumulating Technical Debt like this. Whether that happens or not in practice depends principally on the personal characteristics of the ScrumMaster in my experience. A clueless ScrumMaster won't even know whether the team is being truthful re Definition of Done. Scrum co-founder Ken Schwaber highlighted this "ScrumMaster Problem" in a Google tech talk:
In Section
Meditations
|
|