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






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






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






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






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






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






7. A component of the human resource plan that describes when and how team members will be acquired and how long they will be needed.






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






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






10. A method of estimating project duration or cost by aggregating the estimates of the lower-level components of the work breakdown structure (WBS).






11. A technique used to shorten the schedule duration for the least incremental cost by adding resources.






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






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






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






15. An estimate of the longest activity duration - which takes into account all of the known variables that could affect performance.






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






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






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






19. A group of related schedule activities aggregated and displayed as a single activity.






20. A component of the project - program - or portfolio management plan that describes how - when - and by whom information will be administered and disseminated.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






38. A group of potential causes of risk.






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






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






41. A critical path method technique for calculating the late start and late finish dates by working backward through the schedule model from the project end date.






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






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






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






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






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






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






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






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






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