Prepare a project scope statement

After all that work outlining your idea, it’s time to put it on paper. Your definition work leads to project scope. It defines the project’s scope, what is included, and, equally important, what is not. It’s critical to document the project scope. Otherwise, you’ll get scope creep. That’s not some weirdo who sneaks a peek at your project’s scope. Scope creep occurs when stakeholders ask, “Can you do this?” We forgot to ask. Can you include it? No need to go through your change management process.

Another purpose to document project scope is to remind stakeholders of their initial commitment. If someone responds, “I expected you’d do X, Y, and Z,” you can point them to the scope declaration and show them they’re out. In that case, use change management to add them to the project.

A scope declaration defines the project’s scope. This document contains the project’s aim and objectives, deliverables and success criteria, assumptions, risks, and constraints. Here’s what the hospital scheduling project will cover.

Your scope statement also highlights what the project does not entail. For example, the project doesn’t update the system that assigns personnel to shifts. Scheduling hospital and rehab resident rooms are likewise out of scope. A project’s success depends on controlling scope. Create a scope statement for the hospital scheduling project using the exercise files folder’s template.