HKSM

A collaborative session where the Scrum Team sizes the work to complete one or more tasks for a specific Sprint and estimates the people effort and other resources needed to accomplish those tasks during that Sprint.

Key Points

• Purpose: estimate the effort to complete tasks in a defined Sprint, including staffing effort and supporting resources.
• Participants: the Scrum Team; the Product Owner clarifies scope and acceptance criteria, and the Scrum Master facilititates.
• Approach: decompose work into tasks and use techniques such as Planning Poker, relative sizing, or ideal hours; consider team capacity and constraints.
• Outputs: task-level estimates, identified resource needs, assumptions and risks, and inputs to Sprint Planning and the Sprint forecast.

Example

Before Sprint Planning, the team breaks a user story into tasks (e.g., API endpoint, UI update, unit tests). They estimate each task in hours and note they will need 1 QA tester for a day and access to a staging environment. These estimates help right-size the Sprint backlog to match the team's capacity.

PMP Example Question

An agile team needs to determine the effort and supporting resources required to perform tasks planned for the next Sprint. What should they conduct?

1. Sprint Review
2. Task Estimation Workshop
3. Daily Scrum
4. Release Planning

Correct Answer: B — Task Estimation Workshop

Explanation: A Task Estimation Workshop is used to estimate task effort and resource needs for the upcoming Sprint; the other events serve different purposes.