nerdexam
PMI

CAPM · Question #288

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?

The correct answer is D. Plan the backlog by estimating and reprioritizing the user stories as new information becomes available. The session at the end of an iteration where the team plans the next iteration is sprint planning, and its core activity is reviewing, estimating, and reprioritizing backlog stories based on updated knowledge. This is a fundamental agile ceremony.

Agile Frameworks/Methodologies

Question

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?

Options

  • ADevelop a user story analysis based on the work done, depicting the current status, S-curve, schedule variance (SV), and planned value (PV).
  • BRun a spike to ensure all information available is correct and then decide which stories to implement.
  • CBring up all risks for implementing the user stories and discuss possible solutions.
  • DPlan the backlog by estimating and reprioritizing the user stories as new information becomes available.

How the community answered

(43 responses)
  • A
    14% (6)
  • B
    2% (1)
  • C
    5% (2)
  • D
    79% (34)

Why each option

The session at the end of an iteration where the team plans the next iteration is sprint planning, and its core activity is reviewing, estimating, and reprioritizing backlog stories based on updated knowledge. This is a fundamental agile ceremony.

ADevelop a user story analysis based on the work done, depicting the current status, S-curve, schedule variance (SV), and planned value (PV).

S-curves, SV, and PV are earned value metrics used in predictive project management, not in agile iteration planning sessions.

BRun a spike to ensure all information available is correct and then decide which stories to implement.

Spikes are time-boxed research tasks used to resolve uncertainty about a specific story, not a standard step in every iteration planning session.

CBring up all risks for implementing the user stories and discuss possible solutions.

Discussing risks for user stories is not the primary purpose of iteration planning; risk discussions occur in retrospectives or separately.

DPlan the backlog by estimating and reprioritizing the user stories as new information becomes available.Correct

Sprint or iteration planning requires the team to pull items from the product backlog, re-estimate them based on velocity and newly available information, and reprioritize to maximize value delivered in the next iteration. Backlogs are dynamic documents that evolve as the team learns, so reprioritization at each planning session is expected. This directly reflects agile principles of responding to change over following a fixed plan.

Concept tested: Agile iteration planning and backlog reprioritization

Source: https://www.pmi.org/pmbok-guide-standards/agile-practice-guide

Topics

#Agile planning#Backlog refinement#Iteration planning#User story estimation

Community Discussion

No community discussion yet for this question.

Full CAPM Practice