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 condition or capability that is required to be present in a product - service - or result to satisfy a contract or other formally imposed specification.






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






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






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






6. A component of the project or program management plan that describes how an organization's quality policies will be implemented.






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






8. A point in time when the status of the project is recorded.






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






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






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






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






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






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






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






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






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






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






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






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






21. The measure of work performed expressed in terms of the budget authorized for that work.






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






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






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






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






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






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






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






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






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






31. The series of phases that a project passes through from its initiation to its closure.






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






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






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






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






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






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






38. A representation of the plan for executing the project's activities including durations - dependencies and other planning information - used to produce a project schedule along with other scheduling artifacts.






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






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






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






42. A risk that would have a positive effect on one or more project objectives.






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






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






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






46. A measure of schedule efficiency expressed as the ratio of earned value to planned value.






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






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






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






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