Stakeholder Management
Stakeholder Analysis
Communications Plan
Stakeholders are all of those who have an interest (stake) in the project
I.e., they will be affected in some way by it
As a result, they will have an interest in influencing it
In software development, stakeholders can be:
→ The organization behind it
→ Clients (Customers)
→ Developers working directly or indirectly on it
→ System Administrators
→ People who will use it
→ People affected by it
Internal
→ Top management
→ Developers
→ Direct managers
→ System admins
External
→ Clients (customers, users)
→ Government (regulatory)
→ Contractors and suppliers
→ Anyone affected
Stakeholder influence is often greatest at early stages
This normally drops during the middle stages...
... and increases again during the final stages
Note: Agile methods try to maintain engagement throuhgout the project
First, it is important to identify all stakeholders
Then, you need to classify them according to two dimensions:
→ Their level of power to influence the project
→ Their level of interest in the project
This classification can be captured in a stakeholder analysis matrix
After classification, you must develop stakeholder management strategies
Strategies are developed based on:
→ Their spot in the stakeholder analysis matrix (e.g. high-power and high-motivated)
→ Their attitude towards the project: positive or negative
High Power and High Interest
Positive Attitude:
→ Keep them informed and involved
→ Meet often and consult about changes
→ Encourage their participation
High Power and High Interest
Negative Attitude:
→ Attempt to gain their support and confidence
→ Find out what they need/want
→ Counter their negative influence on others
→ More strategies here
A communication plan allows you to set expectations and standards
It defines how and when information is communicated
It also defines who receives which updates
Note that in Scrum, this is part of a Working Agreement
A list of items to be communicated
The person responsible (owner) for communicating the item
Names of all stakeholders involved (target audience)
A schedule or frequency of updates
The preferred communications channel
Project Plan Details
Confidential or sensitive details
Unclear or unrealistic expectations
Note that your communications plan is deeply tied to your stakeholder analysis
It should address the stakeholder management strategies
| Information | Owner | Audience | Schedule | Channel | |----------|:-------------|:------| :-------| :-------| | Project Status | Project Manager | Team members, QA Leader, and clients | Biweekly | In Person | | QA Status | QA Leader | Team members and Project Manager | Weekly | MS Teams | | System Status | Sysadmin| Team members and QA Leader | Monthly | Email | | Financial Report | Project Sponsor | Project Manager | Monthly | Phone |
Communications Plan (until "Improve team communication from start to finish...")