Scope worksheet — Season 4 Rollout

Four plain-words lenses on the same answer: what the project's scope statement says the product is. Technique: Product Analysis · PMBOK-6 process 5.3 · read about this technique.

The project as the system, its stakeholders as the actors around it. Technique: Context Diagram · PMBOK-6 process 5.2 · read about this technique.

What a prototype must show before it earns the time to build it. Technique: Prototypes · PMBOK-6 process 5.2 · read about this technique.

• Shows the product's key features well enough for a stakeholder to react to
• Is disposable — cheap enough to throw away and rebuild
• Surfaces requirements a written document alone would not have caught
• Can be walked through with a stakeholder in one sitting

No requirements documentation is filed yet — a prototype built now has nothing written to check itself against.

Fill this table from your own comparison points — add ?against=Name to the address, once per project or organisation you want a column for. Nothing here is saved. Technique: Benchmarking · PMBOK-6 process 5.2 · read about this technique.

A walkthrough of this project's deliverables — its milestones, each with its own status. Technique: Inspection · PMBOK-6 process 5.5 · read about this technique.

1 of 3 milestones met (33%).