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 authorized budget assigned to scheduled work.






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






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






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






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






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






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






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






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






10. A process whereby modifications to documents - deliverables - or baselines associated with the project are identified - documented - approved - or rejected.






11. An activity that logically comes before a dependent activity in a schedule.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






33. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






34. A process used to investigate or analyze the output of the schedule model in order to optimize the schedule






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






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






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






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






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






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






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






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






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






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






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






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






47. An uncertain event or condition that - if it occurs - has a positive or negative effect on one or more project objectives.






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






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






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