PMP · Question #476
The project manager started a new project and must ensure that the team members and stakeholders are adequately trained. After an interview with the team, the project manager discovers that all resour
The correct answer is C. Ensure the team has a common understanding of agile. Despite diverse agile experience among team members, the project manager must ensure a common understanding of the specific agile approach adopted for the current project to ensure consistency and efficiency.
Question
The project manager started a new project and must ensure that the team members and stakeholders are adequately trained. After an interview with the team, the project manager discovers that all resources have experience in different agile methodologies. What should the project manager do?
Options
- AMake sure the project team is aware of all agile techniques
- BSkip the training because the team already understands agile
- CEnsure the team has a common understanding of agile
- DTeach one agile methodology fully and completely
How the community answered
(28 responses)- A4% (1)
- B14% (4)
- C75% (21)
- D7% (2)
Why each option
Despite diverse agile experience among team members, the project manager must ensure a common understanding of the specific agile approach adopted for the current project to ensure consistency and efficiency.
Making the team aware of *all* agile techniques is unnecessary and overwhelming, as only specific techniques will be relevant to the project.
While team members having experience in different agile methodologies is valuable, it does not guarantee a unified approach or common understanding for the specific agile framework, practices, and tools adopted for the current project. The project manager must ensure all team members and stakeholders share a consistent understanding to prevent confusion, promote efficient collaboration, and ensure everyone works towards common goals with consistent methods.
Concept tested: Establishing common agile understanding for project teams
Source: https://www.scrum.org/resources/what-is-scrum
Topics
Community Discussion
8C is the winner. Think "C for Common" because when everyone brings different agile flavors to the table, your job is to blend them into one shared understanding so the team does not talk past each other.
I first leaned toward A because it seemed thorough, but the key word is "different" agile methodologies. The PMBOK emphasis is on alignment, so C is correct because the team needs a shared understanding rather than awareness of every technique.
Failed this one on my first attempt and C is right but the trap is thinking "different methodologies" means you need to study all of them, when really it is about getting everyone speaking the same language regardless of which framework you land on.
C is correct, confirmed on my pass last week. I actually picked B on my first attempt and it cost me because even though everyone knows agile, they know different flavors. The key trap here is that experience in various methodologies means the team needs a shared baseline to collaborate effectively. You want alignment, not assumption.
Saw this one on my PMP last spring, C is the move. Everyone came in with different agile backgrounds on my exam day so the key was getting everyone on the same page rather than skipping training or forcing a single framework.
Spot on, and I would add that in practice getting people aligned is a recurring activity, not a one-time kickoff, because agile comfort levels shift once the team actually starts hitting real delivery pressure.
Going with B here. In the real world, if you have experienced people coming off different agile projects you don't burn schedule and budget on redundant training, you just get them aligned on how this particular project will run during kickoff.
Samuel, I picked B on my first attempt too and it cost me, the answer is C. The question is testing whether you recognize that team members coming from different agile environments likely have inconsistent practices and terminology, so formal training gets everyone to a shared baseline rather than risking misalignment disguised as agreement during kickoff.