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 sequence of activities that represents the longest path through a project - which determines the shortest possible duration.






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






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






4. An estimate of the most probable activity duration that takes into account all of the known variables that could affect performance.






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






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






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






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






9. A critical path method technique for calculating the early start and early finish dates by working forward through the schedule model from the project start date or a given point in time.






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 graphical representation of the logical relationships among the project schedule activities.






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






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






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






15. The application of knowledge - skills - tools - and techniques to a program to meet the program requirements and to obtain benefits and control not available by managing projects individually.






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






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






18. A management control point where scope - budget - actual cost - and schedule are integrated and compared to earned value for performance measurement.






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






20. A component of the project - program - or portfolio management plan that describes how risk management activities will be structured and performed.






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






22. A distinct - scheduled portion of work performed during the course of a project.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






49. A bar chart of schedule information where activities are listed on the vertical axis - dates are shown on the horizontal axis - and activity durations are shown as horizontal bars placed according to start and finish dates.






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