Software project stakeholder case studyThis guide is continued from stakeholder analysis - power interest matrix.
To see how these powerful stakeholder analysis techniques work in practice let’s look at an example based on a Customer Relationship Management (CRM) software implementation project. The software was procured from a 3rd party supplier, but to help illustrate the analysis method I haven’t included all of the project stakeholders, instead I have focused on the stakeholders in the organization that bought the software.
The following stakeholders were identified during stage 1 Stakeholder Definition and their interest areas added to a stakeholder interest map.
- Chief Information Officer(CIO)
- Change Manager
- Project Manager
- Outsourced call-center managers
- Networking & security
- Web standards
- Training Manager
- Legacy systems owners
- Outsourced call-center staff
The software will be implemented in an outsourced call center. It includes an online support site which will be integrated with the organization's corporate website by the developers. The testing team will responsible for UAT and will be drawn from the business and the call-center.
The completed power and interest matrix is shown below.
Example Stakeholder Analysis for a Software Project
Influence lines between stakeholders
If we now consider how the stakeholders can influence each other we find useful intelligence that can help drive the stakeholder engagement strategy. We can do this by adding lines that indicate how certain stakeholders influence other stakeholders. The influence lines for the CRM project are shown below. You will probably notice that they are specific to the organization and personalities involved. Influence lines can clearly never be drawn between roles or ‘reused’ for other projects - there are so many different factors involved.
Influence lines will not only change between projects, but also within projects as different phases in the lifecycle increase the interest and/or power of certain stakeholders.For example the legal department are particularly influential in the matrix below, but may become less so during the build phases on the project once questions around procurement and contracts have been answered.
Stakeholder Analysis with Influence lines
The lines of influence can also identify stakeholders within a particular quadrant that need special attention. Legal fall within the high power/low interest square so at a base level the project simply needs to meet their needs. However, they influence finance who in turn influence the CIO this means that they have the ear of the most powerful Key Player and could stop or significantly delay the project. Legal don't have a political interest so the project manager needs to be proactive in identifying when Legal need to be involved and engaging with them.
The call center agents are outsourced so they have little choice in the software procurement or configuration. Their power and interest is low, but they can influence their managers who can in turn influence the change manager who is a key player. Trouble from this influence chain is not likely to impact the project until the software is live, but it could seriously damage the perceptions of project success and ultimately lead to the software being replaced.
This example shows how the influence lines add depth to the analysis which enable us to pick up subtle relationships and understand complexities that can be fed into your Stakeholder Engagement Strategy, project planning andrisk management.
Download this Example Stakeholder Analysis
zip file download with PowerPoint version .ppt .pptx
zip file download with PDF version
Stakeholder Analysis Resources
- Stakeholder analysis templates in Word, Visio and Excel.
- Basic Stakeholder Analysis Method
- BPM Stakeholder Analysis
- Career Stakeholder Analysis
- Stakeholder Analysis - keeping stakeholders happy
- Stakeholder Analysis Keyplayers
- Stakeholder Analysis Questions
- Stakeholder Salience
- Stakeholder Analysis Software
- Stakeholder Analysis Video