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 component of a project or program management plan that describes how costs will be planned - structured - and controlled.






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






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. An intentional activity to modify a nonconforming product or product component.






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






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






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






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






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






10. A technique for estimating the duration or cost of an activity or a project - using historical data from a similar activity or project.






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






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






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






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






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






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






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






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






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






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






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






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






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






24. The authorized budget assigned to scheduled work.






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






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






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






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






29. Plans - processes - policies - procedures and knowledge bases specific to and used by the performing organization.






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






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






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






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






34. The sequence of activities that represents the longest path through a project - which determines the shortest possible duration.






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






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






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






38. In the critical path method - the earliest possible point in time when the uncompleted portions of a schedule activity can finish based on the schedule network logic - the data date - and any schedule constraints.






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






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






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






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






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






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






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






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






47. A hierarchical representation of the project organization - which illustrates the relationship between project activities and the organizational units that will perform those activities.






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






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






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