Scope gaps and change orders during design
Key Takeaway
When design uncovers a requirement that needs work outside the statement of work (SOW), first define that change's scope in detail with stakeholders so you can estimate its schedule and cost impact. The change then goes through a change order: the customer submits a written request, and the change is reviewed and approved before the team builds it.
Project scope is all of the work a project must do to deliver its expected outcome. A clear scope states what is included and what is not. During design, a consultant finds gaps between what stakeholders ask for and what is planned. The consultant then decides whether each gap becomes in-scope work, deferred work, or a formal change. A change order process keeps late requests from quietly expanding the project and breaking its budget or timeline.
What project scope is
Project scope defines all of the work needed to deliver a project's expected outcome. Scope comes from the requirements that the sponsor and key stakeholders provide. A good scope says precisely what is and is not included in the project.
Scope planning is a joint effort between the project team and key stakeholders. Together they define, discuss and document the requirements, then reach consensus on them. The requirements must be detailed enough that no one misunderstands what the project will deliver.
Scope is the main input for the schedule and cost estimates. Scope is also used to measure project performance.
Traditional project management defines the entire scope before the project begins. Agile methods define and refine requirements continuously.
Agile projects often start with an MVP and move more complex requirements into later sprints.
A simple way to confirm scope is to draw a box on a whiteboard while stakeholders explain their requirements. Write in-scope items inside the box and out-of-scope items outside it. Anything not inside the box is not in scope. The picture also helps manage expectations during execution.