Chapter 5: Project Scope Management Flashcards
Project Scope Management Processes
PLANNING 1. Plan Scope Management 2. Collect Requirements 3. Define Scope 4. Create WBS MONITORING AND CONTROLLING 5. Validate Scope 6. Control Scope
Plan Scope Management
It is the process of creating a scope management plan that documents how the project and product scope will be defined, validated and controlled
Collect Requirements
It is the process of determining, documenting and managing stakeholder needs and requirements to meet the objectives.
Scope Management Plan
It is a component of the project management plan that describes how the scope will be defined, developed, monitored, controlled and validated.
Requirements Management Plan
It is a component of the project management plan that describes how a project and product requirements will be analyzed, documented and managed
Joint Application Design/Development
- Used in the software industry
- A facilitation technique
- Brings the business SMEs and development team to gather requirements and improve the software development process
Quality Function Deployment
- Used in Manufacturing Industry
- A facilitation technique
- Helps determine the critical characteristics of a new product development
- Starts by collecting customer needs, AKA VOC (Voice of Customer)
- These needs are then objectively sorted and prioritized and goals are set to achieve them
User Stories
- A facilitation technique
- Short, textual description of the required functionality
- Often developed during the requirements workshop
It describes
1. Stakeholder role
2. Who benefits from the feature
3. What stakeholder needs to accomplish
4. Benefits of stakeholders
Prototyping
Method of obtaining early feedback on the requirement by providing a model of the expected product before actually building it.
Storyboarding
It is a prototyping technique showing a sequence or navigation through a series of images and illustrations.
Requirements Documentation
Describes how individual requirements meet the business needs of the project.
Requirements Traceability Matrix
It is a grid that links product requirements from their origin to their deliverables that satisfy them.
Acts as a means to track requirements throughout the project lifecycle thus ensuring that requirements mentioned in the requirements documentation are delivered at the end of the project
Define Scope
A process of defining a detailed description of a project and product.
Project Scope Statement
Description of the project scope, major deliverables and exclusions
Create WBS
The process of subdividing project deliverables and project work into smaller more manageable components.
Work Packages
is the work defined at the lowest level of WBS for which cost and duration can be estimated and managed
Decomposition
The technique used for dividing and subdividing the project scope and project deliverables into smaller more manageable parts.
Scope Baseline
The approved version of Scope statement, WBS and WBS dictionary, which can be changed only through formal change control procedures and is used as a basis for comparison
WBS
Is the hierarchical decomposition of the total scope of the work to be carried out by the project team to accomplish the project objectives and create the project deliverables.
Each descending level of the WBS represents an increasingly detailed definition of the project work
Control Account
It is a management control point where scope, budget and schedule are integrated and compared with the earned value for performance measurement
- One work package is assigned to one control account
- One control account may have 2 or more work packages assigned to it
- It may include one of more planning packages
Planning package
It is a work breakdown structure below the control account and above the work package with known work content but without the detailed schedule
WBS dictionary
Is a document that provides detailed deliverable, scope and scheduling information about each component in the WBS
Validate Scope
Process of formalizing acceptance of the completed project deliverables
Control Scope
It is the process of monitoring the status of the project and the product scope and managing changes to the scope baseline
8/80 Rule
A planning heuristic for creating the WBS. It states that work packages in a WBS should take no more than 80 hours of labour to create and no fewer than 8 hours of labour to create
Active Observation
The observer interacts with the worker to ask questions and understand each step of the work being completed. In some cases, the observer could serve as an assistant in doing the work
Affinity Diagrams
When stakeholders create a large number of ideas, you can create an affinity diagram to cluster similar ideas together for further analysis
Alternatives generation
A scope definition process of finding an alternative solution for the project customer while considering the customers’ satisfaction, the cost of the solution and how customers may use the product in operations
Autocratic
A decision method where only one individual makes the decision for the group
Brainstorming
This approach encourages as many ideas as possible about the project requirements. No idea is judged or dismissed during the brainstorming process.
Change Control System (CCS)
Documented in the scope management plan.
This system defines how changes in a scope management plan are managed and controlled
Code of Accounts
A numbering system for each items in WBS
Context Diagram
These diagrams show the relationships between elements of an environment
Focus groups
A moderation-let requirements collection method to elicit requirements from stakeholders
Functional Analysis
- This is the study of functions within a system, project or what more likely in a project scope statement, the product the project will be creating.
- Functional analysis studies the goals of the product, how the product will be used and the expectations that the customer has of the product once it leaves the project and moves into operations
- Functional analysis may also consider the cost of the products in operations which is known as life-cycle costing
Funding Limit
Most projects have a determined budget in relation to the project scope. There may be a qualifier on this budget, such as plus or minus 10 percent based on the type of cost estimate created
Interviews
A requirements collection method to elicit requirements from stakeholders in a one to one conversation
Majority
A group decision method where more than 50 percent of the group must be in agreement
Mind Mapping
This approach maps ideas to show the relationship among requirements and differences between requirements. The map can be reviewed to identify new solutions or to rank identified requirements
Nominal Group Technique
As with brain storming participants are encouraged to generate as many ideas as possible, but the suggested ideas are ranked by a voting process
Passive Observer
The observer records information about the work being completed without interrupting the process
- sometimes called the invisible observer
Plurality
A group-decision method where the largest part of the group makes the decision when its less than 50% of the total
Product Acceptance Criteria
This project scope statement component works with the project requirements but focuses specifically on the product and what the conditions and processes are for formal acceptance of the product
Product Breakdowm
A scope definition technique that breaks down a product into hierarchical structure, much like a WBS breaks down a project scope
Product Scope Definition
This is a narrative description of what the project is creating as a deliverable for the project customer
Product Scope
Defines the product or service that will come as a result of completing the project. It defines the features and function that characterize the product.
Project Boundary
A project boundary clearly states what is included in the project and what is excluded from the project.
This helps eliminate assumption between the project management team and the project customer
Project Constraint
A constraint is anything that limits the project managers’ options. Examples: Predetermined budget, deadline, materials or resources the project manager must use within the project
Project Objectives
These use measurable goals that determine a projects acceptability to the project customer and overall success of the project. Objectives often include the cost, schedule, technical requirements and quality demands
Project Requirements
These are demands set by the customer, regulations or performing organization that must exist for project deliverables to be acceptable
Project Scope
Defines the scope and only the required work to complete the project objectives
Project Scope Management Plan
This project management subsidiary plan control
- how the scope will be defined
- How the project scope statement will be created
- how the WBS will be created
- how the scope validation will proceed
- how the project scope will be controlled throughout the project
Requirements Documentation
This document of what the stakeholders expected in the project defines all the requirements that must be present for the work to be accepted by the stakeholders
Requirements Management Plan
This subsidiary plan defines
- how changes to the project requirements will be permitted
- how requirements will be tracked
- how changes to the requirements will be approved
Schedule Milestones
The project customer may have specific dates when phases of the project should be completed. These milestones are often treated as project constraints.
Scope Validation
The formal inspection of project deliverables which lead to project acceptance
Stakeholder Analysis
A scope definition process where the project management team interviews the stakeholders and categorizes, prioritizes and documents what the project customer wants and needs. The analysis is to determine, quantify and prioritize the interests of the stakeholders. Stakeholder analysis demands quantification of stakeholder objectives: goals such as “good”, “satisfaction” and “speedy” arent quantifiable
System Analysis
A scope definition approach that studies and analyses a system, its components and the relationships of components within the system
Systems Engineering
This project scope statement creation process studies how a system should work, designs and creates a system model and then enacts the working system based on the projects goals and the customer expectations. Systems engineering aims to balance the time and cost of the project in relation to the scope of the project
Value Analysis
This approach examines the functions of the projects products in relation to the cost of the features and functions. This is where, in some extent, the grade of the product is in relation to the cost of the product.
Value Engineering
This approach to product scope statement creation attempts to find the correct level of quality in relation to a reasonable budget for project achieving an acceptable performance of the product
WBS template
A prepopulated WBS for repetitive projects. Previous projects WBS are often used as a template for current situations
