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 technique for estimating the duration or cost of an activity or a project - using historical data from a similar activity or project.






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






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






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






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






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






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






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






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






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






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






12. A component of the project or program management plan that describes how the roles and responsibilities - reporting relationships - and staff management will be addressed and structured.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






46. A technique used for constructing a schedule model in which activities are represented by nodes and are graphically linked by one or more logical relationships to show the sequence in which the activities are to be performed.






47. The approved version of a schedule model that can be changed only through formal change control procedures and is used as a basis for comparison to actual results.






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






49. An activity where effort is allotted proportionately across certain discrete efforts and not divisible into discrete efforts. (Note: Apportioned effort is one of three earned value management [EVM] types of activities used to measure work performance






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