Scrum: Sprint Planning: Capacity Driven Versus Velocity Driven Planning
The event crew are the one ones that decide to delivering a dash. There are two frequent strategies used to reach at a dedication. Each of them are guides crew can use to find out how a lot work to tackle.
Capability pushed planning implies that the crew commit on what they will ship in a dash, based mostly on proof of the variety of hours price of duties they suppose they will full. They observe a buffer to account for conferences and downtime. They then complete the variety of hours of sub-tasks within the dash backlog and solely decide to tales until their capability is reached. That is useful for groups that don’t but have a velocity and I’ve seen it work throughout a mission to nice impact.
The hot button is in adjusting the buffer based mostly on retrospective. For instance:
– In a two-week dash there are 9 7.5 hour days (not together with planning day if conferences take all day). That is: 67.5 hours
– If we observe a buffer of 1.5 hours per day (13.5 hours) to account for lunch and conferences. This works out 67.5 – 13.5 = 54 hours a dash for work.
– Subsequently the crew decide to not more than 54 hours of labor in a dash.
The buffer will be expanded or contracted every dash, and you’ll quickly attain a predictable variety of hours which are misplaced to scheduled conferences and different immoveable impediments. That is in fact not fool-proof, however it is extremely shut for my part.
Velocity pushed planning implies that the crew commit on what number of tales they will ship in a dash based mostly on empirical proof of the quantity of story factors they delivered per dash until that time. The variety of story factors per dash known as the common velocity. For instance:
– The crew’s common velocity is 50 factors per dash
– They talk about and suppose that they had been overly formidable earlier than and rushed the job, due to this fact they cut back barely to 45 factors (as a result of they barely delivered the ultimate 5 level story of their final dash).
The primary three to 4 sprints are often wanted to set a dependable velocity, due to this fact whether it is their first dash, they use their intestine feeling as a crew to choose tales.
Which one is greatest?
Each capability pushed and velocity pushed approaches can work, however I’ve discovered that velocity pushed planning tends to depend on intestine feeling extra for the primary few sprints till the crew are in full swing. Capability pushed planning can falsely make groups suppose that the hours estimates are anticipated to be correct (which they don’t seem to be). I might suggest that capability pushed planning yields higher outcomes for brand new groups who haven’t run a dash collectively earlier than, as a result of the empirical proof of activity estimation is stronger and often based mostly on one thing everybody within the crew has achieved. I say this as a result of velocity pushed planning is predicated on story factors, whose relationship to time is much less predictable within the early sprints.
CLICK BELOW FOR A FREE SCRUM EBOOK