At the end of the third iteration, the project team gathers to discuss the stories to be implemented in the next iteration. What should the team do during this session?
A.
Develop a user story analysis based on the work done, depicting the current status, S-curve, schedule variance (SV), and planned value (PV).
B.
Run a spike to ensure all information available is correct and then decide which stories to implement.
C.
Bring up all risks for implementing the user stories and discuss possible solutions.
D.
Plan the backlog by estimating and reprioritizing the user stories as new information becomes available.
Why the other options are incorrect:
A. Develop a user story analysis... SV, PV, S-curve:
❌ These are Earned Value Management (EVM) techniques, typically used in predictive (waterfall) methodologies — not in Agile or iterative planning.
B. Run a spike... then decide:
❌ A spike is used when there is a significant unknown or technical uncertainty. It’s not a standard step in every planning session.
C. Bring up all risks and discuss solutions:
❌ While risks can be discussed during planning, the main goal of this session is planning the upcoming iteration — not risk management alone.
D. Plan the backlog by estimating and reprioritizing the user stories as new information becomes available.
Explanation:
At the end of an iteration, a team typically gathers to:
Review the work completed in the iteration.
Inspect the product increment.
Adapt the plan for the next iteration.
This section is not available anymore. Please use the main Exam Page.CAPM 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.
JesseChou_123
1 month, 2 weeks agoVangelis_1980
1 year agoCyberpleb
1 year ago