PMP · Question #1316
A project manager has been managing an agile project for 6 months. Over the last two iterations, the team velocity has decreased due to a new technology that was needed for the product. What should th
The correct answer is C. Use retrospectives to better understand the new technology's impact on the schedule, map the. To address decreased velocity in an agile project caused by a new technology, the project manager should use retrospectives to understand the impact and identify process improvements.
Question
A project manager has been managing an agile project for 6 months. Over the last two iterations, the team velocity has decreased due to a new technology that was needed for the product. What should the project manager do to continue with the delivery plan and return to the expected velocity?
Options
- ASeek sponsor approval for additional funding to hire new team members, increasing the capacity
- BReplace poorly performing team members with more experienced members, setting an example
- CUse retrospectives to better understand the new technology's impact on the schedule, map the
- DReevaluate the backlog by looking for high-value/low-effort items, and negotiate a new minimum
How the community answered
(15 responses)- A7% (1)
- B20% (3)
- C60% (9)
- D13% (2)
Why each option
To address decreased velocity in an agile project caused by a new technology, the project manager should use retrospectives to understand the impact and identify process improvements.
Seeking additional funding for new team members might increase capacity, but it doesn't address the underlying challenge of working with the new technology and can disrupt team dynamics without first understanding the root cause.
Replacing team members is a drastic measure that should only be considered after attempting to resolve performance issues through coaching, training, or process improvements, and it does not address the new technology challenge directly.
In an agile project, a decrease in velocity, especially due to a new technology, is a prime candidate for discussion in a retrospective meeting. The team can collaboratively analyze the challenges presented by the new technology, understand its impact on their workflow and estimates, and identify actionable process improvements or training needs to improve efficiency and gradually return to the expected velocity. This aligns with the agile principle of continuous inspection and adaptation.
Reevaluating the backlog for high-value/low-effort items and negotiating a new MVP is a reaction to the decreased velocity, but it doesn't solve the core issue of the team struggling with the new technology which caused the velocity drop in the first place.
Concept tested: Agile velocity management and retrospectives
Source: https://www.scrum.org/resources/what-is-a-retrospective
Topics
Community Discussion
No community discussion yet for this question.