Monday, July 15, 2013

Two styles of Scope definition in Scrum



In every start of Sprint, we have Sprint Planning meeting. In this meeting each Scrum team member (Pigs as well as Chickens) agree upon stories to be completed in current Sprint. This is an ideal picture.

Do we live in ideal world?

Does we have picture perfect Scrum and Sprint? 

No.

There are at least two different styles of scope definitions.
First one where, day one during sprint planning, scope of whole of sprint is defined and then team race towards a fixed target.



In second approach, during sprint planning meeting, team agrees upon broad scope for sprint and keep on refining the scope with time. 



In my point of view, first approach is derivative of water fall model while second has blend of Kanban.

What do you think?

P.S.: Discussion about details of Burnout chart in second case if for some other time.
 

No comments:

Post a Comment