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 component of the project or program management plan that describes how requirements will be analyzed - documented and managed.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






18. The amount of budget deficit or surplus at a given point in time - expressed as the difference between the earned value and the actual cost.






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






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






21. The authorized budget assigned to scheduled work.






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






23. A schedule method that allows the project team to place buffers on any project schedule path to account for limited resources and project uncertainties.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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 technique for determining the cause and degree of difference between the baseline and actual performance.






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






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






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






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






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






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