Download

Writing a project scope statement – MindGenius

Resources›How-To Guides›Project Management
Project management

Writing a project scope statement

A scope statement is the agreement about what's in, what's out, and what done looks like, written before the work, so the project has something to point back to when it starts to drift.

Most projects don't fail on execution. They fail because nobody agreed precisely what the project was before it started, so scope creeps, expectations diverge, and the argument arrives too late. A scope statement is the cheap insurance against that.

What a scope statement settles

  • What's in, the work this project will deliver.
  • What's out, the work it explicitly won't, so "could you just also…" has an answer.
  • What done looks like, the conditions that mean it's finished, agreed up front rather than argued at the end.
Why write it in a map first: a scope statement is the output of thinking, not a form to fill in. Working it through visually, surfacing the edges, the assumptions, the things people quietly disagree on, is exactly the work that should happen before a single task is scheduled.

From map to document

Once the scope is agreed in the map, export it to Word or PDF as the signed-off statement everyone refers back to. The thinking stays in MindGenius; the agreement travels in the format the business already uses.

How MindGenius handles the thinking first