What is and is not included.
WHY IT MATTERS MOST
Scope problems cause more project failures than any other single factor.
WHAT SCOPE DEFINES
The work to be done The deliverables produced The boundaries
WHAT TO STATE EXPLICITLY
What is included, in detail What is excluded, particularly things reasonably assumed
WHAT COMMONLY GETS ASSUMED
Training Documentation Data migration Support after delivery Changes discovered during the work
WHAT TO DO ABOUT EACH
Say whether it is included.
WHAT SCOPE CREEP IS
Gradual expansion without corresponding changes to time, cost or resources.
HOW IT HAPPENS
Small additions, each reasonable on its own.
WHY IT IS DANGEROUS
The project fails on the original deadline while delivering more than agreed.
WHAT TO DO ABOUT REQUESTED ADDITIONS
Assess the impact on time and cost, then decide.
WHAT NOT TO DO
Absorb them silently.
WHY
It teaches that additions are free, and more follow.
WHAT A CHANGE PROCESS LOOKS LIKE
The request is recorded Its impact is assessed Someone decides The plan is updated
HOW HEAVY IT SHOULD BE
Proportionate. For a small project, an email chain suffices.
WHAT MATTERS
That the impact is visible before the change is accepted.
