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 amount of time that a schedule activity can be delayed without delaying the early start date of any successor or violating a schedule constraint.






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






3. A technique used to shorten the schedule duration without reducing the project scope.






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






5. The sequence of activities that represents the longest path through a project - which determines the shortest possible duration.






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






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






8. A dependent activity that logically comes after another activity in a schedule.






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






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






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






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






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






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






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






16. A component of the human resource plan that describes when and how team members will be acquired and how long they will be needed.






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






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






19. A schedule compression technique in which activities or phases normally done in sequence are performed in parallel for at least a portion of their duration.






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






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






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






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






24. An activity that can be planned and measured and that yields a specific output. (Note: Discrete effort is one of three earned value management [EVM] types of activities used to measure work performance.)






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






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






27. A component of the project - program - or portfolio management plan that describes how - when - and by whom information will be administered and disseminated.






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






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






30. The application of knowledge - skills - tools - and techniques to project activities to meet the project requirements.






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






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






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






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






35. The iterative process of increasing the level of detail in a project management plan as greater amounts of information and more accurate estimates become available.






36. A risk response strategy whereby the project team acts to eliminate the threat or protect the project from its impact.






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






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






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






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






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






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






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






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






45. An event or situation that indicates that a risk is about to occur.






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






47. A group of potential causes of risk.






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 management structure that standardizes the project-related governance processes and facilitates the sharing of resources - methodologies - tools - and techniques.