This document discusses how to manage scope changes on projects. It begins by defining project scope as the work needed to deliver specified features and functions. It then provides tips for properly defining an initial project scope by identifying the project, documenting requirements, setting priorities, and establishing budgets and timelines. Any changes to scope, timeline, or budget require adjustments to the other two. Scope changes should be tracked in a change log and approved through change management. Left uncontrolled, continuous scope changes can lead to harmful scope creep. The document emphasizes properly planning and documenting scope to set the project up for success.

1. How to Manage
Scope Change

2. Kelly Hagen, PMP
khagen@bdo.ca

3. Project Scope
“The work that needs to be accomplished to deliver a product, service,
or result with the specified features and functions.”
--Wikipedia

4. Get off on the right foot.

5. How to Define Scope
• Identify your Project
• Document your requirements
• Set priorities between must have and nice to have
• Set your budget
• Define your timeline expectations

6. BDO Project Methodology
Planning Design Configuration Testing Deployment Support

7. Planning
• Spend enough time to understand the project
expectations
• Scope can go beyond functionality
• Who is doing what?
• Time, Scope and Budget go hand in hand
• One cannot move without the other

8. Project Balance
• If you have a change in scope…
• The timeline and cost change
• If you have a change in timeline…
• The cost and scope change
• If you have a change in budget…
• The scope and timeline change

9. Project Balance

10. Function Requirements Document
(FRD)
• Defines the requirements identified in the planning
workshops
• Needs to be detailed enough to ensure both parties
understand and agree to the expected results

11. FRD….

12. Fit / Gap Analysis
• Next step to the functional requirements document
• Confirm your must haves and compare them
against the solutions “out of the box” capabilities
• If there is a gap – ask if there is a industry standard
approach using “out of the box” functionality.
• Determine if you can adopt the standard process or
if you need the solution to bend to your process
• Create a custom specification document to support
the need

13. Custom Design Spec

14. Custom Design Spec

15. Things Change….

16. Things Change …
• New functionality leads to change
• If you ask, the consultant will say “YES”
• Keep a change log
• Insist on good change management
• Ensure the project team understands the original
scope

17. What does Change Look Like
• Extended functionality
• Additional Training
• Additional resources
• Additional software

18. Change Log

20. Scope Creep
• Scope creep (also called requirement creep,
function creep and feature creep) in project
management refers to uncontrolled changes or
continuous growth in a project's scope. This can
occur when the scope of a project is not properly
defined, documented, or controlled. It is generally
considered harmful.

21. Questions?
Kelly Hagen – khagen@bdo.ca