Manage Scope - Memorization

Question 1

Affinity diagram

Answer 1

A schematic representation that organizes requirements into groups according to their similarities.

Question 2

Brain writing

Answer 2

Documented ideas are passed along to other participants who will use it to generate and record new ideas.

Question 3

Deliverable

Answer 3

Verifiable item that must be produced to complete the project.

Question 4

Product analysis

Answer 4

Scope definition technique used to translate product descriptions into specific and verifiable deliverables

Question 5

Mind mapping

Answer 5

Diagram that organizes previously identified requirements around common ideas

Question 6

Requirements management plan

Answer 6

Subsidiary management plan that establishes the approach used to collect, analyze, refine, organize, prioritize, document, develop, validate, change, report and trace requirements.

Question 7

Requirements documentation

Answer 7

Documents that describe requirements and explain how the project’s business need is addressed.

Question 8

Prototype

Answer 8

A demonstration of a model or early version of a future product to collect feedback from stakeholders.

Question 9

Scope screep

Answer 9

Uncontrolled additions to the project scope.

Question 10

Work breakdown structure dictionary

Answer 10

Document that records detailed information regarding individual work packages.

Question 11

Product breakdown

Answer 11

Product analysis technique that graphically decomposes the product into high-level deliverables, which will be further decomposed into more detailed deliverables.

Question 12

Work breakdown structure

Answer 12

Deliverable-oriented treelike depiction of all the work required to accomplish the project objectives.

Question 13

Scope inspection

Answer 13

Deliverables are compared to requirements documentation and the scope baseline to ensure that they meet acceptance criteria.

Question 14

Scope management plan

Answer 14

Subsidiary management plan that specifies the scope management procedures, tools, techniques, roles, responsibilites and records.

Question 15

Scope baseline

Answer 15

Aggregates the approved version of the scope statement, WBS and WBS dictionary.

Question 16

Verifiable

Answer 16

Can be validated without ambiguity.

Question 17

Product requirement

Answer 17

Clear statement of the capabilities and behaviors required from the product.

Question 18

Scope statement

Answer 18

Document that establishes a common understanding regarding the project and product scope.

Question 19

Work package

Answer 19

Discrete work element, represented at the lowest level of the WBS, which express the work required to produce a deliverable by specific individuals, teams or organizational units.

Question 20

Product scope

Answer 20

Describes the project’s products and how they must perfom.

Question 21

Decomposition

Answer 21

The top-down process of identifying work packages by breaking down deliverables into smaller, more manageable elements.

Question 22

Project scope

Answer 22

Describes all the work required to deliver the project’s products, with the agreed-upon specifications.

Question 23

Requirements traceability matrix

Answer 23

Document that establishes a clear link between business, stakeholder and solution requirements.

Question 24

Product backlog

Answer 24

Prioritized list of the features, requirements, enhancements and product defects that might be addressed in future iterations.

Question 25

100% rule

Answer 25

WBS decomposition rule that states that the WBS captures all the project work.

Question 26

Epic

Answer 26

Large broadly-defined requirements that can span multiple iterations.

Question 27

User story

Answer 27

Concise and intuitive description of a feature, often written from the user perspective.

Question 28

Interviews

Answer 28

Information is collected through direct discussions with subject matter experts.

Question 29

Facilitated workshop

Answer 29

Stakeholders from multiple areas of expertise meet to define cross-functional requirements.

Question 30

Dot voting

Answer 30

Participants distribute a limited number of dot stickers or pen marks to the available options (e.g., requirements).

Question 31

Experiment

Answer 31

Time-boxed knowledge-acquisition activity used to learn more about a user story or explore potential improvement opportunities.

Question 32

Brainstorming

Answer 32

Ideas are collected with the help of a facilitator who encourages everyone to contribute.

Question 33

Focus groups

Answer 33

Selected subject matter experts meet in a focused setting to provide information regarding their expectations towards the product.

Question 34

Nominal group technique

Answer 34

Group decision-making technique that reaches a decision through vote, taking everyone’s opinion into account.

Question 35

Benchmarking

Answer 35

Searching inside and ouside the organization for references and improvement ideas.

Question 36

Delphi technique

Answer 36

Group decision-making-technique that seeks a consensus by repeatedly consulting a panel of experts who usually participate anonymously.

Question 37

Context diagram

Answer 37

Graphical, high-level representation of the product context, depicting how people and the environment interact with the product.