Test your basic knowledge |

PMI Project Management Vocab

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. The expected cost to finish all the remaining project work.






2. The approved version of a scope statement - work breakdown structure (WBS) - and its associated WBS dictionary - which can be changed only through formal change control procedures and is used as a basis for comparison.






3. The approved version of a work product that can be changed only through formal change control procedures and is used as a basis for comparison.






4. In the critical path method - the earliest possible point in time when the uncompleted portions of a schedule activity can finish based on the schedule network logic - the data date - and any schedule constraints.






5. A risk that would have a negative effect on one or more project objectives.






6. A schedule method that allows the project team to place buffers on any project schedule path to account for limited resources and project uncertainties.






7. A relationship in which a schedule activity has more than one predecessor.






8. Any activity on the critical path in a project schedule.






9. The centralized management of one or more portfolios to achieve strategic objectives.






10. A person or group who provides resources and support for the project - program - or portfolio - and is accountable for enabling success.






11. A component of the project - program - or portfolio management plan that describes how risk management activities will be structured and performed.






12. The document that describes how the project will be executed - monitored - and controlled.






13. A temporary endeavor undertaken to create a unique product - service - or result.






14. The description of the project scope - major deliverables - assumptions - and constraints.






15. The amount of budget deficit or surplus at a given point in time - expressed as the difference between the earned value and the actual cost.






16. An intentional activity to modify a nonconforming product or product component.






17. A dependent activity that logically comes after another activity in a schedule.






18. A component of the project or program management plan that describes how a team will acquire goods and services from outside of the performing organization.






19. A factor in the planning process that is considered to be true - real - or certain - without proof or demonstration.






20. A set of conditions that is required to be met before deliverables are accepted.






21. A measure of schedule efficiency expressed as the ratio of earned value to planned value.






22. An output of a schedule model that presents linked activities with planned dates - durations - milestones - and resources.






23. A document that provides detailed deliverable - activity - and scheduling information about each component in the work breakdown structure.






24. A document in which the results of risk analysis and risk response planning are recorded.






25. A significant point or event in a project - program - or portfolio.






26. A graphical representation of the logical relationships among the project schedule activities.






27. The amount of time that a schedule activity can be delayed or extended from its early start date without delaying the project finish date or violating a schedule constraint.






28. Projects - programs - subportfolios - and operations managed as a group to achieve strategic objectives.






29. A technique in which start and finish dates are adjusted based on resource constraints with the goal of balancing demand for resources with the available supply.






30. An activity that does not produce definitive end products and is measured by the passage of time. (Note: Level of effort is one of three earned value management [EVM] types of activities used to measure work performance.)






31. A formally chartered group responsible for reviewing - evaluating - approving - delaying - or rejecting changes to the project and for recording and communicating such decisions.






32. A response to a threat that has occurred - for which a prior response had not been planned or was not effective.






33. A technique used for dividing and sub-dividing the project scope and project deliverables into smaller - more manageable parts.






34. A management structure that standardizes the project-related governance processes and facilitates the sharing of resources - methodologies - tools - and techniques.






35. A risk response strategy whereby the project team decides to acknowledge the risk and not take any action unless the risk occurs.






36. A component of the project or program management plan that describes how the roles and responsibilities - reporting relationships - and staff management will be addressed and structured.






37. An estimate of the most probable activity duration that takes into account all of the known variables that could affect performance.






38. A formal proposal to modify any document - deliverable - or baseline.






39. A grid that shows the project resources assigned to each work package.






40. A group of potential causes of risk.






41. An event or situation that indicates that a risk is about to occur.






42. An estimating technique in which an algorithm is used to calculate cost or duration based on historical data and project parameters.






43. A methodology that combines scope - schedule - and resource measurements to assess project performance and progress.






44. A grid for mapping the probability of each risk occurrence and its impact on project objectives if that risk occurs.






45. A component of the project or program management plan that describes how requirements will be analyzed - documented and managed.






46. The approved version of a schedule model that can be changed only through formal change control procedures and is used as a basis for comparison to actual results.






47. A limiting factor that affects the execution of a project - program - portfolio - or process.






48. The realized cost incurred for the work performed on an activity during a specific time period.






49. The measure of work performed expressed in terms of the budget authorized for that work.






50. A distinct - scheduled portion of work performed during the course of a project.