Chapter 5 Flashcards
process of creating a scope management plan that documents how the project and project scope will be defined, validated, and controlled
Plan Scope Management
process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives
Collect Requirements
The process of developing a detailed description of the project and product
Define Scope
Process of subdividing project deliverables and project work into smaller, more manageable components
Create WBS
process of formalizing acceptance of the completed project deliverables
Validate Scope
process of monitoring the status of the project and product scope and managing changes to the scope baseline.
Control Scope
The features and functions that characterize a product, service, or results
Product Scope
the work performed to deliver a product, service, or result the specified feature and functions.
Project Scope
_______ define deliverables at the beginning while ________ are defined over multiple iterations.
1) Predictive
2) Adaptive/Agile
Scope: Three processes repeated at each iteration.
1) Collect requirements
2) Define Scope
3) Create WBS.
validate scope and control scope repeated at each iteration
Adaptive/Agile
Validate scope occurs at each deliverable or phase review and control scope is ongoing
Predictive
Scope Baseline Predictive has:
- approved version of the project scope statement.
- work break down structure (WBS)
- Its associated WBS Dictionary
hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
WBS (Work Break-Down Structure)
lowest level of WBS component that contains planned work and used to group activities where work is scheduled, estimated, monitored, and controlled.
Work Packages
contains highest level of info. Includes the purpose, measurable objectives.
Project Charter
contains detailed description of the scope component. Includes project scope description, deliverables, acceptance criteria, and project exclusions.
Project Scope Statement
Uses decision matrix to provide a systematic analytical approach for establishing criteria in order to refine the project and product scope for the project
Multicriteria decision analysis
defines product and services; describes use, characteristics, and other relevant aspects of what is going to be delivered. Involves: Product Breakdown, Required Analysis, System Analysis, System Engineering, Value analysis, value engineering.
Product Analysis
1) Starts with needs assessment;
2) Then collaborating with business analysis for determining problems/business needs, identify viable solutions; elicit, document, and manage stakeholder requirements; facilitate successful implementation.
3) Requirements closure- transitions the product/service/result to the recipient to measure, monitor, sustain, and realize benefits over time.
Requirements Management Process
Quality policies, methodologies, and standards are implemented on the project
Quality Management Plan
Determines the series of phases that a project passes through from its inception to the end of the project
Project Life Cycle Description
Defines whether waterfall, iterative, adaptive, agile, or hybrid approach will be used.
Development Approach
Component of the PM Plan that describes how a project and product required will be analyzed, documented, and managed. *How requirement activities will be planned, tracked, and reported.
Requirements Management Plan (Business Analysis Plan)
the process of determining, documenting, and managing stakeholder needs and requirements to meet objectives.
* Provides basis for defining the product scope and project scope.
Collect Requirements
Contains info on how the project scope will be defined and developed.
Scope management plan
info on how the project requirements will be collected, analyzed, and documented.
Requirements plan
Used for understanding stakeholder communication requirements and level of stakeholder engagement and assess how to adapt level of stakeholder participation in required activities.
Stakeholder engagement plan
can describe required, desired, and optional criteria for meeting the business needs.
Business case
- organizational culture
- infrastructure
- personnel administration
- Marketplace conditions
Collection Requirement- Enterprise Environmental factors
Policies, procedures, historical info and lessons learned repository.
Organizational Process Assets
Data Gathering
Brainstorming interviews focus groups questionnaires and surveys benchmarking
decision reached whereby the largest block decides, even if majority is not achieved. Used when more than two options.
Plurality
Sole Source decision
Autocratic Decision making
Decision making using decision matrix providing systematic analytical approach for establishing criteria
multicriteria decision making
Allow large numbers of ideas to be classified into groups
Affinity diagram
consolidates ideas created through individual brainstorming session
Mind Mapping
enhances brainstorming with the voting process used to rank the most useful ideas for further brainstorming and prioritization.
Nominal Group Technique
define cross functional requirements and reconcile stakeholder differences
Workshops
Facilitation Skill (JAD)
Joint application design/development- business subject matter experts and dev team to gather requirements and improv software dev processes.
Facilitation Skill (QFD)
Helps Determine critical characteristics for new product development
short/textual descriptions of required functionality often dev during required workshops. Describe stakeholder roles, who benefits from features (role), what stakeholders need to accomplish (Goal), and benefit to stakeholder (Motivation)
User Stories
Visually depicts the product scope by showing a business system (process, equipment, computer system, etc.) and how people and other systems (actors) interact with it.
Context Diagram
Two categories of Requirement Types
business solutions
technical solutions
describe features, functions, characteristics of the product/service/result that will meet the business and stakeholder requirements
Solutions Requirements
describes the behaviors of a product, actions, processes, data, and interactions that the product should execute.
Functional Requirement
supplement functional requirement and describe the environment conditions or qualities required for the product to be effective.
nonfunctional Requirements
describe temporary capabilities, such as data conversion and training requirements needed to transition from the current state as-is state to the desired future state.
Transition and readiness requirements
describes actions, processes, or other conditions the project needs to meet: milestone dates, contractual obligations, constraints, etc.
Project requirements
capture any condition or criteria needed to validate the successful completion of project deliverables or fulfill other project requirements: Tests, certifications, validations, etc.
Quality Requirements
Grid that links product requirements to their origin to the delivery that satisfy them.
Requirements Traceability Matrix
Detailed Project Scope statement includes:
- Product scope statement
- acceptance criteria
- deliverables
- project exclusions
WBS Structure Methods:
- Top-down approach
- Organization specific guidelines
- WBS Template
- Bottom-up approach- used to group subcomponents
Represent verifiable products/services/results
WBS Components
WBS Structures
- Outlined, organizational chart, or other methods identifying hierarchical breakdown.
Project Management team agrees on deliverables and subcomponents before the details of the WBS can be delivered.
Rolling Wave Planning
WBS represents
All product and project work including PM work
Total of work at lowest level should roll up to the higher levels so that nothing is left out nd no extra work is performed.
100 percent rule
the approved version of a scope statement, WBS, and its associated WBS Dictionary, which can be changes only through formal change control procedures and used as a basis for comparison
Scope Baseline
A work break-down structure component below the control account and above the work package with known work content but without detailed scheduled activities.
Planning Package
a document that provides detailed deliverable, activity, and scheduling information about each component in the WBS
WBS Dictionary
the uncontrolled expansion to product or project scope without adjust to time, cost, resources.
Scope Creep
Correlated and contextual information on how the project/product scope are performed compared to scope baseline. Include:
- Categories of change received
- Identified scope variances
- impacts to schedule or cost
- forecast of future scope performance.
Work Performance Information
