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 risks that is organized according to risk categories.






2. A critical path method technique for calculating the late start and late finish dates by working backward through the schedule model from the project end date.






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






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






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






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






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






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






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






10. An earned value management technique used to indicate performance trends by using a graph that displays cumulative costs over a specific time period.






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






12. A critical path method technique for calculating the early start and early finish dates by working forward through the schedule model from the project start date or a given point in time.






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






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






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






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






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






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






19. A group of potential causes of risk.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






37. A hierarchical representation of resources by category and type.






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






39. A technique for determining the cause and degree of difference between the baseline and actual performance.






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






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






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






43. The application of knowledge - skills - tools - and techniques to a program to meet the program requirements and to obtain benefits and control not available by managing projects individually.






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






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






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






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






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






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






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