Tirsvad
1d35410b8d
Create the Business Case, Stakeholder Analysis (S01 course participant, S02 Udemy coursists, S03 GitHub viewers), Project Plan and the milestone documents MIL-001 (project setup, 6 tasks) and MIL-002 (game implementation, 8 tasks) for the console Blackjack game. Register PP and MIL in the artifact registry, set the PO language to en, and link the synced Gitea milestones in the Gateway Schedule. Refs #1 Refs #2 Refs #3 Refs #4 Refs #5 Refs #6 Refs #7 Refs #8 Refs #9 Refs #10 Refs #11 Refs #12 Refs #13 Refs #14
2.3 KiB
2.3 KiB
Business Case (BC)
Cite in CrossReference only if the instance exists (new-artifact.sh checks this for you):
- SA — Stakeholders section — cite S-IDs instead of re-describing roles
- BMC — Cost–Benefit Assessment must agree with its cost/revenue blocks
- BPMN — Forward: the process that realizes the objectives
- KPI — Success Criteria — each criterion is operationalized by a KPI
- UCD — Forward: scope expressed as actors and goals
Required sections (after Metadata / Version History)
In this order:
- Executive Summary — one paragraph framing the problem and the proposed solution.
- Methodological and Standards Foundation — states the methodology (e.g. Larman's Applying UML and Patterns) and quality standards (e.g. ISO/IEC 25002/25010/25019) the rest of the document and downstream artifacts are built on.
- Problem Statement — the recurring problems that justify the project.
- Business Opportunity — what becomes possible if the problem is solved.
- Objectives — concrete, verifiable statements of what the project will achieve.
- Scope — split into
## In Scopeand## Out of Scopesubsections. - Expected Benefits — split into
### Tangible Benefitsand### Intangible Benefits. - Strategic Alignment — how the project supports organizational goals.
- Success Criteria — a table with explicit, measurable targets (not aspirations).
- Risks — a table with
Risk | Impact | Mitigationcolumns; every risk must have a mitigation. - Assumptions — bullet list, kept distinct from Constraints.
- Constraints — bullet list, kept distinct from Assumptions.
- Cost–Benefit Assessment — a table (
Costs | Benefits); may be qualitative if explicitly justified. - Stakeholders — a table referencing exact stakeholder IDs from the
project's Stakeholder Analysis (e.g.
S01,S07) ifSAexists per the CrossReference check above. Never re-describe stakeholder roles inline instead of citing their IDs — this is the single most common defect found when reviewing Business Cases (seeQC-BC-001's Common Defects). - Recommendation — a single, unambiguous "proceed" or "do not proceed" statement.