Planning Scope

Planning Scope

1. Plan Scope Management (guidance and direction)

   • M: How the scope will be defined, validated and controlled
   • IP: 3, I:4, T&T:2
   • Output: Scope Management plan
     • 1 Preparing a detailed project scope statement
     • 2 Enables the creation of the WBS
     • 3 Establish how the WBS will be maintained and approved
     • 4 Specifies how formal acceptance of the completed deliverables will be obtained
     • 5 How requeste for changes will be processed
   • Output: Requirements management plan
     • 1 How requirements activities will be planned, tracked and reported
     • 2 Configuration management activities: changes to the product, impacts will be analyzed, traced and tracked, authorization levels
     • 3 Requirements priorization process
     • 4 Product metrics
     • 5 Traceability structure: atributes on traceability matrix
   • Context
     • Project Charter: Project Statement of work and product characteristics
     • Enterprise/Organization: Culture, Infraestructure, Marketplace conditions, polices and procedures, lessons learned
     • Project Management Plan: influence the approach

2. Collect Requirements (the project scope including product scope)

   • M:Stakeholders needs and requirements to meet project objectives
   • IP: 4, I: 5; T&T: 11
   • Output: Requirements documentation
   • Outputs: Requirements traceability matrix
     • Description
     • Classification
     • Project objectives
     • WBS deliverables
     • Associated attributes: complexity, acceptance criteria
     • ID
   • Context
     • RMP: define and document stateholders needs
     • SMP: which type of requirements?
     • PCh
     • Stakeholder mangement plan: understand stake holder communication requirements
     • Stakeholder register: main expectations
   • Classification
     • Bussiness
     • Stakeholder
     • Functional: behavior of the product
     • Nonfunctional: reliability, security, safety
     • Transition
     • Project
     • Quality

3. T&T

   • Expert Judgment
   • Group decision-making
   • Meetings
   • Decomposition (100 percent rule)

4. Define Scope (Develop the project scope statement)

   • IP: 4, I:4, T&T: 4
   • Output: Project Scope Statement
     • 1 Product Scope description (Characteristics)
     • 2 Acceptance criteria (conditions/deliverables)
     • 3 Deliverable (unique & verifiable)
     • 4 Project exclusion (out of scope)
     • 5 Constraints (restrictions, limitations)
     • 6 Assumptions (without proof)
   • M: which of the requirements collected will be included?
   • Context
     • OPA
     • PCh
     • RD: to select
     • SMP: activities for developing, M&C the project scope
   • Output: Project Documents Updates
     • Stakeholder register
     • Requirements documentation
     • Requirements traceability matrix

5. Create WBS (structured vision. Subdividing deliverables and work)

   • M: hierarchical decomposition, smaller, more manageable ($, t) components (delverables, results)
   • IP:4, I:5, T&T:2
   • Context
     • SMP: how to create WBS, maintained and approved
     • PSS
     • RD: what needs
     • EEF, OPA
   • Output: Scope Baseline (approved version)
     • Project scope statement
     • WBS (unique identifier, code of accounts)
     • WBS dictionary (about each component)
       • Code of account identifier
       • Description of work
       • Assumptions & Constraints
       • Responsible organization
       • Schedule milestone
       • Associated schedule activities
       • Resources required
       • Cost estimates
       • Quality requirements
       • Acceptance criteria
       • Technical references
       • Agreement information
   • Output: Project Documents Updates (approved changes)