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 methodology that combines scope - schedule - and resource measurements to assess project performance and progress.






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






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






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






5. A schedule compression technique in which activities or phases normally done in sequence are performed in parallel for at least a portion of their duration.






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






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






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






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






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






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






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






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






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






15. A group of potential causes of risk.






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






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






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






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






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






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






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






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






24. A critical path method technique for calculating the late start and late finish dates by working backward through the schedule model from the project end date.






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






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






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






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






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






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






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






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






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






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






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






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






37. A risk that arises as a direct result of implementing a risk response.






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






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






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






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






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






43. The document that describes how the project will be executed - monitored - and controlled.






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






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






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






47. A logical relationship in which a successor activity cannot finish until a predecessor activity has finished.






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






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






50. The authorized budget assigned to scheduled work.