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 condition or capability that is required to be present in a product - service - or result to satisfy a contract or other formally imposed specification.






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






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






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






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






6. An individual - group - or organization who may affect - be affected by - or perceive itself to be affected by a decision - activity - or outcome of a project - program - or portfolio.






7. A logical relationship in which a successor activity cannot start until a predecessor activity has started.






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






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






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






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






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






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






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






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






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






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






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






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






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. A component of a project or program management plan that describes how costs will be planned - structured - and controlled.






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






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






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






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






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






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






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






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






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






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






32. A measure of the cost efficiency of budgeted resources expressed as the ratio of earned value to actual cost.






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






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






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






36. A group of potential causes of risk.






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






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






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






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






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






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






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






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






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






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






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






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






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






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