STAKEHOLDER ANALYSIS
tasleemat asset PMO-03.05 template --lang en
Deliverable Summary & Governance Boundaries
Lifecycle Phase Alignment
Phase 03: Initiating
Sizing Tier Requirements
Tier 1
Validation Contract
This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.
tasleemat validate PMO-03.05 ./completed_data.json
Template Markdown (Bilingual)
<!-- LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.
Section Instructions:
* **ID:** Unique identifier linking back to the Stakeholder Register (e.g., SH-01).
* **Name or Role:** The name or role of the stakeholder being analyzed.
* **Interest:** The level of interest the stakeholder has in the project outcomes (e.g., High, Medium, Low).
* **Influence:** The level of power or influence the stakeholder has over the project (e.g., High, Medium, Low).
* **Attitude:** The stakeholder's attitude towards the project (e.g., Champion, Positive, Neutral, Negative, Blocker).
-->
<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">STAKEHOLDER ANALYSIS</h1>
| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |
---
## Stakeholder Analysis Entries
<!--
Please populate the table below with the following details:
- **ID:** Unique identifier linking back to the Stakeholder Register (e.g., SH-01).
- **Name or Role:** The name or role of the stakeholder being analyzed.
- **Interest:** The level of interest the stakeholder has in the project outcomes (e.g., High, Medium, Low).
- **Influence:** The level of power or influence the stakeholder has over the project (e.g., High, Medium, Low).
- **Attitude:** The stakeholder's attitude towards the project (e.g., Champion, Positive, Neutral, Negative, Blocker).
-->
| ID | Name or Role | Interest | Influence | Attitude |
| :---: | :--- | :--- | :--- | :--- |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] | [ Add details... ] |
---
### Sign-off and Approvals
| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
| **Change & Communications Lead** | {{Change_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Sponsor** | {{Project_Sponsor_Name}} | _______________________ | [ .... - .... - .... ] |
---
<div align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
<span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
<strong>Template:</strong> STAKEHOLDER ANALYSIS | <strong>Ref:</strong> PMO-03.05 <br>
<i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>
User Guide & Practitioner Instructions
Tasleemat Forms Guide
Project Artifact: Stakeholder Analysis
Document Reference: PMO-03.05
This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Stakeholder Analysis in alignment with the Tasleemat framework.
1. What?
An analytical matrix mapping stakeholder power, interest, and sentiment to formulate targeted engagement approaches.
2. Why?
To identify potential conflicts, build alliances, and focus management attention on high-impact stakeholders.
3. When?
Conducted in the initiating phase and updated whenever stakeholder dynamics or project scopes change.
4. Who?
Performed by the Project Manager with input from the project team and sponsor.
Tailoring Tips
- Focus engagement plans on stakeholders with high power and high interest.
- Re-evaluate attitudes regularly as project changes occur.
Alignment & Dependencies
1. Pre-requisites & Inputs (Upstream Dependencies)
- Mandatory:
- Stakeholder Register (PMO-03.04)
- Project Charter (PMO-03.01)
- Optional / Contextual:
- Organizational Context & Culture Assessments
2. Downstream Dependents
- Mandatory:
- Stakeholder Engagement Plan (PMO-04.10.01)
- Communications Management Plan (PMO-04.07.01)
- Optional / Contextual:
- OCM Strategy & Plan (PMO-04.11.01)
- Training Plan (PMO-04.11.02)
5. How?
To accurately and professionally complete the Stakeholder Analysis, the responsible party
must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):
- ID: Unique identifier linking back to the Stakeholder Register (e.g., SH-01).
- Name or Role: The name or role of the stakeholder being analyzed.
- Interest: The level of interest the stakeholder has in project outcomes (e.g., High, Medium, Low).
- Influence: The level of power or influence the stakeholder has over the project (e.g., High, Medium, Low).
- Attitude: The stakeholder's stance towards the project (e.g., Champion, Positive, Neutral, Negative).
6. Reference Example
A fully completed, gold-standard reference example illustrating this artifact in practice is available:
๐ Completed Example: 03_05_Stakeholder_Analysis_Example.md
LLM Generation Prompt & Agent Instructions
Stakeholder Analysis - Generation Prompt
System Instructions: This document contains instructions for generating the ยซStakeholder Analysisยป. When asked to fill this template, follow the section-by-section instructions below. Refer to
parameters.mdfor project variables.Context and Definition: A technique of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project.
Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Stakeholder Register (PMO-03.04), Project Charter (PMO-03.01) * Optional: Organizational Context & Culture Assessments * Downstream Dependents: * Mandatory: Stakeholder Engagement Plan (PMO-04.10.01), Communications Management Plan (PMO-04.07.01) * Optional: OCM Strategy & Plan (PMO-04.11.01), Training Plan (PMO-04.11.02)
Stakeholder Analysis Entries
ID
Instruction: Unique identifier linking back to the Stakeholder Register (e.g., SH-01).
Generated Value: [ Add details... ]
Name or Role
Instruction: The name or role of the stakeholder being analyzed.
Generated Value: [ Add details... ]
Interest
Instruction: The level of interest the stakeholder has in project outcomes (e.g., High, Medium, Low).
Generated Value: [ Add details... ]
Influence
Instruction: The level of power or influence the stakeholder has over the project (e.g., High, Medium, Low).
Generated Value: [ Add details... ]
Attitude
Instruction: The stakeholder's stance towards the project (e.g., Champion, Positive, Neutral, Negative).
Generated Value: [ Add details... ]
Stakeholder Analysis (Reference Example)
๐ Gold Standard Reference Example: This document illustrates a fully completed, production-grade artifact adhering to the Tasleemat PMO Framework (
PMO-03.05). All company names, project references, and figures are realistic fictional simulations.
Apex Global Solutions
Apex Unified Cloud ERP & Supply Chain Modernization - PRJ-2026-ERP-01
STAKEHOLDER ANALYSIS
Stakeholder Analysis Entries
| ID | Name or Role | Interest | Influence | Attitude |
|---|---|---|---|---|
| INIT-01 | Dr. Muna Al-Ghamdi (Executive VP of Technology & Operations) | Approved and aligned with Apex Global Solutions governance baseline | Approved and aligned with Apex Global Solutions governance baseline | Approved and aligned with Apex Global Solutions governance baseline |
| REQ-02 | Sultan Al-Dossary (VP of Operations) | Approved and aligned with Apex Global Solutions governance baseline | Approved and aligned with Apex Global Solutions governance baseline | Approved and aligned with Apex Global Solutions governance baseline |
| ACT-03 | Nasser Al-Ghamdi (Commercial Client Director) | Approved and aligned with Apex Global Solutions governance baseline | Approved and aligned with Apex Global Solutions governance baseline | Approved and aligned with Apex Global Solutions governance baseline |
Sign-off and Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Project Manager | Faisal Al-Harbi, PMP | [Electronically Signed] | 2026-03-18 |
| Change & Communications Lead | Dr. Sarah Al-Kuwaiti, Prosci CCP | [Electronically Signed] | 2026-03-18 |
| Project Sponsor | Dr. Muna Al-Ghamdi (Executive VP of Technology) | [Electronically Signed] | 2026-03-18 |
| --- |
Generated on: 2026-03-15 10:00 UTC, by Tasleemat
Draft 2020-12 JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://tasleemat.pmo/schemas/completed/PMO-03.05.schema.json",
"title": "Completed STAKEHOLDER ANALYSIS Data Contract",
"description": "Additive structural schema validating completed STAKEHOLDER ANALYSIS artifact data payloads (PMO-03.05).",
"type": "object",
"properties": {
"artifact_id": {
"type": "string",
"const": "PMO-03.05"
},
"metadata": {
"type": "object",
"properties": {
"project_name": {
"type": "string",
"minLength": 1
},
"project_code": {
"type": "string"
},
"date_prepared": {
"type": "string",
"format": "date"
},
"project_manager": {
"type": "string",
"minLength": 1
},
"prepared_by": {
"type": "string",
"minLength": 1
},
"version": {
"type": "string"
},
"status": {
"type": "string",
"enum": [
"draft",
"baselined",
"in_review",
"approved"
]
}
},
"required": [
"project_name",
"date_prepared",
"project_manager",
"prepared_by"
]
},
"stakeholder_analysis_entries": {
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Unique identifier linking back to the Stakeholder Register (e.g., SH-01)."
},
"name_or_role": {
"type": "string",
"minLength": 1,
"description": "The name or role of the stakeholder being analyzed."
},
"interest": {
"type": "string",
"minLength": 1,
"description": "The level of interest the stakeholder has in project outcomes (e.g., High, Medium, Low)."
},
"influence": {
"type": "string",
"minLength": 1,
"description": "The level of power or influence the stakeholder has over the project (e.g., High, Medium, Low)."
},
"attitude": {
"type": "string",
"minLength": 1,
"description": "The stakeholder's stance towards the project (e.g., Champion, Positive, Neutral, Negative)."
}
},
"required": [
"id",
"name_or_role",
"interest",
"influence",
"attitude"
]
}
},
"required": [
"artifact_id",
"metadata",
"stakeholder_analysis_entries"
]
}
๐ Form Field Definitions Dictionary (Legacy Specification)
{
"form_name": "STAKEHOLDER ANALYSIS",
"document_reference": "PMO-03.05",
"_llm_instructions": "Populate the fields of 'STAKEHOLDER ANALYSIS' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-03.05.",
"project_title": "",
"date_prepared": "",
"fields": {
"f01_ID": {
"section": "Stakeholder Analysis Entries",
"label": "ID",
"guidance": "Unique identifier linking back to the Stakeholder Register (e.g., SH-01).",
"value": ""
},
"f02_Name_or_Role": {
"section": "Stakeholder Analysis Entries",
"label": "Name or Role",
"guidance": "The name or role of the stakeholder being analyzed.",
"value": ""
},
"f03_Interest": {
"section": "Stakeholder Analysis Entries",
"label": "Interest",
"guidance": "The level of interest the stakeholder has in project outcomes (e.g., High, Medium, Low).",
"value": ""
},
"f04_Influence": {
"section": "Stakeholder Analysis Entries",
"label": "Influence",
"guidance": "The level of power or influence the stakeholder has over the project (e.g., High, Medium, Low).",
"value": ""
},
"f05_Attitude": {
"section": "Stakeholder Analysis Entries",
"label": "Attitude",
"guidance": "The stakeholder's stance towards the project (e.g., Champion, Positive, Neutral, Negative).",
"value": ""
}
}
}