RE: Decomposing only minimal work in Sprint Planning

It does depend on what you mean by “decompose”..

I’ve been on a team where we took our stories and decomposed them into parallelizable vertical slices as part of our planning, but we didn’t do any technical decomposition. We had found that doing technical decomposition in planning gave poor results compared to what we got with pairs, so we stopped doing it.

From: [email protected] [mailto:[email protected]]
Sent: Tuesday, November 24, 2015 11:10 AM
To: yahoogroups <[email protected]>
Subject: [SCRUMDEVELOPMENT] Decomposing only minimal work in Sprint Planning


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<http://agilesoftwaretraining.com/>
Agile Software - Training, Consulting, Coaching