Chapter 5- Project Scope Management Flashcards
8/80 Rule
A planning heuristic for creating the WBS. This rule states that the work package in a WBS 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 instances, the observer could server as an assistant in doing the work.
Affinity diagrams
When stakeholders create a larger number of ideas, you can use an affinity diagram to cluster similar ideas together for further analysis. Common categories: Business requirements, Project Reqs, Stakeholder req, Solution Reqs, Quality Reqs, Technical Reqs, Transition requirements
Alternatives generation
A scope definition process of finding alternative solutions for the project customer while considering the customer’s satisfaction, the cost of the solution, and how the customer may use the product in operations
Brainstorming
This approach encourages participants to generate as many ideas as possible about the project requirements. No idea is judged or dismisses during the brainstorming session.
Change Control System CCS
Documented in the scope management plan, this system defines how changes o the project scope are managed and controlled.
Change Management Plan
This subsidiary plan defines how changes will be allowed and managed within the project.
Code of accounts
A numbering system for each item in WBS. The PMBOK is a good example of a code of accounts, as each chapter and its subheadings follow a logical numbering scheme.
Configuration management plan
The subsidiary plan defines how changes to the features and functions of the project deliverables will be monitored and controlled within the project.
Context diagram
These diagrams show the relationship b/n elements of an environment. For example a context diagram would illustrate the networks, servers, work stations, and people that interact with the elements of the environment
Delphi technique
This approach uses rounds of anonymous survey to build consensus. Because the surveys are anonymous, participants are more likely to be honest with their requirements, opinions, and statements. The PM organises these comments and inputs and then sends them back to the participant for another round of anonymous input.
Dictatorship
A decision method where only one individual makes the decision for the group.
Focus groups
A moderator-led requirements collection method for elicit requirements from stakeholders
Functional analysis
This is the study of the functions within a system, project, or, what’s more likely in the 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 the customer has of the product once it leaves the project and moves into operations. Functional analysis may also consider the cost of the product in operations, which is known as life-cycling.
Funding limit
Most projects have a determined budget in relation to the project scope. There may be a qualifies if this budgets, such as plus or minus 10% based on the type of cost estimate created.
Initial Project organisation
The project scope statement identifies the project team and the key stakeholders. In some organisation, especially on larger projects, the team organization and structure are also documented.
Interviewers
A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversations.
Majority
A group decision method where more than 50% of the group must be in agreement.
Mind mapping
Diagram of ideas or notes used to help generate, classify, or record information. It will show branches extending out from central core word or words.
Nominal Group technique
A technique that enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization.
Passive observation
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 it’s less than 50 percent of the total ( Consider three or four fractions within the stakeholders.)
Product acceptance criteria
This project scope statement components work with the project requirements, but focuses specifically on the product and what the conditions are processes are for formal acceptance of the product.
Product breakdown
A scope definition technique that breaks down a product into a hierarchical structure, much like a WBS breaks down a project scope
Product Scope description
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 about as a results of completing the project. It defines the features and functions that characterise the product.
Project assumptions
A project assumption is a factor in the planning process that is held to be true but not proven to be true.
Project boundaries
clearly states what is included with the project and what’s excluded from the project. This helps to eliminate assumptions between the project management team and the project customer
Project constraints
A constraint is anything that limits the project managers; option. Consider a predetermined budget, deadline, resources, or materials the project manager must use within the project-these are all examples of project constraint.
Project objectives
These are measurable goals that determine a project’s acceptability to the project customer and the overall success of the project. Objectives often include the cost, schedule, technical requirements and quality demands.
Project requirements
These are the demands set by customer, regulations, or the performing organisation that must exist for the project deliverables to be acceptable. Requirements are often prioritised in a number of ways, from “must have” to “should have” to “would like to have”
Project scope
This defines all of the work, and only the required work to complete the project objectives.
Project scope management plan
This project management subsidiary plan controls how the scope will be defined, how the project scope statement will be created, how the WBS will be created, how scope validation will proceed, and how the project scope will be controlled throughout the project.
Prototype
A model of the finished deliverable that allows the stakeholder to see how he final project deliverable may operate.
Requirement documentation
This documentation of what the stakeholders expected in the project defines all of 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, and how changes to the requirements will be approved.
Requirements traceability matrix RTM
Output of collect requirements
Links requirements to objectives, and/or another requirements to ensure the strategic goals are accomplished. Requirements attributes need to be documented.
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 screep
Undocumented, unapproved changes to the project scope.
Scope validation
The formal inspection of the project deliverables, which leads to project acceptance.
Stakeholder analysis
A scope definition process where the project management team interviews the stakeholders and categorises, prioritises, and documents what the project customer wants and needs. The analysis is to determine, quantify, and prioritise the interests of the stakeholders. Stakeholders analysis demands quantification of stakeholder objectives; goals such as “good”, “satisfaction” and “speedy” aren’t quantifiable.
System analysis
A scope definition approach that studies and analyses a systems, its components, and the relationship of the components within the system.
Systems engineering
This project scope statement creation process studies how a system should work, design and creates a system model, and then enacts the working system based on the project’s goals and the customer’s expectations. Systems engineering aims to balance the time and cost of the project in relation to the scope of the project.
Unanimity
A group decision method where everyone must be in agreement.
Value analysis
As with value engineering, this approach examines the functions of the project’s product in relation to the cost of the features and functions. This is where, in some extent, the grade of the product is in relationship to the cost of the product.
Value engineering
This approach to project scope statement creation attempts to find correct level if quality in relation to a reasonable budget for the project deliverable where still achieving an acceptable level of performance of the product.
WBS dictionary
A WBS companion document that defines all of the characteristics of each element within the WBS.
WBS template
A prepopulated WBS for repetitive projects. Previous project’s WBS are often used as templates for current similar projects.
WBS
A deliverable-oriented breakdown of the project scope.
Work package
The smallest item in the WBS
Work performance information
Status of the deliverables; the work that’s been started, finished, or has yet to begin.
Group creativity techniques
Brainstorming, Nominal Group Technique, Multi-criteria decision analysis, Mind maps, affinity diagram
Consensus technique
seeks general agreement about a decision; those who would prefer another option are willing to accept the decision that most members of the group support.
Group decision technique
Input into Collect Requirements, Delphi Technique, Majority, Dictatorship, Plurality, Consensus
Collect Requirements
Inputs:
Scope Management Plan, Requirements Management Plan, Charter, Stakeholder register, Stakeholder Management plan
T&T Interviews Focus Groups Facilitation Workshops Group creativity techniques Group decision making techniques Questionaries & surveys Prototypes Benchmarking Observations Context Diagrams
Outputs
Requirements documentations
Requirements traceability matrix
Define Scope
Planning Inputs: Requirements documentations, Scope Management Plan, Charter, Organisational Process Assets
T&T Expert judgement Product Analysis Alternatives generations Facilitated workshops
Output
Project Scope Statement
Project documentation updates
Project Scope Statement
description of the project scope, major deliverables, constraints and assumptions. It documents the entire scope, including project and product scope. It includes: Product Scope Project Scope Deliverables Acceptance Criteria What is not part of the project Constraints and Assumptions
Create WBS
Planning Inputs Scope Management Plan Project Scope Statement Requirements Documentation Enterprise env factors Organisational Process assets T&T Decomposition Expert judgement
Output
Scope Baseline
Project Documentation Updates
Validate Scope
Monitor & Control
Process of formalising the acceptance of deliverables.
Inputs PMP Requirements Documentation Requirements Traceability Matrix Verified deliverables Work Performance Data
T&T
Inspections
Group decision making techniques
Outputs Accepted deliverables Change requests Work performance data Project documentation updates
Control Scope
Process of monitoring the status of the project& product scope and managing changes to the scope baseline
Inputs PMP Requirements documentation Requirements Traceability Matrix Work performance data Organisational process assets
T&T
Variances analysis
Outputs Work performance information Change requests Project Management Plan updates Project Document update Organisational Process assets updates
Facilitation workshops
T&T for “Collect Requirements”. Workshops bring together stakeholders with different perspectives to talk about product and, ultimately, define requirements.
Multi-criteria decision analysis
This technique utilizes a decision matrix to provide a systematic analytical approach for establishing criteria, such as risk levels, uncertainty, and valuation, to evaluate and rank many ideas.
Mind Map
diagram of ideas and notes used to generate, classify, or record information. It will show branches extending from a central core word.
Benchmarking
T&T for “Collect Requirements”
Comparison of actual or planned practices, such as processes and operations, to those of comparable organisations to identify best practices, generate ideas for improvement and provide a basis for measurement.
Context diagram
T&T for “Collect Requirements
A visual description of the product scope showing a business system ( process, equipment, computer system, etc.). and how people and other systems interact with it.
What document contains acceptance criteria
Requirements Documentation (Output of Collect requirements), Project Scope Statement
