Project Scope

Project Scope is a defined boundary for what a project will and won’t cover — documented as a scope statement and supporting details before work begins.

Why it matters#

Without a clear scope, projects expand to fill whatever time and energy are available. Content gets added because it “seems relevant,” deadlines slip, and the course loses focus. A scope statement gives you and your collaborators a shared reference point for every decision about what’s in and what’s out.

The scope statement#

A single sentence that captures the project’s purpose and intended outcome.

Formula: [What the course will teach] so that [desired outcome].

Example:

“Provide applicable instruction on dog training principles, practised in the field, so that adopted dogs successfully transition into their new homes.”

Write this before anything else. Every subsequent design decision — objectives, content, assessments — should be traceable back to it.

What the full scope document covers#

Element What to define
Goals What the course is trying to achieve
Deliverables What will be produced (modules, videos, assessments, etc.)
Tasks The work required to produce each deliverable
Costs Budget for time, tools, and team
Timeline Deadlines and milestones
Roles Who is responsible for what — see Elearning Team

Key facts#

  • The scope statement is a decision-making tool, not just a planning formality. When an SME wants to add a new topic or a stakeholder requests a change, the scope statement is how you evaluate whether it belongs — does it serve the stated outcome?
  • Scope creep is the norm, not the exception. New content, new stakeholders, and new requirements will appear. A written scope doesn’t prevent this, but it gives you grounds to push back or renegotiate deliberately rather than absorbing changes silently.
  • A vague scope produces a vague course. If the outcome in your scope statement could apply to any course (“learners will improve their skills”), it’s not specific enough. The outcome should describe a measurable change in what learners can do or how they behave.
  • Scope connects directly to learning objectives. Once the scope is set, objectives operationalise it — they define the specific outcomes that collectively deliver on the scope statement.

When to use it#

  • At the start of every project, before writing objectives or designing content
  • When a stakeholder requests a significant change — revisit the scope first
  • When a course feels unfocused — trace everything back to the scope statement and cut what doesn’t connect