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 person or group who provides resources and support for the project - program - or portfolio - and is accountable for enabling success.






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






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






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






5. The number of labor units required to complete a schedule activity or work breakdown structure component - often expressed in hours - days - or weeks.






6. A measure of the cost efficiency of budgeted resources expressed as the ratio of earned value to actual cost.






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






8. An estimate of the shortest activity duration that takes into account all of the known variables that could affect performance.






9. A group of related projects - subprograms and program activities that are managed in a coordinated way to obtain benefits not available from managing them individually.






10. The series of phases that a project passes through from its initiation to its closure.






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






12. A grid that links product requirements from their origin to the deliverables that satisfy them.






13. The amount of time whereby a successor activity is required to be delayed with respect to a predecessor activity.






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






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






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






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






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






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






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






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






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






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






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






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






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






27. The expected total cost of completing all work expressed as the sum of the actual cost to date and the estimate to complete.






28. A risk that arises as a direct result of implementing a risk response.






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






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






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






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






33. An intentional activity that realigns the performance of the project work with the project management plan.






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






35. A measure of schedule performance expressed as the difference between the earned value and the planned value.






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






37. A component of the project or program management plan that describes how an organization's quality policies will be implemented.






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






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






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






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






42. A point in time when the status of the project is recorded.






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






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






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






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






47. The person assigned by the performing organization to lead the team that is responsible for achieving the project objectives.






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






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






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