Vladislav Kochelaevs - Fotolia
When two other team members (perhaps a tester and a developer, for example) aren't getting along, how can a project manager handle the situation to keep the project on track?
When there is team conflict, especially when two team members seem like they are continually disagreeing and butting heads, it's usually because they have conflicting priorities. Although everyone on the project team should have the same goal, team members may fundamentally disagree on the best approach to accomplish that goal. In general, getting the project back on track requires the project manager to get the fighting parties to focus on their common ground and move toward a mutually beneficial understanding.
The team's goal should be to complete the project on schedule, within budget and with a high degree of quality. Each team member will generally embrace one element of this triple constraint (time, cost or scope) more than the others. What is most important to each team member usually comes from their respective roles and responsibilities on the project. For example, a developer or business-systems analyst may place a lot of importance on keeping the scope on track, whereas a tester may be more concerned about the quality of the delivery.
When team conflict threatens to steer the project off-course, the project manager needs to analyze the root cause in order to understand what each team member considers most important.
A project manager who takes the time to understand the needs, values and priorities of each team member will understand the root cause of the clash, and he or she will be better equipped to deal with the issue. Then the project manager can meet individually with the team members who are fighting to help them understand each other's point of view. If the conflict is more pervasive among the team members, a team meeting during which each member offers his or her point of view may be a better approach.
In conclusion, in order to avoid refereeing a team conflict, the project manager should seek to understand the root of the conflict and then help each team member see the other's point of view.
Defining project management
Project management lessons learned shouldn't be limited to postmortems
How to deal with workplace conflict
Learn how to select the right ALM software for your organization
Dig Deeper on Building Software Project Teams
Related Q&A from Gerie Owen
A script-based tool has replaced a daily testing exercise on some code. Is it simply an automated test, part of a test automation strategy or even ... Continue Reading
Developers and testers strive to create quality, reusable code to deploy apps faster and keeps users happy. But what metrics should they track to ... Continue Reading
Don't get stuck in QA monotony. Show your technical knowhow and expand your horizons to boost your career -- even if it means throwing out the map. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.