Skip to content
CAPMEasy

CAPM Practice: Determine how to prepare and execute task management steps

Question 9 of 60 in Determine how to prepare and execute task management steps

Pick an answer below — you'll get the explanation instantly, no signup.

What is the PURPOSE of task decomposition within a sprint?
Show answer & explanation

Correct answer: To break user stories into small, concrete work activities that can be tracked and completed within the sprint

Explanation

Task decomposition breaks user stories into specific activities (code the API endpoint, write unit tests, update documentation, design UI). This enables daily progress tracking, identifies potential issues early, and helps the team understand the full scope of work. Tasks are typically 4-8 hours and can be tracked on the sprint board as they move through workflow states.

**Why not A:** Task decomposition exists to help the team plan and self-organize its own work, not to give the Scrum Master oversight of individual team members. The Scrum Master is a servant leader, not a supervisor monitoring what each person is doing.

**Why not C:** A work breakdown structure is a predictive planning artifact. In adaptive projects, the product backlog and user stories fill that role, and task decomposition is a lightweight, just-in-time activity within the sprint rather than a formal WBS.

**Why not D:** Task estimates are approximate and help the team gauge whether the sprint commitment fits its capacity. They are not meant to predict the exact hours each team member will work, and agile teams avoid using them to manage individual utilization.

Key Concept

This question covers Determine how to prepare and execute task management steps under Determine how to prepare and execute task management steps (Agile Frameworks/Methodologies).

Share:

All 1,500+ CAPM questions are free

Sign up to track your progress, see detailed analytics, and get personalized study recommendations.

Sign Up Free