Scope Creep

In this topic, students and community leaders learn the discipline of Scope Control. We move beyond defining the work to the active defense of the project plan. Participants will learn how to implement a formal Change Control process that allows for flexibility while maintaining the integrity of the project’s original goals.

Core Objectives:

• Identifying the Warning Signs: Learning to spot the moments when a project begins to drift, such as unrecorded “side requests” or team members adding features that weren’t in the original Requirements Document.
• The Change Request Process: Establishing a simple, professional 4-step workflow for any new idea:
  1. Submit: The stakeholder proposes the change.
  2. Impact Analysis: The Project Manager calculates the effect on time, cost, and risk.
  3. Approve/Reject: A designated authority (like a school principal or committee) makes the decision.
  4. Update: If approved, the Project Plan and WBS are officially adjusted.
• Managing Expectations: Communication strategies for explaining to stakeholders why a “great idea” might have to wait for a future phase of the project.
• Gold Plating vs. Value: Understanding that giving a “bonus” feature without approval is actually a failure of professional management, as it consumes resources that weren’t budgeted.

Key Outcome: By the end of this topic, participants will have the confidence to manage changes without losing control of their project. They will possess a formal framework for evaluating new ideas, ensuring that their school and community initiatives are delivered on time, within budget, and with the high level of quality originally promised.