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. An activity that logically comes before a dependent activity in a schedule.






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






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






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






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






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






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






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






9. A hierarchical representation of risks that is organized according to risk categories.






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






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






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






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






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






15. A significant point or event in a project - program - or portfolio.






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






17. The approved version of a work product that can be changed only through formal change control procedures and is used as a basis for comparison.






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






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






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






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






22. A technique used to estimate cost or duration by applying an average of optimistic - pessimistic - and most likely estimates when there is uncertainty with the individual activity estimates.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






38. A risk response strategy whereby the project team decides to acknowledge the risk and not take any action unless the risk occurs.






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






40. A schedule method that allows the project team to place buffers on any project schedule path to account for limited resources and project uncertainties.






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






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






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






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






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






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






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






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






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






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