The Project Management Plan (PMP) 2.1

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/21

encourage image

There's no tags or description

Looks like no tags are added yet.

Last updated 2:32 PM on 6/9/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai

No analytics yet

Send a link to your students to track their progress

22 Terms

1
New cards
Project Management Plan (PMP)
The formal, approved document that outlines how a project will be executed, monitored, controlled, and closed.
2
New cards
Scope Creep
The gradual, uncontrolled expansion of a project’s scope.
3
New cards
Scope Management Plan
A document that addresses how the scope of the project will be managed throughout the project life cycle. This can also be known as the scope document.
4
New cards
Business Requirements
A type of requirement that refers to the needs of the sponsoring organization, always from a management perspective.
5
New cards
Deliverables
The tangible output a project provides.
6
New cards
Development Requirement
A type of requirement that focuses on the limits on the process when creating a deliverable, such as budget.
7
New cards
Functional Requirements
A type of requirement that describes the characteristics of the deliverable in ordinary non-technical language.
8
New cards
Non-Functional Requirements
A type of requirement that specifies criteria that can be used to judge the final product or service that your project delivers.
9
New cards
Performance Requirement
A type of requirement that states how well the requirement must perform after it is completed.
10
New cards
Regulatory Requirements
A type of requirement that may be internal or external and include restrictions, licenses, and laws applicable to a product or business that are imposed by the government.
11
New cards
Requirements
Describe the characteristics of the deliverable, whether it is a product or a service.
12
New cards
Requirements Traceability Matrix
A document that provides a way to track all requirements that have been agreed upon to make sure nothing gets lost or forgotten.
13
New cards
Technical Requirements
A type of requirement that emerges from the functional requirements to specify how the system needs to be designed and implemented to provide required functionality and fulfill required operational characteristics.
14
New cards
User Requirements
Requirements from the perspective of the end-user experience.
15
New cards
Acceptance Criteria
A list of things that define what conditions must be met for a product, service, or deliverables to be considered complete and acceptable to the client or stakeholder. It also addresses the responsibilities of each stakeholder.
16
New cards
Scope Validation
A check-in to ensure the deliverables meet requirements, often identified in the scope management document.
17
New cards
Flexible Backlog
A way to break down work in Agile, and a living to-do list for the project where instead of mapping out every single task, the backlog holds all the features, ideas, and user stories the team might work on.
18
New cards
Hierarchical Decomposition
A method to break down large projects into hierarchical subcomponents to simplify and better understand what needs to be done to complete a project.
19
New cards
Work Breakdown Structure (WBS)
A process where the project deliverables are broken into smaller, manageable work components.
20
New cards
100% Rule
States that the WBS must contain all of the work necessary to complete the project, nothing more and nothing less.
21
New cards
Baselining
A fixed, agreed upon reference point for a project.
22
New cards
Work Package
The groupings of project work, usually defined by a major deliverable and its sub deliverables.