An agile team identifies that their velocity is lower than predicted, and that their previous forecasts in the product roadmap are wrong. The team is worried that they will be unable to meet a…

Question

Options

• ACollaborate with the product owner to reprioritize the product backlog, thus ensuring that more
• BAsk the team lead to calculate the team's target velocity according to the project plan, and assign
• CFocus on velocity and schedule concerns during the retrospective to inspect, adapt, and improve
• DReestimate the backlog items from the release, ensuring that contingency is included to set

• A
  3% (1)
• B
  6% (2)
• C
  80% (28)
• D
  11% (4)

Explanation

In Scrum and agile frameworks, the retrospective is the dedicated ceremony for the team to inspect their own process and adapt. When velocity is lower than expected, the team must use the retrospective to analyze the root causes (e.g., estimation errors, impediments, skill gaps) and agree on corrective actions. Option A is partly relevant but backlog reprioritization is the product owner's responsibility and doesn't address process improvement. Option B violates agile's self-organizing team principle by assigning work top-down based on a calculated 'target velocity.' Option D masks the problem by inflating estimates rather than fixing the underlying process issue.

No community discussion yet for this question.