Vision Workspace¶
Purpose¶
Start here by making the business case explicit. Do not write requirements until the problem, desired future state, stakeholders, boundaries, assumptions, and success measures are credible.
This directory should contain the project’s actual working artifacts for this lifecycle area. The links below intentionally point to the Template Library and, where available, the completed LMU/COICP example. Create the real project files in this directory when the project is ready to populate them.
What belongs here¶
| Artifact | Project File Name | Template | Completed Example |
|---|---|---|---|
| Problem Statement | problem_statement.md |
Template | Completed example |
| Vision Statement | vision_statement.md |
Template | Completed example |
| Stakeholders | stakeholders.md |
Template | Completed example |
| Scope | scope.md |
Template | Completed example |
| Assumptions | assumptions.md |
Template | Completed example |
| Success Metrics | success_metrics.md |
Template | Completed example |
| Vision Readiness Summary | vision_readiness_summary.md |
Template | Completed example |
Start from templates¶
Problem Statement
Open the reusable template for problem_statement.md.
Vision Statement
Open the reusable template for vision_statement.md.
Stakeholders
Open the reusable template for stakeholders.md.
Scope
Open the reusable template for scope.md.
Assumptions
Open the reusable template for assumptions.md.
Success Metrics
Open the reusable template for success_metrics.md.
Vision Readiness Summary
Open the reusable template for vision_readiness_summary.md.
Working pattern¶
- Open the relevant template.
- Create the same-named file in
docs/project-workspace/vision/. - Replace template guidance with project-specific evidence.
- Compare the result with the LMU/COICP example when available.
- Record open risks, assumptions, and unresolved questions.
- Finish with the review or readiness artifact for this stage.
Evidence quality bar¶
| Quality | What It Means |
|---|---|
| Specific | Names actual project facts, stakeholders, systems, scenarios, risks, and decisions. |
| Traceable | Connects back to earlier stages and forward to later stages. |
| Reviewable | Gives another reviewer enough evidence to challenge or approve the work. |
| Current | Reflects the project’s actual state rather than old intent. |
| Governable | Makes AI use, exceptions, risks, release posture, and limitations visible. |
Create project artifacts here. Learn the artifact structure from the Template Library. Learn the completed pattern from the LMU/COICP example.