2. Project Scope Management Flashcards
Project Scope Management
Project scope management is to define what is included in the project and what is not included in the project. The scope of the project is the work that is involved and the factors to execute the project successfully. There are 6 project scope management processes in planning and controlling process group.
Project Scope Management Processes
- Plan Scope Management; develop a plan for how you will manage and control scope and requirements on the project
- Collect Requirements; determine requirements making sure all requirements support the projects business case as described in the project charter
- Define Scope; short and balance the needs of the stakeholders to determine scope
- Create WBS;
- Validate Scope;
- Control Scope. - measure scope performance and adjust
- Plan Scope Management process
It is the process of creating the document in which information about how the scope is defined and managed throughout the project process. The scope management plan provides the direction of how to deal with the end to end requirements of the project. The scope management plan acts as a guide to the project flow. Planning process group
- Creates project scope management plan defining project’s boundaries
- direct how control of scope will be managed through project, as well as how changes are to be implemented
documents how project scope will be defined, validated and controlled
Provides guidance and direction for scope management throughout project
- Collect Requirements process
The process of collecting all the requirements from all the resources or stakeholders to meet the project objective is called Collect Requirement Process. The documentation of all the requirement helps in tracing the matrix of the organizational assets required for the project. The collected requirement is to be managed and fulfilled to meet the objective of the project. (planning process)
- determine, documents, manages project requirements and stakeholder needs
- Leads to requirements doc and project responsibilities being established
- Define Scope process
The complete description of the scope of the project is documented in this process. The main objective of the project is to document what is included in the project and what is not included in the project. This process includes the scope management plan, the requirements documentation created in the collect requirements process, project charter and project risks assumptions and constraints to define the project and product scope
A clear description of the project is available from this process. Planning process
1. refines requirements into a clear description of the project and its product
2. Leads to development of project scope statement, including acceptance criteria, constraints and assumptions
- Create WBS process
Creating WBS refers to the Work Breakdown Structure in which all the project activities are divided into smaller activities. This helps in assigning tasks or activities to the resources. This framework also helps in understanding the project objectives and the defined scope. The inputs, tools and techniques, and the outputs are clearly defined in this process. Planning process group
- develop a WBS used to decompose project work into discrete activities
- establishes a scope baseline, including the project scope statement, WBS and WBS dictionary
- Validate Scope process
In this process, the final deliverables are validated and accepted by the project manager. It is a formal acceptance of the completed project whether it met the scope or not is validated in this process. Before submitting the final deliverables to the customer, if the project manager validates the scope, then the chances of the customer accepting the projects are also high. Monitoring and controlling process group
- formalize acceptance of completed deliverables
- Utilized established requirements information and inspections to approve a project’s completion and request any needed changes
- Control Scope process
The control scope process ensures whether all the project activities are according to the planned scope. This process monitors the status of the project and manages the changes according to the scope baseline. It ensures there is no slippery in the project scope during project activities. Monitoring and controlling process group
- ensures project work remains in alignmentu with project scope
- utilizes a variety of assets created in other Project Scope Management processes
Scope baseline
includes all the work that must be done on a project. Used as a point of comparison for controlling purposes.
- Must only be modified via formal change control methods
- Must only be updated when changes are approved
Includes:
- Project Scope Statement
- WBS
- WBS Dictionary
Project scope statement
Primary output from define scope process is the project scope statement. describes project scope (project and product), major deliverables, acceptance criteria, what is NOT part of the project, assumptions and constraints
- here is what we will do on this project
- here is the approved project and product scope
WBS
visualization of all project work, broken down into individual pieces of work, more manageable deliverables including identifying and control information
WBS Dictionary
sister document to WBS including more detailed information related to work atttributes, requirements, and assumptions
Plan Scope Management (Input, T&T, Output)
Plan Scope Management -
INPUTS include: Project plans, project charter, Enterprise Environment Factors (EEFs), and Organization Process Assets (OPAs):
TOOLS and TECHNIQUES includes expert judgement, data analysis and meetings
OUTPUS: includes the scope management plan and requirements management plan
SMP - the entirety of the project - both scope & project
RMP - focuses on product that the project is trying to create
Product scope
Product scope Is another way to say requirements that relate to the product of the project
Requirements management plan
Once I have all the requirements what will I do to analyze prioritize manage and track changes to them? What should I include in the requirements traceability matrix
