Writing an ICT project scope that prevents surprises

Most disputes on technology projects trace back to a scope that left room for different interpretations. Writing it well takes a little longer at the start and saves a great deal later.

What a good scope includes

• **Objectives:** what the project must achieve, in business terms.
• **Deliverables:** the systems, equipment, installations and documents to be handed over.
• **Exclusions:** what is explicitly not included — often the most valuable section.
• **Assumptions and dependencies:** what the client provides, such as site access, power, internet or data.
• **Acceptance criteria:** how each deliverable will be tested and accepted.
• **Constraints:** deadlines, working hours, budget and regulations.

Use measurable language

"Fast Wi-Fi in all offices" invites argument. "Coverage in all listed rooms, verified by survey, with every access point cabled and labelled" does not.

Agree how changes are handled

Changes are normal. Define how they are requested, assessed for cost and time, and approved before work proceeds.

Review together

Walk through the scope with everyone involved, including end users, before signing. Questions asked now are cheaper than changes later.

See our ICT project management services.