HKSM
Sources of conflict
Typical project conflicts arise from schedule pressure, changing priorities, limited resources, unclear reporting lines, disagreements about technical approaches, differences in procedures, personality clashes, and budget or cost concerns.
Key Points
- Conflict is normal in projects and can be healthy if addressed early and respectfully.
- Common triggers include schedules, priorities, resources, reporting hierarchy, technical issues, procedures, personality, and costs.
- Use collaboration and problem solving; focus on interests, clarify roles, and escalate only when needed.
- In agile teams, make work and priorities visible (backlog, WIP limits) to reduce schedule and resource clashes.
Example
An agile team faces conflict when a fixed delivery date compresses schedules, two features compete for scarce test resources, and a database change requires approval through a separate reporting hierarchy. The scrum master facilitates a discussion to re-prioritize the backlog, adjust scope, align on the technical approach, and communicate cost and schedule impacts to stakeholders.
PMP Example Question
According to PMI guidance, which is most commonly the source of conflict in projects?
- Schedules
- Personality differences
- Reporting hierarchy
- Technical issues
Correct Answer: A — Schedules
Explanation: While conflicts can stem from priorities, resources, hierarchy, technical issues, procedures, personality, and costs, schedule pressure is most frequently cited as the primary source.
