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 shifts the impact of a threat to a third party - together with ownership of the response.






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






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






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






5. A technique used for dividing and sub-dividing the project scope and project deliverables into smaller - more manageable parts.






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






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






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






9. A hierarchical representation of resources by category and type.






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






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






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






13. A response to a threat that has occurred - for which a prior response had not been planned or was not effective.






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






15. An estimate of the shortest activity duration that takes into account all of the known variables that could affect performance.






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






17. An earned value management technique used to indicate performance trends by using a graph that displays cumulative costs over a specific time period.






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






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






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






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






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






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






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






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






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






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






28. The authorized budget assigned to scheduled work.






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






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






31. The knowledge gained during a project which shows how project events were addressed or should be addressed in the future for the purpose of improving future performance






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






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






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






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






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






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






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






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






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






41. A risk response strategy whereby the project team acts to eliminate the threat or protect the project from its impact.






42. The work performed to deliver a product - service - or result with the specified features and functions.






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






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






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






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






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






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






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






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