PMP · Question #1383
A project manager brings in a new team member from an agile environment to work in a predictive environment. The project manager expects to leverage the new team member's agile experience with the exi
The correct answer is A. Set expectations with the new team member and explain what is needed.. To effectively integrate a new team member with agile experience into a predictive environment, the project manager must first clearly set expectations regarding the project's needs. This clarifies their role and how their agile skills can be adapted or utilized within the existi
Question
Options
- ASet expectations with the new team member and explain what is needed.
- BAcknowledge that hiring this new employee is a risk to the existing team.
- CTrain the new team member in the predictive project management approach.
- DMeet with all team members and explain the new employee's position.
How the community answered
(31 responses)- A74% (23)
- B3% (1)
- C16% (5)
- D6% (2)
Why each option
To effectively integrate a new team member with agile experience into a predictive environment, the project manager must first clearly set expectations regarding the project's needs. This clarifies their role and how their agile skills can be adapted or utilized within the existing framework.
When integrating a team member from a different methodological background, setting clear expectations is paramount for successful adaptation and effective contribution. This involves explaining the project's predictive nature, the new team member's specific responsibilities, and how their agile experience can be leveraged within the existing team and project structure, preventing potential misunderstandings.
Acknowledging the new hire as a risk without proactive management fosters a negative perception and does not aid in effective integration.
Concept tested: Team integration, expectation setting
Topics
Community Discussion
4A is the answer here. My senior PM always says the first thing you do when someone comes in from a different methodology is set clear expectations up front so they know exactly what is needed of them in the new environment.
A is the move here because direct expectation-setting is always the first integration step, before training or team meetings. I remember my PMP sitting last spring, saw this almost word-for-word, and used my EASE hook: Expectations first, Assess later, Support always, Educate as needed. C is the trap because you think a predictive newbie needs a crash course, but the PM wants to leverage that agile background, not erase it. D sounds collaborative but you do not call a full-team meeting before you have even aligned the new person on what success looks like.
B is the right call here. PMBOK Guide section on risk management is clear that staffing changes and team integration issues should be documented as risks, and bringing someone from agile into predictive creates real adaptation friction that the PM needs to acknowledge and plan for rather than gloss over.
Actually it is A, because the question is asking what the PM should do first, and updating the risk register is the immediate action before you start planning mitigation for the adaptation friction. One of the senior PMs at my company drilled this into me: if a new risk surfaces, documenting it comes before everything else. Hiroshi, do you think the exam is testing whether we know the sequence here rather than whether the risk is real?