Scrum Pattern: Requirement estimation

 
Deutsche Übersetzung

  
ContextProduct Backlog Items including acceptance criteria are available for estimation.
ProblemEstimating requirements based on effort is incomplete and complex.

Traditional estimates of project work packages focus solely on mandays and if the project is managed with mature processes, risk is dealt with in a risk register. Complexity of work packages is usually ignored and managing two or three of these dimensions separately leads to continuous rework of the project management plan.

Forcestoo little/too much effort is spent on estimation
too little/too many experts estimate requirements
SolutionCreate quick estimates including risk and complexity based on the Delphi technique.

Estimates based on effort, risk and complexity are usually calculated in Story Points or Estimation Points. Using Planning Poker or the Team Estimation Game with Fibonacci numbers as Estimation Point classes provides for quick estimates while ensuring independent results by each expert.

Resulting ContextProduct Backlog Item estimates allow the planning of Sprints.

Comments are closed.