Decomposing only minimal work in Sprint Planning
"Charles Bradley - Professional Scrum Trainer and Coach [email protected] [SCRUMDEVELOPMENT]" <[email protected]>
| Newsgroups | gmane.comp.programming.scrum.general |
|---|---|
| Message-ID | <[email protected]> |
Hello fellow ScrumDev-ers, As I understand it, the Scrum Guide requires that the Scrum Team decompose the work(Sprint Backlog) for at least the first couple of days of the Sprint. I think every Scrum team I've ever encountered goes ahead and attempts to decompose the work for the entire Sprint inside of Sprint Planning (leaving room/flexibility for emergence of course). Have any of you run across real life teams that decompose only the first couple of days worth of work in Sprint Planning? If so, in what contexts did you find this beneficial? Also, what was the team's main reason(s) for doing it this way?------- Charles Bradley Chief Executive Officer Professional Scrum Trainer http://AgileSoftwareTraining.com Agile Software - Training, Consulting, Coaching