Join Terri Wagner for an in-depth discussion in this video Conducting our stakeholder analysis, part of Project Management Foundations: Requirements.
- I have another course in the lynda.com library that is devoted entirely to managing your project stakeholders. So I'll keep this brief and let you explore the other course for more information. Once you've identified all your project stakeholders you'll want to analyze your stakeholders to figure our who you need to engage in order to gather your requirements. Some stakeholders will have more power and influence over your final requirements than others. So doing some analysis on your stakeholder group early on will be critical to your success.
See the lynda.com course on managing project stakeholders to learn more details about this technique. Let's explore a couple of additional stakeholder-classification techniques including level of interaction with the project outcome, job title or function, users of the project product, service or result, and stakeholder role in the organization. A sample organizational stakeholder-classification matrix for an IT project might look like this.
Then this process could be repeated with individual stakeholders within each of those organizational groups. A business analyst often has specialized training in the requirements management piece of a project. Sometimes they have different tools and techniques than someone from a pure project management background. For example, they may create stakeholder profiles and personas. A stakeholder profile is a free-form description of user attributes as deemed relevant by the analyst for each user group.
A user persona is an instance of a profile describing one ore more mythical users for each user group. You write a persona when you want to understand your customer better. It's a story you tell about a typical but not real customer. We'll share a persona of a bank customer and their interaction with an automatic teller machine later in the course. Profiles and personas are based on information gathered during requirements elicitation. On many projects it's common to develop personas and refer to them when making trade-off decisions.
A persona will take representative classes and categories of users and create an abstraction of their characteristic, the user persona. Key user personas are selected and elaborated defining business and user goals within the scope of our efforts. General features that aid the users in achieving their goals. Typical situations or scenarios the users find themselves in as they try to achieve their goals. And behaviors, the way users interact with the features to solve problems, thus describing a persona's behavior.
There is a persona data worksheet in the exercise file for you to view. Do you build personas when analyzing your stakeholders?
Lynda.com is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- Classifying requirements
- Developing requirements
- Investigating requirements
- Documenting requirements
- Validating requirements
- Managing changing requirements