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 point in time when the status of the project is recorded.






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






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






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






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






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






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






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






9. The authorized budget assigned to scheduled work.






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






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






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






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






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






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






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






17. The number of labor units required to complete a schedule activity or work breakdown structure component - often expressed in hours - days - or weeks.






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






19. A technique used for dividing and sub-dividing the project scope and project deliverables into smaller - more manageable parts.






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






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






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






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






24. The amount of budget deficit or surplus at a given point in time - expressed as the difference between the earned value and the actual cost.






25. Any activity on the critical path in a project schedule.






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






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






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






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






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






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






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






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






34. A management control point where scope - budget - actual cost - and schedule are integrated and compared to earned value for performance measurement.






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






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






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






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






39. A process used to investigate or analyze the output of the schedule model in order to optimize the schedule






40. A methodology that combines scope - schedule - and resource measurements to assess project performance and progress.






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






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






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 method of estimating project duration or cost by aggregating the estimates of the lower-level components of the work breakdown structure (WBS).






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






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






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






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






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






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