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 measure of schedule efficiency expressed as the ratio of earned value to planned value.






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






3. A risk that would have a positive effect on one or more project objectives.






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






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






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






7. The expected cost to finish all the remaining project work.






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






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






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






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






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






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






14. Conditions - not under the immediate control of the team - that influence - constrain - or direct the project - program - or portfolio.






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






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






17. The authorized budget assigned to scheduled work.






18. A relationship in which a schedule activity has more than one successor.






19. A group of potential causes of risk.






20. A component of the project - program - or portfolio management plan that describes how - when - and by whom information will be administered and disseminated.






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






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






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






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






25. A projection of the amount of budget deficit or surplus - expressed as the difference between the budget at completion and the estimate at completion.






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






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






28. A bar chart of schedule information where activities are listed on the vertical axis - dates are shown on the horizontal axis - and activity durations are shown as horizontal bars placed according to start and finish dates.






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






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






31. A set of procedures that describes how modifications to the project deliverables and documentation are managed and controlled.






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






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






34. An enterprise whose personnel are the most directly involved in doing the work of the project or program.






35. A calendar that identifies the working days and shifts upon which each specific resource is available.






36. An intentional activity that ensures the future performance of the project work is aligned with the project management plan.






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






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






39. A management control point where scope - budget - actual cost - and schedule are integrated and compared to earned value for performance measurement.






40. A logical relationship in which a successor activity cannot start until a predecessor activity has finished.






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






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






43. A component of the project or program management plan that describes how the scope will be defined - developed - monitored - controlled - and verified.






44. A logical relationship in which a successor activity cannot start until a predecessor activity has started.






45. A logical relationship in which a successor activity cannot finish until a predecessor activity has finished.






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






47. A condition or capability that is required to be present in a product - service - or result to satisfy a contract or other formally imposed specification.






48. The work performed to deliver a product - service - or result with the specified features and functions.






49. A collection of logically related project activities that culminates in the completion of one or more deliverables.






50. A diagramming and calculation technique for evaluating the implications of a chain of multiple options in the presence of uncertainty.