Conflict can easily arise in projects. Project work can lead to workplace conflict.
Project managers are a huge contributor to this because they go out and search for it. We challenge leaders, discuss risk and what could go wrong, and call out poor performance through project control and monitoring.
One could say that we look for trouble.
It’s part and parcel of the job. Conflict is a healthy part in any team’s development. It’s a great way to challenge requirements and ensure your business case and plans are up to scrutiny.
While you should not avoid conflict, it is important to be prepared.
This article will discuss the causes of conflict between team members on projects, how to identify conflict, and resolution strategies to help you all get back to work. You can skip to the videos at the end of each section if you prefer to read instead.
This article:
What is team conflict? Project Management Conflict Examples in Phase 1.
Conflict Examples in the Definition Phase
Conflict Examples in the Development Phase
Conflict Examples in the Handover Phase and Close Phase

What causes conflict in project teams
Identifying Conflict at Work
How do I deal with conflicting priorities?Conflicting priorities happen when:
Focus on no consensus to resolve

Team Conflict Resolution
The Thomas-Kilmann Conflict Mod InstrumentThe Avoiding Conflict Method
The Accommodating Conflict Mode
The Competing Conflict Mode
The Mode of Collaborating in Conflict

The Mode of Compromising Conflict
Understanding Your Role
The Key Takeaways

What is Team Conflict?
This is how I like conflict to be defined:
Conflict occurs when two or more people disagree with each other and one of them (at the very least) decides that it is worth a fight.
Let’s first look at the areas where conflict occurs during the project’s life cycle. Who is involved? You will also find examples of the factors that drive these difficult situations. This will help you be more prepared for any challenges that may arise (because they will). ).
Examples of Conflict Management in Project Management during the Concept Phase
The Concept or Initiation phase is the first. This is the beginning of the project, while you plan what will happen.
This phase is prone to conflict between:
The users and the sponsor, for example, about the requirements or cost or around agreeing on the problem and solution.
The project manager and the sponsor, for example, around the requirements and how they can be achieved.
The portfolio management and sponsor, such as business case approval.

These examples will help you to imagine conflict situations based on your own experiences. These are just my thoughts. There will be many other times in a project when people disagree.
As we said, this is normal and not something to worry about. My experience shows that there are more conflict points at the start of a project. This is partly due to team members trying to figure out their place in the hierarchy and how their contribution will be valued.
Conflict Examples in the Definition Phase
This phase is where the project is fully scoped out and planned. There are workshops, facilitated meetings and backlog grooming sessions. There is also plenty of chat among team members — but not all of it in agreement.
There is a possibility that you will see conflict between:
For example, the project manager and team leader may have a disagreement about planning, roles and responsibilities, or assigning risk ownership to people who don’t believe they are responsible for it.
For example, the sponsor and project manager. After the detailed planning has been completed, there may be a need for sc review.