How sprint "0" it is defined by many people?
- Groom your product backlog to make it usable to plan and estimate
- Create a minimal environment that enables the writing of quality code
- Clean up technical debt carried from the previous releases
- (middle-management trick) Buy-in some time before team is really ready to work on the next release

I am very sure that you were tempted to use sprint "0" (or something similar) at some point of time. Will you make it a norm or just use this an exception to get to a healthy trend? Also, don't forget to check more Rules of Thumb here.
Mr. Agile is explaining Sprint "0" to Amy in the latest discussion in his office.
References
No comments:
Post a Comment