Stakeholder Analysis in Project Management

Study Notes

Requirements Document

Stakeholder Analysis

Identifies individuals or groups with an interest in the project
Involves understanding their needs, expectations, and levels of influence
Helps to:
- Identify and prioritize requirements
- Ensure that all stakeholders' needs are met
- Build relationships and manage expectations
Steps involved:
1. Identify stakeholders
2. Analyze their interests and expectations
3. Determine their level of influence
4. Develop a stakeholder management plan

Non-Functional Requirements (NFRs)

Describe how the system should behave, rather than what it should do
Also known as "quality attributes" or "constraints"
Examples:
- Performance: response time, throughput, and resource utilization
- Security: authentication, authorization, and access control
- Usability: user experience, accessibility, and user interface
- Scalability: ability to adapt to increased load or growth
NFRs are often conflicting, so trade-offs may be necessary

Functional Requirements

Describe what the system should do
Define the functions and capabilities of the system
Examples:
- User authentication and authorization
- Data storage and retrieval
- Calculation and reporting
- User interface and workflow
Functional requirements are often categorized as:
- User requirements: describe what the user wants to do
- System requirements: describe what the system must do

Use Cases

Describe how users interact with the system to achieve a goal
Identify the primary and secondary actors involved
Define the preconditions, triggers, and postconditions
Use cases are often represented using:
- Use case diagrams (UML)
- Use case descriptions (text-based)
Use cases help to:
- Identify functional requirements
- Develop user interface and workflow designs
- Create test cases and scenarios

Stakeholder Analysis

Identifies and analyzes individuals or groups with an interest in the project to understand their needs, expectations, and levels of influence
Helps to identify and prioritize requirements, ensure needs are met, and build relationships
Involves four steps: identifying stakeholders, analyzing interests and expectations, determining influence levels, and developing a stakeholder management plan

Non-Functional Requirements (NFRs)

Describe how a system should behave, focusing on quality attributes or constraints
Examples include performance, security, usability, and scalability
NFRs often conflict, requiring trade-offs

Functional Requirements

Describe what a system should do, defining its functions and capabilities
Examples include user authentication, data storage, calculation, and reporting
Functional requirements are categorized into user requirements (what users want to do) and system requirements (what the system must do)

Use Cases

Describe how users interact with a system to achieve a goal, identifying primary and secondary actors
Define preconditions, triggers, and postconditions, and are represented using use case diagrams and descriptions
Use cases help identify functional requirements, develop user interface and workflow designs, and create test cases and scenarios

Description

This quiz covers the importance of stakeholder analysis in project management, including identifying individuals or groups with an interest in the project, understanding their needs, and determining their level of influence. Test your knowledge of stakeholder analysis and its role in project success.