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 risk response strategy whereby the project team acts to reduce the probability of occurrence or impact of a risk.






2. A graphical representation of the logical relationships among the project schedule activities.






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






4. An intentional activity that ensures the future performance of the project work is aligned with the project management plan.






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






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






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






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






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






10. A limiting factor that affects the execution of a project - program - portfolio - or process.






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






12. A measure of schedule performance expressed as the difference between the earned value and the planned value.






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






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






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






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






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






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






19. An output of a schedule model that presents linked activities with planned dates - durations - milestones - and resources.






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






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






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






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






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






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






26. A document in which the results of risk analysis and risk response planning are recorded.






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






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






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






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






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






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






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






34. An activity that can be planned and measured and that yields a specific output. (Note: Discrete effort is one of three earned value management [EVM] types of activities used to measure work performance.)






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






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






37. The number of labor units required to complete a schedule activity or work breakdown structure component - often expressed in hours - days - or weeks.






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






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






40. A component of the project or program management plan that describes how the scope will be defined - developed - monitored - controlled - and verified.






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






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






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






44. The person assigned by the performing organization to lead the team that is responsible for achieving the project objectives.






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






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






47. The authorized budget assigned to scheduled work.






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






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






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