Study your flashcards anywhere!

Download the official Cram app for free >

  • Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off

How to study your flashcards.

Right/Left arrow keys: Navigate between flashcards.right arrow keyleft arrow key

Up/Down arrow keys: Flip the card between the front and back.down keyup key

H key: Show hint (3rd side).h key

A key: Read text to speech.a key


Play button


Play button




Click to flip

32 Cards in this Set

  • Front
  • Back
Organizational Process Assets (OSA)
Input to the charter. Assets used by the sponsor in creating the project charter, such as financial procedures that have been detailed in previous projects at the company.
Project Charter
Created by the project sponsor. Within this document is the appointment of the PM and the PM team as well as other necessary internal resources. It also lists out constraints and assuptions, which help form a boundary within which all other planning of the progress takes place.
Statement of Work (SOW)
Created by the project sponsor. Describes, in detail, the characteristics of the output or deliverable of the project.
Enterprise Environmental Factors (EEF)
Environmental pressures that surround the project that may have an affect on the overall deliverables.
Preliminary Scope Statement
Created by PM. 1) Defines what the project must accomplish. 2) Also lists the acceptance criteria necessary to be labelled a success. 3) Details steps to ever change #1 and #2.
Project Management Plan
Created by PM. Details out the entire project life cycle. Signed off by the sponsor after the PM presents it to him. 1) Lists what processes wil be used to execute the work as well the level of implementation and the tools that will be used. 2) Lists what baselines to be used during planning for schedule, cost, quality, and risk. This will be used in tracking and variance analysis. 3) Leads to kickoff launch meeting as next step.
Corrective Action
Make up for current delays by modifying future tasks in order to avoid changing the project plan via creative problem solving or taking advantage of opportunities.
Preventive Action
Make up for potential delays by modifying future tasks in order to speed up the process without affecting the overall project due date.
Change Requests
If Corrective Action cannot resolve an issue, then we will have to resort to this and include a form to fill out as well a full review and a PM recommendation based on this review.
Replaces Statement of Work (SOW) in client organizations (such as Nimbus). This provides the key information to develop the project charter.
Project Management Information System (PMIS)
An organization's way of automating project information.
Earned Value Management
Data from previous plans used to help analyze a new project plan.
Change Control System
Formal set of procedures for submitting, tracking, and approving changes to project plans and deliverables.
Configuration Management System
Identifies and documents characteristics about a particular project and helps control any changes to these characteristics. Might even include a committee who oversees this system in larger companies.
Approved Defect Repair
Upon inspection of work in a project, a repair may be necessary and this will be approved at this rate. (p. 40)
Approved Preventative Action
Reduces the probability of a risk event occurring. (p.40)
Approved Corrective Action
Brings future expected performance in line with the Project Management Plan. (p.40)
Approved Change Request
Expansion or contraction of the project scope, budget, schedule, or Project Management Plan. (p. 40)
Validated Defect Repair
After a defect has been approved, it is communicated as validated and will be documented as such. (p. 41)
Requested Change
A request to change scope, cost, schedule, or the Project Management Plan. Must go through the approval process in integrated change control. (p. 41)
Work Performance Information
Collection of data to see how the project is going. Can consist of the schedule progress, deliverables, cost, and other information. (p. 41)
Change Control Systems
Notes on how changes will be addressed in a project. (p. 42)
Earned Value
Compares where we are now in a project to where we planned to be. Can be broken down into Cost Variances and Schedule Variances if needed. (p. 43)
Our projection for anticipated situations that could affect our project. (p. 43)
Project Schedule
Created after the WBS is created.
Subdiving major deliverables into smaller deliverables, thus making it easier to estimate cost and duration of performing tasks.
3 most common reasons project plans get revised are...
1) crashing to meet end dates
2) trade-off decisions revolving manpower, cost, or scheduling
3) adjusting resources
Life cycle costs
Life-cycle costs include; production, construction, operation and maintenance, retirement and phase-out costs. Life-cycle costs are used in the evaluation of alternatives.
Strategic Plan
Created by project initiators in the Initiation phase. Describes long term goals.
Scope Verification Process
When the senior project managers sign off on the project deliverables. Done during the monitoring and controlling phase.
Lessons Learned document
Created by all stakeholders after the project is complete, not just the PM team.
Progressive Elaboration
Technique in that the work that is closer to us is planned in detail and the work that is further from us is more general and gets more specific as we progress in the project.