Overall Flashcards
Change Management Plan
part of the PMP, describes how change requests throughout the project will be formally authorized and incorporated.
Configuration Management Plan
Part of the PMP, describes how info about the items of the project (and which items) will be recorded and updated so that the result of the project remains consistent.
Performance Measurement Baseline
Part of the PMP, an integrated scope-schedule-cost plan for the project work against which project execution is compared to measure and manage performance.
Project life cycle
part of the PMP, describes the series of phases that a project passes thru from initiation to closing.
Development approach
part of the PMP, describes the product, services or result development approach, such as predictive, iterative, agile, or hybrid.
Management reviews
part of the PMP, identifies the points in the project when the PM and relevant SHs will review project progress to determine if performance is as expected, or if preventive or corrective actions are necessary.
Brainstorming
Data gathering technique - used to identify a list of ideas in a short period of time. Conducted in a group environment, led by a facilitator. 2 parts: idea generation, and analysis.
Focus groups
Data gathering technique - brings together SHs and subject matter experts to learn about perceived project risk, success criteria, etc. in a more conversational way than one-on-one
Interviews
Data gathering technique - used to obtain info from SHs on high level requirements, assumptions/constraints, approval criteria, etc. by talking directly to them.
Checklists
data gathering technique - list of items, actions, or points to be considered. Often used as a reminder of various items.
Project Management Information System (PMIS)
provides access to IT software tools such as scheduling software, work authorization systems, configuration mgmt systems, info collection & distribution systems, as well as interfaces to other online automated systems such as corporate knowledge base repositories.
Work performance data
the raw observations and measurements identified during activities being performed. Data is gathered thru work execution and passed to the controlling processes for further execution.
Work performance info
the performance data collected from various controlling processes, analyzed in context and integrated based on relationships across areas.
work performance reports
the physical or electronic representation of work performance info, compiled into project documents, intended to generate decisions or raise issues, actions, or awareness.
Change request
a formal proposal to modify any document, deliverable, or baseline. Can include:
- Corrective action
- Preventive action
- Defect repair
- Updates to project documents, plans, etc.
Explicit knowledge
knowledge that can be readily codified using words, pictures, and numbers.
Tacit knowledge
knowledge that is personal and difficult to express, such as beliefs, insights, experience, and “know-how”
Issue Log
Project document where all project issues are recorded and tracked. Includes:
- issue type
- who raised the issue and when
- description
- priority
- who is assigned to the issue
- target resolution date
- status
- final resolution
assumption log
project document that contains info about all assumptions and constraints identified as affecting the project.
lessons learned register
Project document where lessons learned are recorded throughout the project life cycle. It is an output of the Manage Project Knowledge process.
Alternatives analysis
Data analysis technique used to select the corrective actions or combination of corrective and preventive actions to implement when a deviation occurs.
Trend analysis
Data analysis technique used to forecast future performance based on past results.
Variance analysis
Data analysis technique used to analyze the difference (or variance) between planned and actual performance. Can include duration estimates, cost estimates, resource utilization, resource rates, tech performance, etc.
Cost-Benefit analysis
data analysis technique used to help determine the best corrective action in terms of cost in case of project deviations.
Earned value analysis
Data analysis technique used to provide an integrated perspective on scope, schedule, and cost performance.
change log
project document used to record all changes that occur during a project.
regression analysis
Data analysis technique used analyze the interrelationships between different project variables that contributed to the project outcomes to improve performance on future projects
Product backlog
Used in an adaptive project life cycle, where the scope is decomposed into a set of requirements and work to be performed, sometimes referred to as a product backlog.
Scope Management Plan
component of the PMP that describes how the scope will be defined, developed, monitored, controlled, and validated. Includes 4 components:
- Process for preparing a scope statement
- process that enables the creation of a WBS from the detailed scope statement
- process that establishes how the scope baseline will be approved and maintained
- Process that specifies how formal acceptance of the completed deliverables will be obtained
Requirements Mgmt Plan
Component of the PMP that describes how project and product requirements will be analyzed, documented, and managed.
Benchmarking
Data gathering technique that involves comparing actual or planned practices or the project’s quality standards to those of comparable projects/organizations to identify best practices, generate ideas for improvement, and provide a basis for measuring performance.
Voting
Decision-making technique that can take 3 forms:
- Unanimity - decision reached whereby everyone agrees on a single course of action
- Majority - decision reached with support of more than 50% of members
- Plurality - decision reached whereby the largest block in a group decides, even if a majority is not achieved.
Autocratic decision making
Decision-making technique where one individual takes responsibility for deciding for the group
Multicriteria decision analysis
Decision-making technique that uses a decision matrix to provide a systematic analytical approach for establishing criteria such as risk levels, uncertainty, and validation, to evaluate and rank many ideas.
Affinity diagram
Data representation technique that allows for large numbers of ideas to be classified into groups for review and analysis
Mind Mapping
Data representation technique that consolidates ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas.
Context diagram
Technique that visually depicts the product scope by showing a business system and how people and other systems interact with it. Shows inputs to the business system, the actor(s) providing the inputs, the outputs from the system, and the actor(s) receiving the outputs.
Prototypes
A method of obtaining early feedback on requirements by providing a model of the expected product before actually building it.
Storyboarding
a prototyping technique showing sequence or navigation through a series of images or illustrations.
Requirements documentation
An output from the ‘Collect Requirements’ process that describes how individual requirements meet the business need for the project. Can include classifications such as:
- Business requirements
- Stakeholder requirements
- solution requirements
- Transition and readiness requirements
- Project requirements
- Quality requirements
Requirements Traceability Matrix
An output of the ‘Collect Requirements’ process, it is a grid that links product requirements from their origin to the deliverables that satisfy them. Helps to ensure that each requirement adds business vlaue by linking it to the business and project objectives. May include attributes such as:
- Unique identifier
- textual description of the requirement
- rationale for inclusion
- owner
- source
- priority
- version
- current status & status date
Product Analysis
Tool/Technique for ‘Define Scope’ process - includes asking questions about a product or service and forming answers to describe the use, characteristics, and other relevant aspects of what is going to be delivered. Examples include:
- product breakdown
- requirements analysis
- systems analysis
- systems engineering
- Value analysis
- value engineering
Project Scope Statement
Output from the ‘Define Scope’ process - is the description of the project scope, major deliverables, and exclusions. Documents the entire scope, including project and product scope. Includes:
- Product scope description - progressively elaborates the characteristics of the product described in the project charter
- Deliverables - unique and verifiable product or service
- Acceptance criteria - set of conditions to be met before a deliverable is accepted.
- Project Exclusions
Work Breakdown Structure (WBS)
a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives. WBS is comprised of work packages.