Managing scope

Managing work scope addresses the what of your project or work. For example, what will be the outcomes of the project? Or what will the system look like that you’re developing? One symptom of possible trouble is scope creep. This happens when additional requirements, functionality, or capability are added to your team’s effort or project.

Do any of these questions sound familiar? Are you asking yourself this question now? Select a question to see guidance and recommendations.

  • How do I define and document scope?

  • How do I negotiate adding scope so the project doesn’t suffer?

  • How do I keep scope creep to a minimum?