Guide me how both Team Velocity and Capacity planning simultaneously assist during Sprint planning while I considered 25% buffer in capacity planning only. Shall I consider Team Velocity Range will assist on this situation? Saving Changes...
Darren KosaPlanning & Controls ContractorHampshire, United Kingdom
Hi Gnana,
If I understand you correctly, capacity would be the total hours available in the team, minus 25% to give you your buffer?
Given the choice I would recommend using velocity planning over capacity planning unless your team is brand new. In such cases there might not be the historical data available and it would make sense to initially plan your sprints using team capacity.
However, capacity planning has its limitations - primarily because assumes that all team members are equally skilled and this is never likely to be the case. With velocity planning it’s about your team’s ability to complete, rather than availability to complete, which I think has more value when you are trying to size the work.
Rather than using buffer, have you thought about using user story points? This approach would take uncertainty into account and negate the need to use buffer in the first place.
"A statesman is an easy man, he tells his lies by rote. A journalist invents his lies and rams them down your throat. So stay at home and drink your beer and let the neighbors vote!"
