Manage Scope - Memorization Flashcards

Memorization exercises (37 cards)

1
Q

Affinity diagram

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Brain writing

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Deliverable

A

Verifiable item that must be produced to complete the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Product analysis

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Mind mapping

A

Diagram that organizes previously identified requirements around common ideas

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Requirements management plan

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Requirements documentation

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Prototype

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Scope screep

A

Uncontrolled additions to the project scope.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Work breakdown structure dictionary

A

Document that records detailed information regarding individual work packages.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Product breakdown

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Work breakdown structure

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Scope inspection

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Scope management plan

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Scope baseline

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Verifiable

A

Can be validated without ambiguity.

17
Q

Product requirement

A

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

18
Q

Scope statement

A

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

19
Q

Work package

A

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.

20
Q

Product scope

A

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

21
Q

Decomposition

A

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

22
Q

Project scope

A

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

23
Q

Requirements traceability matrix

A

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

24
Q

Product backlog

A

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

25
100% rule
WBS decomposition rule that states that the WBS captures all the project work.
26
Epic
Large broadly-defined requirements that can span multiple iterations.
27
User story
Concise and intuitive description of a feature, often written from the user perspective.
28
Interviews
Information is collected through direct discussions with subject matter experts.
29
Facilitated workshop
Stakeholders from multiple areas of expertise meet to define cross-functional requirements.
30
Dot voting
Participants distribute a limited number of dot stickers or pen marks to the available options (e.g., requirements).
31
Experiment
Time-boxed knowledge-acquisition activity used to learn more about a user story or explore potential improvement opportunities.
32
Brainstorming
Ideas are collected with the help of a facilitator who encourages everyone to contribute.
33
Focus groups
Selected subject matter experts meet in a focused setting to provide information regarding their expectations towards the product.
34
Nominal group technique
Group decision-making technique that reaches a decision through vote, taking everyone's opinion into account.
35
Benchmarking
Searching inside and ouside the organization for references and improvement ideas.
36
Delphi technique
Group decision-making-technique that seeks a consensus by repeatedly consulting a panel of experts who usually participate anonymously.
37
Context diagram
Graphical, high-level representation of the product context, depicting how people and the environment interact with the product.