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 measure of schedule efficiency expressed as the ratio of earned value to planned value.






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






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






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






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






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






7. An activity that logically comes before a dependent activity in a schedule.






8. The application of knowledge - skills - tools - and techniques to project activities to meet the project requirements.






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






10. The authorized budget assigned to scheduled work.






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






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






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






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






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






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






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






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






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






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






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. An activity that does not produce definitive end products and is measured by the passage of time. (Note: Level of effort is one of three earned value management [EVM] types of activities used to measure work performance.)






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






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






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






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






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






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






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






30. An event or situation that indicates that a risk is about to occur.






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






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






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






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






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






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






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






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






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






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






41. A dependent activity that logically comes after another activity in a schedule.






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






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






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






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






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






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






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






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






50. An estimate of the most probable activity duration that takes into account all of the known variables that could affect performance.