There are completely different opinions for conducting dash planning. Lengthy debate is going on between velocity pushed dash planning and dedication pushed dash planning. Mike Cohn, founding father of Mountain Goat Software, shared his views in his latest weblog on Why I Prefer Commitment-Driven Sprint Planning.
Mike described each the approaches in his weblog. Velocity-driven dash planning is predicated on the premise that the quantity of labor a crew does in present dash is roughly equal to what they’ve performed in prior sprints.
The steps in velocity-driven dash planning are as follows:
- Decide the crew’s historic common velocity.
- Choose quite a few product backlog objects equal to that velocity.
In commitment-driven dash planning, a crew commits to at least one product backlog merchandise at a time by roughly figuring out and estimating the duties that shall be concerned, and stopping after they really feel the dash is full. As per Mike:
As a result of “dedication” is commonly mistaken as “assure,” this strategy is changing into extra generally known as capacity-based dash planning.
Mike says that there isn’t any must deep dive into all of the duties corresponding to at least one consumer story on the time of planning.
Don’t ask or count on a crew to consider each process that shall be performed through the dash. Not solely is that inconceivable, additionally it is pointless.
Groups ought to consider sufficient of the duties that they really feel they’ve thought via the work—however you will need to notice that pondering via the work is the actual aim of this assembly. Figuring out duties and hours is secondary.
Mike says that he prefers dedication pushed dash planning due to the next causes:
- Velocity is variable so good for long run planning.
- Anchoring, tendency for an estimate to be unduly influenced by earlier data.
In case you are already doing velocity-driven dash planning and it’s working for you, don’t change. Nevertheless, in case your crew is new to Scrum or in case your crew is experiencing among the points, then I like to recommend utilizing commitment-driven dash planning.
Capability pushed planning yields higher outcomes for brand spanking new groups who haven’t run a dash collectively earlier than, as a result of the empirical proof of process estimation is stronger and normally primarily based on one thing everybody within the crew has performed.
Thomas Henson, shared his views on Diqus as:
I might agree along with your evaluation. The bottom line is the tendency for groups to change into in preserving the identical variety of story factors per dash. Dedication-driven permits for the crew to problem themselves. The second level is commitment-driven permits your crew to self handle their workloads, and a key of Scrum is for crew to be self organizing.