PMP · Question #961
PMP Question #961: Real Exam Question with Answer & Explanation
The correct answer is C: Revisit the user story of the similar requirement, learn about its story points and velocity, and. To provide a rough estimate for a new requirement similar to a past one, the product owner should refer to the user story of the similar past requirement, including its story points and the team's velocity.
Question
A customer approaches the product owner with a new requirement and asks for a rough estimation to implement it. The outline of the task would be similar to a prior deliverable. What should the product owner do to properly inform the customer?
Options
- AAnalyze the current backlog and the backlog refinement to determine a gap for fulfilling the
- BCheck the work breakdown structure (WBS) and the cost estimation for the similar requirement
- CRevisit the user story of the similar requirement, learn about its story points and velocity, and
- DRefer to the lessons learned register where the experience and effort of former requirements
Explanation
To provide a rough estimate for a new requirement similar to a past one, the product owner should refer to the user story of the similar past requirement, including its story points and the team's velocity.
Common mistakes.
- A. Analyzing the current backlog and refinement primarily helps in prioritizing and understanding current work, not directly in estimating a new, similar requirement based on past effort.
- B. Work Breakdown Structure (WBS) and cost estimations are typically associated with predictive project management and detailed planning, which is not suitable for a "rough estimation" in an agile context when similarity to past work is the key.
- D. The lessons learned register contains valuable insights but does not directly provide the quantitative metrics like story points and velocity needed for a rough estimation of a new task based on a similar past task's effort.
Concept tested. Agile estimation using story points and velocity
Topics
Community Discussion
No community discussion yet for this question.