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 numbering system used to uniquely identify each component of the work breakdown structure.






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






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






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






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






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






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






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






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






10. A group of potential causes of risk.






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






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






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






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






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






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






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






18. A group of related projects - subprograms and program activities that are managed in a coordinated way to obtain benefits not available from managing them individually.






19. A method used to estimate the minimum project duration and determine the amount of scheduling flexibility on the logical network paths within the schedule model.






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






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






22. A component of the project or program management plan that establishes the activities for developing - monitoring - and controlling the project or program.






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






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






25. An estimate of the shortest activity duration that takes into account all of the known variables that could affect performance.






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






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






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






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






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






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






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






33. An estimate of the longest activity duration - which takes into account all of the known variables that could affect performance.






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






35. A collection of logically related project activities that culminates in the completion of one or more deliverables.






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






37. Plans - processes - policies - procedures and knowledge bases specific to and used by the performing organization.






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 management control point where scope - budget - actual cost - and schedule are integrated and compared to earned value for performance measurement.






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






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






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






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






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






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






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






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






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






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






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