Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
PMI Agile Certified Practitioner · PMI
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Release planning focuses on what can be delivered over a span of multiple iterations, not just a single iteration. Therefore, it must take into account the team’s overall capacity across the entire release timeframe. Agile teams typically have a known velocity, which is the amount of work they can complete per iteration (measured in story points or similar units). To create a realistic and achievable release plan, we multiply this velocity by the number of iterations in the release window, giving us an estimate of the total deliverable work.
A. Individual user story effort: Knowing the effort required for individual user stories helps with backlog prioritization within each iteration, but it doesn't directly determine the overall iteration capacity. B. Team member individual work: Understanding individual team member capacity is helpful for resource allocation and workload balancing within the team, but it doesn't provide the whole picture of the team's collective capacity in an iteration. D. Entire team work: Knowing the total team capacity across all iterations can be helpful for long-term planning, but it's too broad for building the specific iteration-based release plan.
The release is the combination of Sprint(s). Now team will provide high level detail about how much work can be completed in each iteration.