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 hierarchical representation of resources by category and type.






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






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






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






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






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






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






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






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






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






11. A risk response strategy whereby the project team shifts the impact of a threat to a third party - together with ownership of the response.






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






13. A technique for estimating the duration or cost of an activity or a project - using historical data from a similar activity or project.






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






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






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






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






18. A group of potential causes of risk.






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






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






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






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






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






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






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






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






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






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






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






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






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






32. The amount of budget deficit or surplus at a given point in time - expressed as the difference between the earned value and the actual cost.






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






34. In the critical path method - the latest possible point in time when the uncompleted portions of a schedule activity can start based on the schedule network logic - the project completion date - and any schedule constraints.






35. Any unique and verifiable product - result - or capability to perform a service that is required to be produced to complete a process - phase - or project.






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






37. An activity that logically comes before a dependent activity in a schedule.






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






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






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






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






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






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






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






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






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






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






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






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






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