PROJECT SCOPE MANAGEMENT

PROJECT SCOPE MANAGEMENT

1. 1. PLAN SCOPE MANAGEMENT

   • Inputs
     • Project charter
       • Used to provide the project context need, high-level
     • project management plan
       • Approved subsidiary plan of the project management plan are used to create the scope M.P
     • Organizational process assets
       • policies and procedures
     • Enterprise environmental factors
       • Organization's culture infresstructure, personal administration
   • Tools &Techniques
     • Expert judgment
       • refers to input received from knowledgeable and experienced parties
     • Meetings
       • to develop the scope management plan.
   • Outputs
     • Requirements Management Plan
       • describes how requirements will be analyzed, documented, and managed
     • Scope Management Plan
       • is a major input into the Develop Project Management Plan process,

2. 2. COLLECT REQUIREMENTS

   • Inputs
     • Stakeholder Register
       • identify stakeholders who can provide information on the requirements.
     • Requirements Management Plan
       • provides the processes that will be used
     • Stakeholder Management Plan
       • used to understand stakeholder communication requirements and the level of stakeholder
     • Scope Management Plan
       • provides clarity as to how project teams will determine
     • Project Charter
       • used to provide the high-level description of the product
   • Tools &Techniques
     • Group Decision-Making Techniques
       • Unanimity
       • Majority
       • Plurality
       • Dictatorship.
     • Observations
     • Prototypes
       • Early feedback of the product before actually building it.
     • Benchmarking
       • involves comparing actual or planned practices,
     • Context Diagrams
     • Document Analysis
       • Elicit requirements by analyzing existing documentatio and information relevant to the requirements
     • Interviews
     • Group Creativity Techniques
       • identify project and product requirements
     • Questionnaires and Surveys
     • Focus Groups
     • Facilitated Workshops
       • bring key stakeholders together to define product requirements.
   • Outputs
     • Requirements Traceability Matrix
       • grid that links product requirements from their origin to the deliverables that satisfy them
     • Requirements Documentation
       • describes how individual requirements meet the business need for the project.

3. 3. DEFINE SCOPE

   • Inputs
     • Organizational Process Assets
       • can influence how scope is defined.
     • Scope Management Plan
       • establishes the activities for developing, monitoring, and controlling the project scope
     • Requirements Documentation
       • used to select the requirements that will be included in the project.
     • Project Charter
       • provides the high-level project description and product characteristics
   • Tools &Techniques
     • Expert Judgment
       • to analyze the information needed to develop the project scope statement
     • Product Analysis
       • An effective tool.
     • Alternatives Generation
       • to develop as many potential options as possible in order to identify different approaches to execute and perform the work of the project
     • Facilitated Workshops
       • Helps to reach a cross-functional and common understanding of the project objectives and its limits
   • Outputs
     • Project Scope Statement
       • Product scope description.
       • Acceptance criteria.
       • Deliverable
       • Project exclusion.
       • Constraints
       • Assumptions
     • Project Documents Updates
       • Stakeholder register, Requirements documentation, and Requirements traceability matrix.

4. 4. CREATE WBS

   • Outputs
     • Project Documents Updates
       • Requirements documentation, which may need to be updated to include approved changes.
     • Scope Baseline
       • Project scope statement.
       • WBS
       • WBS dictionary.
   • Tools &Techniques
     • Expert Judgment
       • Is applied to technical details of the project’s scope and used to reconcile differences in opinion on how to best break down
     • Decomposition
       • Is a technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts
   • Inputs
     • Enterprise environmental factors
       • may serve as external reference sources for creation of the WBS
     • Requirements documentation
       • Is essential for understanding what needs to be produced as the result of the project and what needs to be done to deliver the project and its final products.
     • Project scope statement
       • describes the work that will be performed and the work that is excluded.
     • Organizational process assets
       • Policies, procedures, and templates for the WBS; Project files from previous projects; and Lessons learned from previous projects.
     • Scope management plan
       • How to create the WBS from the detailed project scope statement and how the WBS will be maintained and approved.

5. 5. VALIDATE SCOPE

   • Outputs
     • Change Requests
       • require a change request for defect repair.
     • Accepted Deliverables
     • Work Performance Information
     • Project Documents Updates
   • Tools &Techniques
     • Group Decision-Making Techniques
       • Are used to reach a conclusion when the validation is performed by the project team and other stakeholders.
     • Inspection
       • such as measuring, examining, and validating to determine whether work and deliverables
   • Inputs
     • Work Performance Data
       • can include the degree of compliance with requirements,
     • Verified Deliverables
       • project deliverables that are completed and checked for correctness through the Control Quality process.
     • Requirements Traceability Matrix
       • links requirements to their origin and tracks them throughout the project life cycle
     • Requirements Documentation
       • lists all the project, product
     • Project Management Plan
       • The scope management plan specifies how formal acceptance of the completed project deliverables will be obtained, The scope baseline includes the approved version of a scope statement,

6. 6. CONTROL SCOPE

   • Outputs
     • Organizational Process Assets Updates
       • Causes of variances,
       • Corrective action chosen and the reasons
     • Project Documents Updates
     • Project Management Plan Updates
       • Scope Baseline Updates.
       • Other Baseline Updates.
     • Change Requests
     • Work Performance Information
   • Tools &Techniques
     • Variance Analysis
       • Cause and degree of difference between the baseline and actual performance.
   • Inputs
     • Requirements Documentation
     • Project Management Plan
       • Scope baseline.
       • Scope management plan.
       • Change management plan.
       • Configuration management plan.
       • Requirements management plan.
     • Organizational Process Assets
       • Existing formal and informal scope
       • Monitoring and reporting
     • Work Performance Data
     • Requirements Traceability Matrix