Planning / v1.0 clean-room
Project Product Description
Define the final project output in a way that supports acceptance and avoids scope drift.
When to use
Use during initiation and whenever the expected final product is unclear or contested.
Sample suggested content
Project example: Online booking service
- Product: Public appointment booking service with staff administration view.
- Acceptance: Users can book, change, and cancel appointments without staff intervention.
- Approver: Service Owner after pilot evidence is reviewed.
Minimum version
- Product purpose
- Users or recipients
- Acceptance criteria
- Quality checks
- Owner
Fuller version
- Composition
- Derivation
- Quality method
- Acceptance authority
- Configuration notes
Field guide
- Product name
- Purpose
- Acceptance criteria
- Quality method
- Approver
- Notes
Tailoring notes
- Keep acceptance criteria testable
- Use fuller quality evidence where handover risk is high
Common mistakes
- Describing activities instead of the final product
- Using vague acceptance language