| 1 |
Power/Interest grid is filled for every stakeholder, with no gaps or unclassified entries |
Pass |
S01 to S03 each have power, interest and quadrant. |
| 2 |
Each stakeholder is assigned a unique, stable ID (e.g. S01-S11 style) reusable for RACI assignments in other artifacts |
Pass |
IDs S01 to S03 are used by every other document. |
| 3 |
Roles and organizational context are defined with explicit Power and Interest levels, not just narrative description |
Pass |
Levels are stated as High/Low in the table, with organisation and role. |
| 4 |
Communication needs (channel, frequency, deliverable type) are mapped to project phases or milestones |
Pass |
Communication table maps each stakeholder to MIL-001 to MIL-003. |
| 5 |
Conflicting stakeholder interests are identified with documented mitigation or resolution strategies |
Pass |
One conflict (assignment names vs testable structure) with a mitigation. |
| 6 |
Stakeholder concerns are explicitly traced to Business Case objectives |
Pass |
Traceability table maps each stakeholder to [BC-001] objectives. |
| 7 |
Primary concerns are expressed in both business language and a recognized quality-attribute mapping (e.g. FURPS+) |
Pass |
Each concern has a FURPS+ attribute. |
| 8 |
Document is understandable and navigable by non-technical stakeholders reviewing their own entry |
Pass |
Plain language, short; each stakeholder can find their own row. |
