liveBook · Manning

Scope

As explained in Think Like a Software Engineering Manager

Project scope is the defined set of goals, requirements, deliverables, boundaries, assumptions, and exclusions for a project.

Project scope defines what a project will accomplish and the boundaries that keep delivery focused. It records goals, requirements, acceptance criteria, assumptions, constraints, risks, and exclusions. section 10.1.2

Scope becomes useful after stakeholders align on priorities, resources, budget, competing demands, and the project’s value. Clear documentation helps teams understand what delivery includes—and what it does not. section 10.1.2

Define scope by asking and recording:

  • What problem, customer need, or business goal does the project address? section 10.1.2
  • Which product requirements, functional requirements, nonfunctional requirements, and acceptance criteria must be satisfied? section 10.1.2
  • What is in scope, what is out of scope, and which assumptions, constraints, risks, timeline, and budget apply? section 10.1.2

Example: Project Accessible

Stakeholders prioritize an accessibility project as a must-have after discussing business value and return on investment. Scope definition then clarifies its requirements, boundaries, risks, and success measures. section 10.1.2

How Think Like a Software Engineering Manager covers it

How deep it goes
Defines goals, requirements, exclusions, assumptions, acceptance criteria, risks, constraints, and success metrics; defers detailed success criteria.
Examples
Uses Project Accessible and a possible web-app security review to make prioritization and scope questions concrete.
What you can do after
Apply it by documenting in-scope and out-of-scope work, requirements, assumptions, acceptance criteria, and success metrics.
How it connects
Connects project scope with stakeholder requirements, project charter, acceptance criteria, constraints, risks, and success metrics.

Also explained in

Compare how 9 books explain scope →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.