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 logical relationship in which a successor activity cannot finish until a predecessor activity has started.






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






3. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






5. A projection of the amount of budget deficit or surplus - expressed as the difference between the budget at completion and the estimate at completion.






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






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






8. A distinct - scheduled portion of work performed during the course of a project.






9. A process used to investigate or analyze the output of the schedule model in order to optimize the schedule






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






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






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






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






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






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






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






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






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






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






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






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






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






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






24. A diagramming and calculation technique for evaluating the implications of a chain of multiple options in the presence of uncertainty.






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






26. The expected total cost of completing all work expressed as the sum of the actual cost to date and the estimate to complete.






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






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






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






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






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






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






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






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






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






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






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






38. An event or situation that indicates that a risk is about to occur.






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






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






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






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






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






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






45. In the critical path method - the latest possible point in time when the uncompleted portions of a schedule activity can start based on the schedule network logic - the project completion date - and any schedule constraints.






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






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






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






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






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