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






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






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






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






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






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






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






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






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






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






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






12. A technique for determining the cause and degree of difference between the baseline and actual performance.






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






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






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






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






17. A bar chart of schedule information where activities are listed on the vertical axis - dates are shown on the horizontal axis - and activity durations are shown as horizontal bars placed according to start and finish dates.






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






19. A group of potential causes of risk.






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






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






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






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






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






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






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






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






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






29. The series of phases that represent the evolution of a product - from concept through delivery - growth - maturity - and to retirement.






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






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






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






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






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






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






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






37. Conditions - not under the immediate control of the team - that influence - constrain - or direct the project - program - or portfolio.






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






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






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






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






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






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






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






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






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






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






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






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






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