5 - Scope Management Flashcards
8/80 Rule
A planning heuristic for creating the WBS.
Creating WBS must take no more than 80 hours, no fewer than 8 hours.
Active observation
Observer interacts with the worker to ask questions and understand each step of the work being completed. Observer can even take part to better understand.
Affinity Diagrams
Use it when stakeholders create a large # of ideas.
Can cluster similar number ideas together for further analysis.
Alternatives Generation
Scope definition process of finding alternative solutions for the customer while considering the customer’s satisfaction, cost, how the customer may use the product in operations.
Autocratic
Decision making process where one person decides for whole group.
Brainstorming
Encourages participants to generate as many ideas about project requirements. No idea is judged or dismissed.
Change control system (CCS)
Defines how changes to scope are managed.
Documented in scope management plan.
Change management plan
Subsidiary plan defines how changes will be allowed and managed within the project.
Code of accounts
Numbering system for each item in the WBS.
E.g. regulations chapter, section, etc.
Configuration management plan
Subsidiary plan - defines how changes to the features and functions of the project deliverables will be monitored and controlled within the project.
Context diagram
Shows relationship between elements of an environment.
e.g. would show networks, servers, workstation, and people that interact with the elements in that environment.
Focus Groups
Moderator-lead requirements collection method to elicit stakeholder requirements.
Functional Analysis
Study of functions wihtin a system, project, or product the project will be creating.
Studies the goal of the product, how it will be used, expectations the customer has/.
May also consider cost of product in operations (known as life cycle costing).
Funding limit
Predetermined budget to project scope.
Could be a qualifier (e.g. +/- 10%)
Interviews
1-1 requirements collection method.
Majority
Voting process - greater than 50% votes wins.
Mind mapping
Maps ideas to show relationships among requirements and differences between requirements.
Nominal group technique
Generate as many ideas as possible, then ranked by voting process.
Passive observation
Observer records information about work without interrupting worker.
aka invisible observer.
Plurality
Voting method where largest group makes decision (even if less than 50% total vote).
Like a minority government.
Product acceptance criteria
A scope statement component - focuses on the conditions and processes that are required for formal acceptance of the product.
Product breakdown
Scope definition technique:
Breaks down product into hierarchal structure, much like WBC breaks down project scope.
Project scope description
Narrative description of what the project is creating as a deliverable for the customer.
Product Scope
Defines the product or service that will come out as a result of completing the project. Defines features and functions that characterize the product.
Project assumptions
A factor in planning process that is held to be true but not proven.
Project boundaries
Clearly states what is included/excluded in the project.
Helps eliminate assumptions.
Project contraints
Limits PMs options. e.g. cost limit 10k.
Project objectives
Measurable goals that determine project acceptability to the project’s customer and overall success of project. e.g. cost, schedule, etc.
Project requirements
Demands set by customer, regulations, or the performing organization that must exist for the projects deliverables to be acceptable.
Often prioritized (must, should, would like)
Project scope
Defines all of the work, and only the required work, to complete the project objectives.
Project scope management plan
Subsidiary PM plan.
Controls how scope will be defined, scope statement creates, WBS created, scope validation will proceed, and how scope controlled.
Requirements documentation
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
Subsidiary plan defines how changes to the project requirements will be tracked, and how changes to the requirements will be approved.
Requirements Traceability Matrix (RTM)
Table that maps all requirements throughout project all the way to their completion (lots of fields to track status).
Schedule Milestones
Specific dates where phases should be completed.
Often a project constraint.
Scope creep
undocumented, unapproved changes to the project scope.
Scope validation
Formal inspection of project deliverables.
Leads to project acceptance.
Stakeholder analysis
Scope definition process - PM team interviews the stakeholders and categorizes, prioritizes, and documents what the customer needs.
Demands quantification of stakeholder objectives. e.g. goals such as “good” “speedy” are not quantifiable.
Systems analysis
Scope definition approach that studies and analyzes a system, its components, and the relatoinship of components within a system.
Systems engineering
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 teh project’s goals and customer expectations. Systems engineering aims to balance the time and cost of the project in relation to the scope of the projcet.
Unanimity
Group decision. All must agree
e.g. court ruling.
Value analysis
Examines functions of the project’s product in relation to the cost of the features and functions. Where the grade of the product is in relatoinship to the cost of the product.
Value engineering
Approach to project scope statement creation. Attempts to find the correct level of quality in relation to a reasonable budget for the project deliverable while still achieving an acceptable level of performance of the product.
WBS dictionary
Companion document to the WBS. Defines all characteristics of each element within the WBS.
WBS Template
prepopulated WBS for repetitive projects.
Work Breakdown Structure (WBS)
Deliverables-oriented breakdown of the project’s scope.
Work Package
Smallest item in the WBS.
Work performance information
Status of the deliverable: work that has been started, finished, or yet to begin.
