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. A hierarchical representation of resources by category and type.






2. A component of the human resource plan that describes when and how team members will be acquired and how long they will be needed.






3. The level of an organization's ability to deliver the desired strategic outcomes in a predictable - controllable - and reliable manner.






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






5. The series of phases that represent the evolution of a product - from concept through delivery - growth - maturity - and to retirement.






6. The knowledge gained during a project which shows how project events were addressed or should be addressed in the future for the purpose of improving future performance






7. A calendar that identifies working days and shifts that are available for scheduled activities.






8. The uncontrolled expansion to product or project scope without adjustments to time - cost - and resources.






9. 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.)






10. The amount of time that a schedule activity can be delayed without delaying the early start date of any successor or violating a schedule constraint.






11. A technique for estimating the duration or cost of an activity or a project - using historical data from a similar activity or project.






12. A component of the project or program management plan that establishes the activities for developing - monitoring - and controlling the project or program.






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






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






15. An individual - group - or organization who may affect - be affected by - or perceive itself to be affected by a decision - activity - or outcome of a project - program - or portfolio.






16. A group of related schedule activities aggregated and displayed as a single activity.






17. A component of a project or program management plan that describes how costs will be planned - structured - and controlled.






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






19. Plans - processes - policies - procedures and knowledge bases specific to and used by the performing organization.






20. The sum of all budgets established for the work to be performed.






21. A dependency between two activities - or between an activity and a milestone.






22. A review at the end of a phase in which a decision is made to continue to the next phase - to continue with modification - or to end a project or program.






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






24. A representation of the plan for executing the project's activities including durations - dependencies and other planning information - used to produce a project schedule along with other scheduling artifacts.






25. A technique used to shorten the schedule duration for the least incremental cost by adding resources.






26. An estimate expressed as a percent of the amount of work that has been completed on an activity or a work breakdown structure component.






27. A hierarchical representation of the project organization - which illustrates the relationship between project activities and the organizational units that will perform those activities.






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






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






30. 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.






31. A method used to estimate the minimum project duration and determine the amount of scheduling flexibility on the logical network paths within the schedule model.






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






33. A technique used to estimate cost or duration by applying an average of optimistic - pessimistic - and most likely estimates when there is uncertainty with the individual activity estimates.






34. A risk response strategy whereby the project team acts to reduce the probability of occurrence or impact of a risk.






35. A risk response strategy whereby the project team shifts the impact of a threat to a third party - together with ownership of the response.






36. An iterative planning technique in which the work to be accomplished in the near term is planned in detail - while the work in the future is planned at a higher level.






37. Any unique and verifiable product - result - or capability to perform a service that is required to be produced to complete a process - phase - or project.






38. A method of estimating project duration or cost by aggregating the estimates of the lower-level components of the work breakdown structure (WBS).






39. In the critical path method - the latest possible point in time when the uncompleted portions of a schedule activity can start based on the schedule network logic - the project completion date - and any schedule constraints.






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






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






42. The process of optimizing the mix of portfolio components to further the strategic objectives of the organization.






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






44. A risk response strategy whereby the project team acts to eliminate the threat or protect the project from its impact.






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






46. A logical relationship in which a successor activity cannot finish until a predecessor activity has started.






47. The amount of time whereby a successor activity can be advanced with respect to a predecessor activity.






48. A hierarchical representation of risks that is organized according to risk categories.






49. A numbering system used to uniquely identify each component of the work breakdown structure.






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