Reasons for stakeholder conflicts on IT Projects
- Prioritisation: Stakeholders may have different priorities for the project, and may disagree on which features or requirements should be given the most attention. Say some stakeholders may prefer higher security compared to speed.
- Budget: Stakeholders may have different ideas about how much money should be allocated to the project and may disagree about how to allocate resources. A Chief Finance Officer may have different outlook towards budget allocation viz a viz an end user.
- Timeline: Stakeholders may have different expectations for how long the project will take, and may disagree on the schedule or deadlines. Some stakeholders may not have a realistic estimate on effort and time required for developing new features for a complex software system.
- Scope: Stakeholders may have different ideas about the scope of the project, and may disagree on what features or requirements should be included. Sometimes almost every stakeholder is ready with a list of new features which is expected from the system. Stakeholders may even try to show off their knowledge with their suggestions.
- Quality: Stakeholders may have different expectations for the quality of the final product, and may disagree on the standards or testing processes that should be used. What might be acceptable to some may not be the same for others.
- Risk: Stakeholders may have different opinions on the risks associated with the project, and may disagree on how to mitigate or manage those risks.
- Technical decisions: Stakeholders may have different opinions on the technical decisions of the project, and may disagree on how to approach certain technical challenges. Say a complex configurable design viz a viz simple less complex and less costly design.
- Decision making: Stakeholders may have different opinions on how decisions should be made, and may disagree on who should be making the decisions. Some times a few stake holders may wish to impose their decisions on every one else.
It's important to note that conflicts are normal in any project, and the Product Manager or Product Owner or Scrum Master has the role of helping the team and the stakeholders to understand each other's perspectives and find a resolution that works for everyone.
Understanding stakeholder conflict with an example.
Resolving Stakeholder Conflicts
Product Manager , Product owner, Scrum Master, Client Representatives should proactively communicate with each other to resolve current and potential conflicts.