From time to time, project team members are replaced or additional members are added. How can project managers ensure that the new members are on the same page with the other team members? In this article, I will present five questions that I answer with new team members in the onboarding process.
Whenever a new team member is assigned to your team, the individual has questions. Take ownership of the onboarding process and ensure that the key questions are answered up front. Here are five key questions:
1. What is the project about?
Don’t assume that the new member understands the project’s background. Educate them. How? One of the best ways to bring a team member up to speed is to review the project charter with the team member. The project manager can explain the project, problems the project will address, the project goals, the deliverables, the assumptions, the constraints, the stakeholders, and the team members.
2. What is my role?
If one developer is replacing another developer, isn’t the role obvious? I mean all they do is develop software. Right? Not so fast, Superhero.
The project manager should share the roles and responsibilities of the individual as well as of other team members. Ideally, the project manager reviews a RASIC Diagram or a Roles and Responsibilities document. Will the developer be responsible for unit testing or helping develop function test plans? Will the developer have responsibilities to perform integration testing with a third-party data provider?
"Alone we can do so little, together we can do so much." –Helen Keller
3. What is the status of my activities?
Naturally, the new team member needs to know which activities they are responsible for and the status of the activities.
- Which activities have been completed?
- What are the current activities?
- Which of the activities are on the critical path?
4. What are the project’s greatest risks?
Not only should project managers provide the background and context of the project, but wise project managers share the most significant risks with new team members. Why?
The individual may be performing activities that are dependent on other activities that are at risk. If the former developer had been having problems with the project requirements, the new one needs to be aware of the issues. The new team member may be able to reduce the risks dramatically.
5. How can I hit a home run?
Your team members want to make a difference. They want to be successful. Be clear about your expectations and ways to bring extra value to the project. If you present this information in a winsome and inviting manner, most people will respond positively.
Pass the Baton
Allow me to offer some closing tips. If possible, arrange for a transition period where both individuals are on the team. Think of the transition like a passing of the baton from one runner to another. The transition period will vary depending on the size and complexity of the project. In most cases, I shoot for a two to three-week transition.
Schedule a meeting between the person transitioning from the team and the new one. In preparation for the meeting, make copies of the project charter, roles and responsibilities, project schedule, and the top risks from your risk register. During the meeting, review these documents and have the former developer add his/her comments.
Ask the two team members to work together during the transition period. The team members should spend more time together initially and less time over the course of the period. Let both team members know that you are available to help as needed.