Session 4 Scope mgmt - Project Scope Management Project Scope Management 5.1 Collect Requirements 5.2 Define Scope 5.3 Create WBS(Work Breakdown

Session 4 Scope mgmt - Project Scope Management Project...

This preview shows page 1 - 10 out of 43 pages.

Project Scope Management
Project Scope Management 5.1 Collect Requirements 5.2 Define Scope 5.3 Create WBS (Work Breakdown Structure) 5.4 Verify Scope 5.5 Control Scope
Project Scope vs. Product Scope Project Scope The work that has to be performed to deliver the product of the project with the specified features and functions. Product Scope Features and functions the characterize the product of the project. A deliverable is a product produced as part of a project, such as hardware or software, planning documents, or meeting minutes.
Project Scope Sets the logical boundaries of the project Defines what the project is and what it is not. Concerned with defining and controlling what is and what is not included in the projects Prevents extra work or gold plating Project scope management includes the processes involved in defining and controlling what is or is not included in a project.
Project Scope Management Processes Collect Requirements : The process of defining and documenting stakeholder’s needs to meet the project objectives. Scope definition : The process of developing a detailed description of the project and product Creating the WBS : Subdividing the major project deliverables into smaller, more manageable components. Scope verification : Formalizing acceptance of the project scope. Scope control : Controlling changes to project scope.
Scope Planning and the Scope Management Plan The scope management plan is a document that includes descriptions of how the team will prepare the project scope statement, create the WBS, verify completion of the project deliverables, and control requests for changes to the project scope. Key inputs include the project charter, preliminary scope statement, and project management plan.
Managing Project Scope Activities and processes needed to ensure that only required work is performed Managing changes on the project scope Scope management needs to be integrated with other knowledge areas to ensure the project work will result in delivery of the specified product scope. The project manager must be in control of scope. Scope changes should be handled in a structured logical and controlled manner.
5.1 Collect Requirements Inputs Process Outputs Tools & Techniques Project charter Stake register “…Defining and documenting stakeholders needs to meet the project objectives. The projects success is directly influenced by the care taken in capturing and managing project and product requirements Requirements documents Requirements management plan Requirements traceability matrix Interviews Focus groups Workshop Group Discussion Questionnaire s and surveys Observations Prototypes
Input Created in project communications management, identify stakeholder process Stakeholder identification information Name, Organization, position, location, role in project, etc.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture