3. Define the scope
The scope is one of the most important documents related to project planning. It’s the document that acts as the “sum of all the parts,” outlining both the overarching project goals and distinct deliverables required to get there.
It’s important because it defines the project for internal and external stakeholders. Internally, your work crews can find an outline to drive their work.
Externally, it creates a boundary between them and your team; defining the scope can keep the project from growing beyond its intended objective, which could lead to burnout, delays, or overspending.
Here are some other items the scope document should include:
- Timeline (which we’ll talk about next) — When the project should be complete
- Project phases/milestones/project dependencies — Progress markers to help identify the end of one phase and the start of another
- Team responsibilities — What each team is responsible for
- Important contacts — Who to contact in case of an emergency; also who to contact for the type of emergency
- A plan for scope changes — How your team will resolve disruptions as they occur