Scope statement.
Describe the boundaries of a project in plain language.
Name the outcome
Use a short intake form to capture the requester, the outcome and the date. Review new entries together before assigning an owner.
Name the outcome: record the project-specific decision, who owns it and what would cause the team to revisit it.
List deliverables
List the outcome, the owner and the next checkpoint. Keep the supporting brief one click away as the work moves forward.
List deliverables: record the project-specific decision, who owns it and what would cause the team to revisit it.
Define how scope changes
Keep the original observation beside the decision it informed. Search a project name to retrieve the supporting notes.
Define how scope changes: record the project-specific decision, who owns it and what would cause the team to revisit it.
More in this collection.
- Iterative planning
- AI product roadmap
- Bug management
- Cross-functional projects
- Engineering project management
- Engineering roadmap
- Engineering workflow
- Project charter
- Technical specifications
- Issue tracking
- Lean product management
- Multiple projects
- Product backlog
- Product launch plan
- Product dashboard
- Product management workflow
- Product specifications
- Project documentation
- Project risks
- Project framework
- Project planning guide
- Project milestones
- Project roadmap
- Project tracking
- Delivery approaches
- Software delivery strategy
- Sprint planning
- Stakeholder mapping