HKSM
Estimate Tasks process
During this process, the Scrum Core Team convenes in a Task Estimation Workshop to determine the effort needed to complete each item in the Task List.
Key Points
- Held as a focused Task Estimation Workshop with the Scrum Core Team.
- Produces effort estimates for every task in the Task List, along with assumptions.
- Common techniques include planning poker, ideal hours, relative sizing, and expert judgment.
- Results help with sprint planning, capacity alignment, and tracking progress.
Example
A Scrum team decomposes a user story into tasks such as design, API changes, UI updates, and tests. In a workshop, they use planning poker to estimate each task in ideal hours (e.g., 6h, 12h, 4h, 8h) and note assumptions like code reuse and available test data.
PMP Example Question
During the Estimate Tasks process, what is the most appropriate primary output?
- An approved product increment
- A prioritized Product Backlog
- A Task List with effort estimates and documented assumptions
- A stakeholder engagement plan
Correct Answer: C — A Task List with effort estimates and documented assumptions
Explanation: The process centers on estimating effort for each task in the Task List, capturing the figures and key assumptions to support planning and tracking.
