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 methodology that combines scope - schedule - and resource measurements to assess project performance and progress.






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






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






4. A hierarchical representation of risks that is organized according to risk categories.






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






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






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






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






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






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






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






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 risk response strategy whereby the project team decides to acknowledge the risk and not take any action unless the risk occurs.






14. A component of the project - program - or portfolio management plan that describes how risk management activities will be structured and performed.






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






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






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






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






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






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






21. An activity that can be planned and measured and that yields a specific output. (Note: Discrete effort is one of three earned value management [EVM] types of activities used to measure work performance.)






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






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






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






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






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






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






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






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






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






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






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






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






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. The work performed to deliver a product - service - or result with the specified features and functions.






36. A factor in the planning process that is considered to be true - real - or certain - without proof or demonstration.






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






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






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






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






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






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






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






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






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






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






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






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






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