Scope and exclusions

Scope is the line around the work: what's in, what's out, roughly when, and who can move the line. Write it before you build, so a request that turns up later has somewhere to go.

This redesign is speculative, so its scope is small. One homepage concept, at desktop and phone width. AllWeb's own photos and published facts. And a review link, kept out of search.

Out of scope matters more. Name everything someone might assume is included. Ticket sales aren't: the ticket buttons are demos. One search counts eighteen demo links on the page, and the sign-up form says nothing was sent. Analytics, the other fifteen planned pages, a new logo and an Albanian version are out too. The brief already said what it wouldn't do, so the scope just carries it over.

Then rough milestones, with dates you can show. The audit and the brief are dated the fifth of October. An outside audit ran on the seventh. The event is on the sixth of November, and after that the concept's dates go stale. Last, who decides. On a speculative project, you do. For a real launch it's the client, and nothing moves from out to in without their yes.

Write what's in, name everything that's out, give the milestones you can show, and say who can move the line.