Chapter 7: Scope Planning

Chapter 7: Scope Planning

1. Definition of scope

   • Scope statements should include how the results will be measured
   • Not measurable
     • A new registration system
     • The system will be fast
     • The system will support the required volumes
   • Measurable
     • Response time will be under 1 second
     • New system, students will be able to register for classes using a browser or a smartphone.
     • 75 students must be able to add an average of 3 classes each 15-minute period.

2. Deliverables

   • Tangible outcomes, measurable results, or specific items
   • Must be described in a sufficiently low level of details

3. Types of requirements

   • Functional
   • Non-functional
     • Performance (capacity, display)
     • Development (time, resource, quality)
   • Technical
   • User
   • Business
   • Regulatory

4. Inputs

   • Project management plan
   • Project Charter
   • Enterprise environmental factors
   • Organizational process assets

5. Tools & Techniques

   • Expert judgment
   • Meetings

6. Outputs

   • Scope management plan
   • Requirements management plan

7. Scope inputs

   • Sources
     • Project sponsor & Management
     • Strategic Plan & Users
     • Users & Customers
     • Competitors & Suppliers & Regulations
   • Techniques
     • Interviews & Focus groups
     • Facilitated groups & Group creativity techniques
     • Prototyping & Observation
     • Questionnaires and surveys

8. Requirements Traceability Matrix fields

   • Unique identifier & Requirement statement
   • Source & Design specification reference
   • Test specification & Test case numbers

9. Work Breakdown Structure (WBS)

   • Creating
     • List of all activities required to create all the deliverables in the scope.
     • Activities may be broken down into smaller tasks, in a hierarchical pattern
     • List all the project outputs
     • Identify of all the activities required to deliver the outputs.
     • Complex for a large project
   • Benefits
     • Help prevent work from slipping through the cracks.
     • Helps prevent changes.
     • Gets team buy-in and builds the team
     • Helps people get their minds around the project.

10. Scope Statement Typical Contents

    • Project Name & Project charter
    • Owner, sponsor, project manager, stakeholders
    • Problem statement & Project Goals and Objectives
    • Project Requirements & Project Deliverables
    • Exclusions & Milestones & Cost estimates