5. PROJECT SCOPE MANAGEMENT

5. PROJECT SCOPE MANAGEMENT

1. 5.1 Plan Scope Management

   • Process of creating a scope management plan that documents how the project and product scope will be defined, validated, and controlled
   • It provides guidance and direction on how scope will be managed throughout the project.
   • Inputs
     • 1 Project charter
     • 2 Project management plan
       • Project life cycle description
         • determines the series of phases that a project passes through from its inception to the end of the project.
       • • Quality management plan
         • can be influenced by how the organization’s quality policy, methodologies, and standards are implemented on the project.
       • • Development approach
         • defines whether waterfall, iterative, adaptive, agile, or a hybrid development approach will be used.
     • 3 Enterprise environmental factors
       • Organization’s culture, Infrastructure, Personnel administration, and Marketplace conditions.
     • 4 Organizational process assets
       • Policies and procedures, Historical information and lessons learned repositories
   • Tools & Techniques
     • 1 Expert judgment
     • 2 Data analysis
       • Alternatives analysis
     • 3 Meetings
       • Include the project manager, the project sponsor, selected project team members, selected stakeholders, anyone with responsibility for any of the scope management processes, and others as needed.
   • Output
     • 1 Scope management plan
       • Describes how the scope will be defined, developed, monitored, controlled, and validated. It´s formal or informal, broadly framed or highly detailed, based on the needs of the project.
     • 2 Requirements management plan
       • Describes how project and product requirements will be analyzed, documented, and managed.

2. 5.2 Collect Requirements

   • Process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
   • It provides the basis for defining the product scope and project scope.
   • Inputs
     • 3 Project documents
       • Assumption Log., Lessons learned register, Stakeholder Register.
     • 4 Business documents
     • 5 Agreements
       • can contain project and product requirements.
     • 2 Project management plan
       • Scope management plan
         • contains information on how the project scope will be defined and developed.
       • Requirements management plan
         • has information on how project requirements will be collected, analyzed, and documented.
       • Stakeholder engagement plan
         • is used to understand stakeholder communication requirements and the level of stakeholder engagement in order
     • 6 Enterprise environmental factors
     • 7 Organizational process assets
     • 1 Project charter
   • Tools & Techniques
     • 2 Data gathering
       • Brainstorming
         • Used to generate and collect multiple ideas related to project and product requirements.
       • Interviews
         • Is a formal or informal approach to elicit information from stakeholders
       • Focus groups
         • Used to learn about their expectations and attitudes about a proposed product, service, or result
       • Questionnaires and surveys
         • Are written sets of questions designed to quickly accumulate information from a large number of respondents
       • Benchmarking
         • Involves comparing actual or planned products, processes, and practices
     • 3 Data analysis
       • Document analysis
     • 4 Decision making
       • Voting
         • Unanimity
           • A decision that is reached whereby everyone agrees
         • Majority
           • Decision that is reached with support obtained from more than 50% of the members of the group
         • Plurality.
           • A decision that is reached whereby the largest block in a group decides, even if a majority is not achieved.
       • Multicriteria decision analysis
       • Autocratic decision making
     • 5 Data representation
       • Affinity diagrams
         • Consolidates ideas created through individual brainstorming sessions into a single map
       • Mind mapping
         • Allow large numbers of ideas to be classified into groups for review and analysis.
     • 6 Interpersonal and team skills
       • Nominal group technique
         • Used to rank the most useful ideas for further brainstorming or for prioritization
       • Observation/conversation
         • Provide a direct way of viewing individuals in their environment and how they perform their jobs or tasks and carry out processes
       • Facilitation
         • Is used to define product requirements.
     • 7 Context diagram
       • Represents the product scope by showing a business system
     • 8 Prototypes
       • Is a method of obtaining early feedback on requirements
   • Outputs
     • 1 Requirements documentation
       • Describes how individual requirements meet the business need for the projec
       • Include: Business requirements, Stakeholder requirements, Solution requirements, Transition and readiness requirements, Project requirements and Quality requirements.
     • 2 Requirements traceability matrix
       • Is a grid that links product requirements from their origin to the deliverables that satisfy them.
       • It´s provides a structure for managing changes to the product scope

3. 5.3 Define Scope

   • Process of developing a detailed description of the project and product
   • Inputs
     • 3 Project documents
       • Assumption log
         • Identifies assumptions and constraints about the product, project, environment, stakeholders, and other factors
       • Requirements documentation
         • Identifie requirements that will be incorporated into the scope.
       • Risk register
         • Contains response strategies that may affect the project scope
     • 4 Enterprise environmental factors
     • 5 Organizational process assets
     • 1 Project charter
     • 2 Project management plan
       • Scope management Plan
   • Tools & Techniques
     • 1 Expert judgment
     • 2 Data analysis
       • Used to evaluate ways to meet the requirements and the objectives identified in the charter.
     • 3 Decision making
       • Multicriteria decision analysis
     • 4 Interpersonal and team skills
       • • Facilitation
     • 5 Product analysis
       • Used to define products and services
   • Outputs
     • 1 Project scope statement
       • Is the description of the project scope, major deliverables, assumptions, and constraints.
     • 2 Project documents updates
       • Requirements traceability matrix
       • Requirements documentation
       • Assumption log
         • Is updated with additional assumptions or constraints that were identified during this process.
       • Stakeholder register
   • It describes the product, service, or result boundaries and acceptance criteria.

4. 5.4 Create WBS

   • Process of subdividing project deliverables and project work into smaller, more manageable components
   • It provides a framework of what has to be delivered.
   • Inputs
     • 2 Project documents
       • Project scope statement
         • Describes the work that will be performed and the work that is excluded.
       • Requirements documentation
         • Describe how individual requirements meet the business need for the project.
     • 1 Project Management Plan
       • Scope management plan
     • 3 Enterprise environmental factors
     • 4 Organizational process assets
   • Outputs
     • 1 Scope baseline
       • Is the approved version of a scope statement, WBS, and its associated WBS dictionary
       • Project scope statement
         • Includes the description of the project scope, major deliverables, assumptions, and constraints
       • WBS
         • Is a hierarchical decomposition of the total scope of work to be carried out
       • Work package.
         • The lowest level of the WBS is a work package with a unique identifier
       • Planning package
         • A control account may include one or more planning packages
       • WBS dictionary
         • It provides detailed deliverable, activity, and scheduling information about each component in the WBS.
     • 2 Project documents updates
       • Assumption log
         • Is updated with additional assumptions or constraints that were identified during the Create WBS process.
       • Requirements documentat
         • To include approved changes resulting from the Create WBS process.
   • Tools & Techniques
     • 1 Expert judgment
     • 2 Decomposition
       • Used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.

5. 5.5 Validate Scope

   • Process of formalizing acceptance of the completed project deliverables
   • Inputs
     • .1 Project management plan
       • Inlcude: Scope baseline., Scope management plan, uu Requirements management plan.
     • .2 Project documents
       • Include: Lessons learned register, Requirements documentation, Quality reports, Requirements traceability matrix.
     • .3 Verified deliverables
       • Are project deliverables that are completed and checked for correctness through the Control Quality process.
     • .4 Work performance data
       • include the degree of compliance with requirements, number of nonconformities
   • Tools & Techniques
     • .1 Inspection
     • .2 Decision making
       • Voting
   • Outputs
     • .1 Accepted deliverables
     • .2 Work performance information
       • Includes information about project progress
     • .3 Change requests
       • Are processed for review and disposition through the Perform Integrated Change Control process
     • .4 Project document updates
       • Lessons learned register
         • is updated with information on challenges encountered
       • Requirements documentation
         • may be updated with the actual results of validation activity
       • Requirements traceability matrix
         • Is updated with the results of the validation, including the method used and the outcome

6. 5.6 Control Scope

   • Process of monitoring the status of the project and product scope and managing changes to the scope baseline.
   • Inputs
     • .1 Project management plan
       • Scope management plan
       • Requirements management plan
       • Change management plan
       • Configuration management plan
       • Scope baseline
       • Performance measurement baseline
     • .2 Project documents
       • Lessons learned register
       • Requirements documentation
       • Requirements traceability matrix
     • .3 Work performance data
       • Include the number of change requests received, requests accepted, and the number of deliverables verified, validated, and completed.
     • .4 Organizational process assets
   • Tools & Techniques
     • .1 Data analysis
       • Variance analysis
         • Is used to compare the baseline to the actual results
       • • Trend analysis
         • Examines project performance over time to determine if performance is improving or deteriorating.
   • Outputs
     • .1 Work performance information
       • includes correlated and contextualized information on how the project and product scope are performing compared to the scope baseline
     • .2 Change requests
     • .3 Project management plan updates
       • Scope management plan
       • Scope baseline
       • Schedule baseline
       • Cost baseline
       • Performance measurement baseline
     • .4 Project documents updates
       • Lessons learned register
       • Requirements documentation
       • Requirements traceability matrix
   • The scope baseline is maintained throughout the project

7. Product scope

   • features and functions that characterize a product, service, or result

8. Project scope.

   • work performed to deliver a product, service, or result with the specified features and functions.