Estimating Work in Scrum
Estimating work is an essential practice in Scrum, helping teams plan and forecast their work effectively. When a Product Owner seeks advice on estimating work, the Scrum Master should provide guidance based on Scrum principles.
Exam Question
A Product Owner wants advice from the Scrum Master about estimating work in Scrum. What guidance should a Scrum Master give? (choose the best answer)
- A. Product Backlog items must be estimated in story points.
- B. Estimates must be in relative units.
- C. Estimates are made by the people doing the work.
- D. Estimates are made by the Product Owner, but are best checked with the Developers.
- E. Scrum forbids estimating.
Correct Answer
C. Estimates are made by the people doing the work.
Explanation
Why C is Correct
C. Estimates are made by the people doing the work:
In Scrum, the responsibility for estimating lies with the Developers who will be doing the work. This approach ensures that estimates are realistic and based on the team’s knowledge and experience. The Developers’ involvement in estimation promotes ownership and accountability for the work they commit to during a Sprint.
Why A, B, D, and E are Incorrect
A. Product Backlog items must be estimated in story points: While story points are a common estimation technique in Scrum, Scrum does not mandate any specific unit of estimation. Teams can choose the method that works best for them, such as story points, hours, or another unit.
B. Estimates must be in relative units: Relative estimation is common in Scrum, but it is not a requirement. The focus should be on the team choosing an estimation method that helps them plan effectively.
D. Estimates are made by the Product Owner, but are best checked with the Developers: The Product Owner is responsible for ordering the Product Backlog but not for estimating the work. Estimates must come from the Developers to ensure accuracy and feasibility.
E. Scrum forbids estimating: Estimating is an integral part of Scrum for planning and forecasting. Scrum encourages estimation to help teams manage their work and set realistic expectations.
Key Points
- Team Ownership: Estimations are more accurate and realistic when made by the Developers who will perform the work.
- Flexibility in Estimation Methods: Scrum allows teams to choose the estimation method that best suits their needs.
Responsibilities in Scrum
- Product Owner: Ensures the Product Backlog is ordered and refined to maximize value and align with the team’s capacity.
- Scrum Master: Facilitates Scrum events, removes impediments, and helps teams adhere to Scrum principles.
- Developers: Estimate the work they will perform, plan, manage, and execute all tasks necessary to deliver a potentially shippable Increment.
Relevance to the PSM I Exam
Understanding who should estimate work and why it’s important is crucial for the PSM I exam. This knowledge emphasizes the principle of team ownership and the practical application of estimation in Scrum.
Conclusion
When advising a Product Owner about estimating work in Scrum, the Scrum Master should emphasize that estimates are made by the people doing the work—the Developers. This approach ensures that estimates are realistic and based on the team’s expertise and experience.
For comprehensive preparation and practice exams, check out PSM I Exam Prep to enhance your understanding and application of Scrum principles.