The starting document.
WHAT TO ESTABLISH BEFORE WORK STARTS
Why the project exists What success looks like What is in scope What is explicitly out of scope Who is accountable What it may cost When it must finish
WHY OUT OF SCOPE MATTERS AS MUCH AS IN SCOPE
Unstated exclusions are assumed to be included.
WHAT SUCCESS LOOKS LIKE SHOULD BE
Measurable, or at least observable.
WHAT VAGUE OBJECTIVES SOUND LIKE
Improving the customer experience.
WHAT SPECIFIC ONES SOUND LIKE
Reducing the time to complete an order from four steps to two.
WHY SPECIFICITY MATTERS
Without it, nobody can say whether the project succeeded.
WHAT TO RECORD ABOUT CONSTRAINTS
Budget Deadline People available Anything that cannot change
WHAT TO RECORD ABOUT ASSUMPTIONS
Anything you are relying on that is not certain.
WHY
If an assumption proves wrong, the plan changes, and the record shows why.
WHAT EXAMPLES OF ASSUMPTIONS LOOK LIKE
That a supplier delivers on time That a person is available That existing systems work as described
WHAT TO PRODUCE
A short document, agreed before work begins.
HOW SHORT
A page or two.
WHY SHORT
Long documents are not read, and unread agreements are not agreements.
WHAT TO DO WITH IT
Have the sponsor approve it, in writing.
