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 logical relationship in which a successor activity cannot start until a predecessor activity has started.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






17. A risk response strategy whereby the project team decides to acknowledge the risk and not take any action unless the risk occurs.






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






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






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






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






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






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






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






25. The authorized budget assigned to scheduled work.






26. A component of the project or program management plan that describes how the scope will be defined - developed - monitored - controlled - and verified.






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






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






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






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






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






32. A risk response strategy whereby the project team acts to eliminate the threat or protect the project from its impact.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






49. The realized cost incurred for the work performed on an activity during a specific time period.






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