Project Scope Management, Project Selection, and Project Charters

Project Scope Management

  • Includes defining and controlling what work is/isn't in a project.
  • Ensures shared understanding between team and stakeholders.
  • Six processes:
    • Plan Scope Management: Creates a scope management plan.
      • Determines how scope will be defined, validated, and controlled.
    • Collect Requirements: Documents stakeholder needs.
      • Basis for defining product/project scope.
      • Poor definition leads to rework, consuming up to 50% of project costs.
      • Methods: interviews, focus groups, workshops.
    • Define Scope: Develops a detailed description of project and product.
      • Describes boundaries and acceptance criteria.
      • Improves estimate accuracy and communication.
    • Create Work Breakdown Structure (WBS): Subdivides project deliverables into manageable components.
      • Provides a framework of what has to be delivered.
      • Foundation for planning schedules, costs, resources, and changes.
    • Validate Scope: Formalizes acceptance of completed deliverables.
      • Increases final acceptance probability.
      • Achieved via customer inspection and sign-off.
    • Control Scope: Monitors project status and manages scope changes.
      • Maintains the scope baseline.
      • Uncontrolled expansion is scope creep.

How Organizations Choose Projects

  • Alignment with organizational strategy is key.
  • Use a two-by-two matrix (ease of implementation vs. impact on goals).
  • Identify a project champion (high-level advocate).
  • Conduct an organizational/environmental assessment.
  • Assess available resources (people, time, budget).
  • Define parameters for success (timeframe and metrics).

Developing the Project Charter

  • Formalizes a project and gives authority to the project manager.
  • Defines:
    • Essence of the project: Goals and objectives (SMART: specific, measurable, achievable, realistic, time-bound).
    • In-scope and out-of-scope items: Project boundaries.
    • Deliverables: Product, service, or result to be delivered.
    • Stakeholders: Key interested parties.
    • Roles and Responsibilities: Assignments for project delivery.
    • Project Risks: Potential negative events; to be followed by a risk register.
    • Project Constraints: Limits on costs, time, quality, etc.
    • Project Benefits: Positive outcomes for stakeholders.
    • Project Assumptions: Statements assumed true without proof.
    • Project Costs: Ballpark budget figure.