Resource published Wed, Jun 22, 2016 at 08:07AM UTC edited Wed, Jun 22, 2016 at 08:07AM UTC
Axia Consultants - 20 Tips for Managing Project Stakeholders Edit Title
To help your project stakeholder management
Stakeholders can make or break a project – particularly in the early stages such as with software selection. Those that support the project can help enormously. But those that wish to block or stop it can easily bring a project to a standstill or kill it off altogether. So it is vital to get stakeholders on your side and manage them well. The stakeholder analysis form can help in this respect. However, as this is such an important topic, here are 20 tips for managing project stakeholders.
• On the stakeholder analysis form – list all individuals and organisations who are interested in (the success or otherwise), impacted by, who have influence or power over your software selection project.
• If in doubt, include them – it’s easier to exclude them later on if they are not key stakeholders, rather than the other way round.
• If you include an organisation as a stakeholder, you will also need to identify the correct individuals within the organisation.
• Work with your project team and collectively brainstorm to identify all stakeholders.
• Once you have a list, group your stakeholders (eg into departments) and identify one key person from each group (who is directly affected and senior enough) to be the link to communicate through to the rest of the group. This could reduce your workload, but only if you are sure that the key person does really represent the views of the other stakeholders they are representing.
Understand your stakeholders
• Initially, to get an idea of how people will react to your project, you could predict each stakeholder’s importance, interest and support. However, this is insufficient. You need to find out precisely each individual stakeholder’s interests, requirements, views and support, which you can really only do by talking to them.
• Create a list of questions to ask - to ensure consistency and to make sure you cover everything.
• Then learn as much as you can about your stakeholders. Talk directly to them. You need to know all about their requirements, their issues with the project, their views and how supportive they are towards the project.
• Meet with the most important / powerful stakeholders first – you are more likely to get their support and resources than leaving them to last.
• Communicate early and frequently, rather than leaving to the later on and infrequently.
• Take care not to raise unrealistic expectations about the project during meetings.
Stakeholder issues with and/or requirements from project
• Carefully document your findings. Amend the stakeholder analysis form accordingly for the levels of importance, interest and support for your project.
• List all stakeholder issues with the project. Note that an individual stakeholder may have many issues and or different levels of support, depending upon the issue eg positive support for the new report they’ve been requesting for the last year, but not for the impact on their departmental processes. Moreover, these may change over time or with a better understanding of the project.
• Similarly list all stakeholder requirements from the project. If the requirements are relevant to the project and within the project scope, treat accordingly and include within the requirements specification.
Attach docs, images, videos, and files by dragging & dropping here, or select files.