Based on the backlog metrics in the chart, what can explain the jump in points at the end of iteration 4?

Question

Exhibit

Options

• AThe team neglected to account for support and maintenance costs associated with other
• BThe team discovered that previously accepted work could be greatly improved and added story
• CThe team realized that some stories were underestimated relative to other stories and re-
• DThe team learned that the product owner needed to increase the output in the next release

• A
  14% (2)
• C
  79% (11)
• D
  7% (1)

Explanation

A sudden jump in total backlog points mid-project is most commonly explained by re-estimation (also called re-sizing or story point recalibration). As the team gains more context and experience with the project, they may realize that previously estimated stories were too small relative to other stories in the backlog - so they re-size them upward to maintain consistency. This inflates the total point count without any new work being discovered. Option A (support/maintenance costs) and D (product owner increasing output demands) don't directly cause re-sizing events. Option B (improving accepted work) would typically generate new stories, not re-estimate existing ones.

No community discussion yet for this question.