Re: Decomposing only minimal work in Sprint Planning

Rather than decomposing I like to make a story map with the whole team,
identify the walking skeleton, and start with that. At some point I will
probably ask the team to throw away the story map and make a new one,
because we will have learned stuff.

Other than that I agree with the sentiment to keep the backlog as small as
possible with just a few days worth of really small, high priority stories.
I think the Lean folks do a good job of explaining why making a “complete”
backlog is wasteful. So, I won’t repeat that here.

On Tue, Nov 24, 2015 at 11:09 AM, Charles Bradley - Professional Scrum
Trainer and Coach [email protected] [SCRUMDEVELOPMENT] <
[email protected]> wrote:

>
>
> 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
>
> 
>