Project Scope Management Terms | Practice Test / Quiz / MCQs

Home > PMP - Project Management Professional > Quizzes > Project Scope Management Terms

Project Scope Management Terms

Fast practice, instant feedback. Timer auto-submits when time’s up.

Avg score: 100% • Most missed: “focus group”

Study First Challenge a Friend Stats

Project Scope Management Terms

Time left 00:00

25 Questions

1. Plurality

Status of the deliverables: the work that's been started, finished, or has yet to begin.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKA group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.

2. Code of Accounts

A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)Status of the deliverables: the work that's been started, finished, or has yet to begin.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

3. Interviews

A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKStatus of the deliverables: the work that's been started, finished, or has yet to begin.A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)

4. Work Performance Information

A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKA group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.Status of the deliverables: the work that's been started, finished, or has yet to begin.

5. Value Engineering

A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)This approach to project scope statement creation attempts to find the correct level of quality in relation to a reasonable budget for the project deliverable while still achieving an acceptable level of performance of the product.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKA requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.

6. nominal group technique

A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)As with brainstorming, participants are encouraged to generate as many ideas as possible, but the suggested ideas are ranked by a voting process.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

7. Project requirements

A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)These are the demands set by the customer, regulations, or the performing organization that must exist for the project deliverables to be acceptable. Requirements are often prioritized in a number of ways, from must have" to "should have" to "would like to have.""A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

8. Configuration Management Plan

A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKThis subsidiary plan defines how changes to the features and functions of the project deliverables will be monitored and controlled within the project.A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.

9. Work Breakdown Structure (WBS)

A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKA group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A deliverables-oriented breakdown of the project scope.

10. WBS Dictionary

A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A WBS companion document that defines all of the characteristics of each element within the WBSA requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

11. Project boundaries

A project boundary clearly states what is included with the project and what's excluded from the project. This helps to eliminate assumptions between the project management team and the project customer.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

12. Requirements Management Plan

This subsidiary plan defines how changes to the project requirements will be permitted, how requirements will be tracked, and how changes to the requirements will be approved.A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

13. Change management plan

A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.This subsidiary plan defines how changes will be allowed and managed within the project.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

14. Scope Creep

A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKA group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.Undocumented, unapproved changes to the project scope.

15. unanimity

A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKA requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A group decision method where everyone must be in agreement.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)

16. WBS template

A prepopulated WBS for repetitive projects. Previous projects' WBSs are often used as templates for current similar projects.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKA requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)

17. Product Scope Description

This is a narrative description of what the project is creating as a deliverable for the project customer.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

18. Brainstorming

A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKA group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)This approach encourages participants to generate as many ideas as possible about the project requirements. No idea is judged or dismissed during the brainstorming sessionA requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.

19. Project Scope

A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKThis defines all of the work, and only the required work, to complete the project objectives.

20. Product Assumptions

A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A project assumption is a factor in the planning process that is held to be true but not proven to be trueA numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKA group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)

21. Active observation

A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.The observer interacts with the worker to ask questions and understand each step of the work being completed. In some instances, the observer could serve as an assistant in doing the workA numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

22. focus group

A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A moderator led requirements collection method to elicit requirements from stakeholdersA numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

23. Product breakdown

A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A scope definition technique that breaks down a product into a hierarchical structure, much like a WBS breaks down a project scope.A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK

24. autocratic

A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKA requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A decision method where only one individual makes the decision for the groupA group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)

25. Funding limit

A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.A group decision method where the largest part of the group makes the decision when it's less than 50% of the total. (Consider three or four factions within the stakeholders.)A numbering system for each item in the WBS. The PMBOK is a good example of code of accounts, as each chapter and it's subheadings follow a logical numbering scheme. For example PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOKMost projects have a determined budget in relation to the project scope. There may be a qualifier on this budget, such as plus or minus 10 percent based on the type of cost estimate created.

⚡ Recently practiced quizzes in this topic

Live quiz activity

PMP: The Executing Domain PMP: The Monitoring and Controlling Domain Project Management Basics Knowledge Test PMP: The Initiating Domain PMI-002 Exam: CAPM PMP Exam Questions Certified Associate In Project Management Exam PMP Glossary Project Risk Management Knowledge Test PMI Project Management Professional Exam

25 Questions

❤ If you liked Fatskills, consider supporting us by checking out The Life Manuals You Never Got.

About | Explore | User Guide | Topics | Subjects | Doubt Solver | Career Aptitude Test | Answers | Free Tools | OSHA Basics Quiz | What Should We Know?
Privacy | Terms |

Without work one finishes nothing. - Ralph Waldo Emerson
© 2026 Fatskills.com

All trademarks, logos and brand names are the property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, trademarks and brands does not imply endorsement.

25 Questions

❤ If you liked Fatskills, consider supporting us by checking out The Life Manuals You Never Got.

About | Explore | User Guide | Topics | Subjects | Doubt Solver | Career Aptitude Test | Answers | Free Tools | OSHA Basics Quiz | What Should We Know? Privacy | Terms |

Without work one finishes nothing. - Ralph Waldo Emerson© 2026 Fatskills.com

All trademarks, logos and brand names are the property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, trademarks and brands does not imply endorsement.

About | Explore | User Guide | Topics | Subjects | Doubt Solver | Career Aptitude Test | Answers | Free Tools | OSHA Basics Quiz | What Should We Know?
Privacy | Terms |

Without work one finishes nothing. - Ralph Waldo Emerson
© 2026 Fatskills.com