PMP · Question #378
During the design phase, a project manager realizes that the project will benefit from using adaptive tools. The effectiveness of this approach has been proven in past projects inside the organization
The correct answer is C. Confirm team capabilities before introducing adaptive tools and artifacts to the project. Before introducing adaptive tools and approaches, the project manager must first confirm the current team's capabilities and readiness to adopt these new methods.
Question
During the design phase, a project manager realizes that the project will benefit from using adaptive tools. The effectiveness of this approach has been proven in past projects inside the organization. What should the project manager do first?
Options
- AUpdate project documents to include adaptive tools and artifacts and plan the first iterative
- BContact the project sponsor and request new team members who are familiar with adaptive
- CConfirm team capabilities before introducing adaptive tools and artifacts to the project
- DFreeze the design stage and look for an external resource to run iterative design at extra cost
How the community answered
(27 responses)- A7% (2)
- B15% (4)
- C74% (20)
- D4% (1)
Why each option
Before introducing adaptive tools and approaches, the project manager must first confirm the current team's capabilities and readiness to adopt these new methods.
Updating project documents and planning the first iteration should come *after* confirming the team's capability to effectively use the adaptive tools and approach.
Immediately requesting new team members without first assessing and trying to develop the existing team's capabilities can be premature and costly, and might not be necessary if the current team can be upskilled.
Before integrating adaptive tools and artifacts into a project, especially if it's a new approach for the team, the project manager must first assess the current team's capabilities, skills, and comfort level with such methodologies. Understanding the team's readiness allows the project manager to plan for necessary training, coaching, or resource adjustments, ensuring a smoother transition and more effective adoption rather than forcing an unready team into new practices.
Freezing the design stage and incurring extra cost for external resources is an extreme and potentially unnecessary step before evaluating the internal team's capacity or training needs.
Concept tested: Team readiness for agile adoption
Source: https://www.pmi.org/learning/library/agile-adoption-strategies-6577
Topics
Community Discussion
4C is correct. Before you roll out adaptive tools you have to confirm the team can actually use them, otherwise you are creating risk instead of reducing it. A is the trap because it jumps straight to updating documents and planning work without validating capability first. The phrase "proven in past projects" tells you the organization has experience, but it does not guarantee your current team has the skills, so always close that gap before committing.
Yeah C is the move, I'd just add that the "proven in past projects" wording is there to make you assume the skills carried over to the current team, which is exactly why it's a trap.
I grabbed A first since the org already proved adaptive works, but then the word "first" jumped out at me. You cant just dump new tools on a team without checking they actually have the skills, so C is the move.
Picked C. Does anyone know if PMI always wants capability check before tool adoption?