Tirsvad
b0a7414204
Business Case, Stakeholder Analysis, Project Plan and milestone MIL-001 with review records RC-001 to RC-003, then the Python project: PrettyTable Pokemon table, constants, pytest tests, pyproject.toml, Doxyfile, CI workflow and README. Task: MIL-001#1 Task: MIL-001#2 Task: MIL-001#3 Task: MIL-001#4 Task: MIL-001#5 Task: MIL-001#6 Task: MIL-001#7 Task: MIL-001#8
1.4 KiB
1.4 KiB
Stakeholder Analysis (SA)
Cite in CrossReference only if the instance exists (new-artifact.sh checks this for you):
- BC — Business Case objectives each stakeholder concern traces to (Business Goal Alignment section)
Required sections (after Metadata / Version History)
- Purpose — why the analysis exists and the methodology it follows.
- Stakeholder Summary Table —
ID | Name | Role/Title | Organization | Power Level | Interest Level | Quadrant | Primary Concern (Business Language). Every row fully filled; no unclassified stakeholder. - Power/Interest Classification Rationale — narrative per quadrant, consistent with the table.
- Primary Concerns and FURPS+ Mapping — each concern in business language and mapped to a FURPS+ attribute.
- Communication Requirements — channel, frequency, deliverable type, tied to a project phase or milestone.
- Conflicting Interests and Mitigations — every conflict has a mitigation.
- Traceability Analysis — stakeholder → actor/use case mapping, and
business-goal alignment citing Business Case (
[BC-001]) objectives. - Sign-Off.
Stakeholder IDs (S01, S02, …) are stable: never renumbered or reused.
Every other artifact cites them for RACI, ownership and review assignment
(AGENTS.md rule 3). Add new stakeholders with the next free S<NN>.