Re: Decomposing only minimal work in Sprint Planning
| Newsgroups | gmane.comp.programming.scrum.general |
|---|---|
| Message-ID | <[email protected]> |
Charles, > On Nov 24, 2015, at 2:09 PM, Charles Bradley - Professional Scrum Trainer and Coach [email protected] [SCRUMDEVELOPMENT] <[email protected]> wrote: > > 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? I’ve encountered teams that don’t really decompose at all, instead just talking about how they’ll likely do things. The advantages of decomposing little include: less work; fewer mistakes; less commitment to a plan made at the worst possible moment; more chance for the team to swarm; more emphasis on what’s most important i.e. first. Ron Jeffries ronjeffries.com <http://ronjeffries.com/>Don't ignore your dreams; don't work too much; say what you think; cultivate friendships; be happy. -- Paul Graham