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.
A = correct (in my opinion).
Why? The first step to planning releases is to prioritize the user stories. Iterations are single units of work, within the release plan. So it is not enough to know just the amount of work that can be accomplished in an iteration.
- Iteration planning focuses on the work in an iteration (it is a plan intended internally, for the development team). Iteration planning creates sprint tasks that teams must complete
- Release planning prioritizes managing the product release from an iteration sequence. The release planning focuses on the final results and the user stories for product completion.
The release is focused on user stories vs. The iteration is focused on tasks, which are decomposed from user stores (meaning if you want to plan a release, first you need a user story, then the team will decompose it into tasks, based on, the team can plan the iterations within that release).
The release consists of 2-4 iterations.
This section is not available anymore. Please use the main Exam Page.PMI-ACP Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
025eaf4
3 weeks, 3 days agochlaithem
1 year agoitsmewajid
1 year, 2 months agoMattAnya
1 year, 3 months agoImrangoshi
1 year, 5 months agoAKB968
1 year, 9 months agoMinhha3
1 year, 10 months agoPetrevski
1 year, 10 months agoPetrevski
1 year, 10 months agoInvisibleBeing
2 years ago