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 logical relationship in which a successor activity cannot finish until a predecessor activity has finished.






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






3. A set of conditions that is required to be met before deliverables are accepted.






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






5. A formally chartered group responsible for reviewing - evaluating - approving - delaying - or rejecting changes to the project and for recording and communicating such decisions.






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






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






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






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






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






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






12. A calendar that identifies working days and shifts that are available for scheduled activities.






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






14. An activity that does not produce definitive end products and is measured by the passage of time. (Note: Level of effort is one of three earned value management [EVM] types of activities used to measure work performance.)






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






33. A component of the project or program management plan that describes how a team will acquire goods and services from outside of the performing organization.






34. The authorized budget assigned to scheduled work.






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






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






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






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






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






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






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






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






43. A measure of the cost performance that is required to be achieved with the remaining resources in order to meet a specified management goal - expressed as the ratio of the cost to finish the outstanding work to the remaining budget.






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






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






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






47. A risk that would have a negative effect on one or more project objectives.






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






49. The description of the project scope - major deliverables - assumptions - and constraints.






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