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 grid that shows the project resources assigned to each work package.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






16. The realized cost incurred for the work performed on an activity during a specific time period.






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






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






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






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






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






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






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






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






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






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






27. The amount of time that a schedule activity can be delayed or extended from its early start date without delaying the project finish date or violating a schedule constraint.






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






29. A grid that links product requirements from their origin to the deliverables that satisfy them.






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






31. An enterprise whose personnel are the most directly involved in doing the work of the project or program.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






47. The authorized budget assigned to scheduled work.






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






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






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