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 performance expressed as the difference between the earned value and the planned value.






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






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






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






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






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






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






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






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






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






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. The document that describes how the project will be executed - monitored - and controlled.






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






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






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






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






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






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






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






20. A point in time when the status of the project is recorded.






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






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






23. A logical relationship in which a successor activity cannot finish until a predecessor activity has finished.






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






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






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






27. The centralized management of one or more portfolios to achieve strategic objectives.






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






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






30. A set of conditions that is required to be met before deliverables are accepted.






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






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






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






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






35. An estimate of the shortest activity duration that takes into account all of the known variables that could affect performance.






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






37. The amount of time that a schedule activity can be delayed without delaying the early start date of any successor or violating a schedule constraint.






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






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






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






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






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






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






44. The iterative process of increasing the level of detail in a project management plan as greater amounts of information and more accurate estimates become available.






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






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






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






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






49. The amount of time whereby a successor activity is required to be delayed with respect to a predecessor activity.






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.