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






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






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






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






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






7. A grid for mapping the probability of each risk occurrence and its impact on project objectives if that risk occurs.






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






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






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






11. A grid that shows the project resources assigned to each work package.






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






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






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






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






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






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






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






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






20. An activity where effort is allotted proportionately across certain discrete efforts and not divisible into discrete efforts. (Note: Apportioned effort is one of three earned value management [EVM] types of activities used to measure work performance






21. An estimate expressed as a percent of the amount of work that has been completed on an activity or a work breakdown structure component.






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






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. An output of a schedule model that presents linked activities with planned dates - durations - milestones - and resources.






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






26. An iterative planning technique in which the work to be accomplished in the near term is planned in detail - while the work in the future is planned at a higher level.






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






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






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






30. A measure of the cost efficiency of budgeted resources expressed as the ratio of earned value to actual cost.






31. Any unique and verifiable product - result - or capability to perform a service that is required to be produced to complete a process - phase - or project.






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






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






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






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






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






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






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






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






40. The knowledge gained during a project which shows how project events were addressed or should be addressed in the future for the purpose of improving future performance






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






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






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






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






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






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






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






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






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






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