Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Show
Plan Scope Management - The process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled. Collect Requirements - The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives. Define Scope - The process of developing a detailed description of the project and product. Create WBS - The process of subdividing project deliverables and project work into smaller, more manageable components. Validate Scope - The process of formalizing acceptance of the completed project deliverables. Control Scope - The process of monitoring the status of the project and product scope and managing changes to the scope baseline. Key Concepts: Product scope. The features and functions that characterize a product, service, or result; and/or Project scope. The work performed to deliver a product, service, or result with the specified features and functions. The term project scope is sometimes viewed as including product scope. Completion of the project scope is measured against the project management plan Completion of the product scope is measured against the product requirements Scope Management depends on the approach taken for Project Management – Predictive or Agile. In Predictive approach the scope is defined and agreed upon at the beginning In Agile approach, the collect requirements, define scope and create WBS processes are done iteratively to take care of changing scope and all the stakeholders are engaged in defining scope and validating deliverables iteratively. Trends and Emerging Practices Collaborating with Business analysis professionals to
Tailoring Considerations:
Considerations for Agile / Adaptive Environments In Agile / Adaptive environment, the scope is not understood at the beginning of the project and it evolves during the project. Agile methodology spend less time to define and agree the scope in the early stages of the project and spend more time establishing the process for its ongoing discovery and refinement. Agile build and review prototypes and release versions in order to refine the requirements. In Agile approaches, the requirements constitute the backlog Plan Scope Management: Plan Scope Management is the process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled. The key benefit of this process is that it provides guidance and direction on how scope will be managed throughout the project. Plan Scope Management - Output: The components of the Scope Management Plan can include:
The componenets of the Requirement Management Plan can include
Collect Requirements: Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives. The key benefit of this process is that it provides the basis for defining and managing the project scope including product scope. Collect Requirement - Tools: Data Gathering
Decision Making
Multi criteria decision analysis Data Analysis Data Representation: Interpersonal and Team skills
Context Diagrams Context diagrams show inputs to the business system, the actor(s) providing the input, the outputs from the business system, and the actor(s) receiving the output. Prototypes Collect Requirements - Outputs
1. Functional requirements describe the behaviors of the product. 2. Nonfunctional requirements supplement functional requirements and describe the environmental conditions or qualities required for the product to be effective
Define Scope Define Scope is the process of developing a detailed description of the project and product. The key benefit of this process is that it describes the project, service, or result boundaries by defining which of the requirements collected will be included in and excluded from the project scope. Define Scope - Tools Product Analysis
Alternatives Analysis Define Scope - Output The Project Scope Statement provides a documented basis for future project decisions regarding the project and product scope. It includes the following key components:
Define Scope - Output Create WBS Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. The key benefit of this process is that it provides a structured vision of what has to be delivered. The WBS:
Which of the following project scope management processes involves subdividing the major project?The Work Breakdown Structure (WBS) involves subdividing the project deliverables into smaller units.
What is the management technique for subdividing the project into its component elements called?Decomposition is a technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.
Which document is produced by breaking the project scope into smaller and manageable components?Breaking work into smaller tasks is a common productivity technique used to make the work more manageable and approachable. For projects, the Work Breakdown Structure (WBS) is the tool that utilizes this technique and is one of the most important project management documents.
What are the 5 scope management processes?Steps of project scope management. Plan Your Scope. In the planning phase, you want to gather input from all of the project stakeholders. ... . Collect Requirements. ... . Define Your Scope. ... . Create a Work Breakdown Structure (WBS) ... . Validate Your Scope. ... . Control Your Scope.. |