Scope Flashcards

1
Q

Requirements traceability matrix

A

Links the product requirements from their origin to their completed deliverables. Ensures that each requirement adds business value, by linking it to the business and project objectives.

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

Unanimity

A

A decision reached where everyone agrees.

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

Majority

A

Decision reached where more than 50% of people agree.

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

Plurality

A

A decision reached where the largest block agrees (even if it’s not more than 50%)

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

Fist of Five (Agile)

A

The project manager asks the team to show their level of support for a decision by holding up a closed fist, one finger, two fingers, etc. Five fingers are full support.

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

Nominal group technique

A

Form of anonymous voting and prioritization to reduce one person like an executive swaying the opinions of others.

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

MoSCoW

A

Must have, should have, could have, will not have.

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

Benefit to cost

A

Prioritizing items with the highest benefit and the lowest cost. Divide benefit by cost, prioritize highest first. (cost or effort)

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

Cost of delay and CD3

A

Uses the value of the item versus the time it will take to deliver. Want the highest cost of delay item to be done first.

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

Decomposition

A

The technique used for dividing and subdividing something into smaller, more manageable parts.

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

Work breakdown structure (WBS)

A

Way of breaking down work into smaller pieces.

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

Product breakdown structure (Agile)

A

Breaks the project down into features

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

Project scope baseline

A

Approved version of the project scope, which can only be changed through formal change control and used to compare to future versions.

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

Project scope statement

A

Includes the description of the project scope, major deliverables, assumptions, and constraints.

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

What is included in the project scope statement?

A

Project scope description, deliverables, acceptance criteria, and project exclusions.

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

Project scope description

A

Written description of the scope

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

Deliverables

A

Any unique and verifiable product, result, or capability.

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

Acceptance criteria

A

Set of conditions to be met before deliverables are accepted. (Given, when, then, as a, I want, so I can)

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

Project exclusions

A

What is excluded-helps reduce scope creep.

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

Work breakdown structure dictionary

A

Supports the WBS with more detailed information on deliverables, activities, and scheduling for each item.

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

Validate scope

A

When we take the completed deliverables to the project sponsor or customer for final acceptance.

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

Control scope

A

Process of managing changes to the product (the scope baseline)

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

Control quality

A

Recording and monitoring the testing results to ensure the product meets its requirements.

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

What is the project scope?

A

Complete outline of all the work that needs to be done including tasks, deliverables, timelines, resources, and boundaries involved, essentially defining the extent and parameters of what the project will achieve and what it will not.

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

What is the scope management plan?

A

Tells us how the project scope will be developed.

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

What is the quality management plan?

A

A document that defines how quality standards will be achieved and maintained throughout the project.

27
Q

What is the project life cycle description?

A

The structured phases a project follows from start to finish, ensuring controlled progress and successful completion.

28
Q

What is the development appraoch?

A

The methodology or framework used to execute and deliver project work. (predictive, agile, iterative, hybrid or incremental)

29
Q

What is alternatives analysis?

A

A technique used to evaluate different options to determine the best course of action for a project.

30
Q

What is a multi-criteria decision chart (MCDA)?

A

a structured tool used in project management to evaluate multiple options based on weighted criteria, helping teams select the best course of action.

31
Q

What is the business analysis plan?

A

A structured plan defining how business analysis activities will be conducted, managed, and communicated throughout the project.

32
Q

What are requirements?

A

Conditions or capabilities that are needed in a product, service, or result to ensure we deliver the right value from our project.

33
Q

What is the lessons learned register?

A

A document that records insights, best practices, and challenges from a project to improve future performance.

34
Q

What are affinity diagrams?

A

Help us group ideas into smaller buckets.

35
Q

What is a nominal group technique? (NGT)

A

A structured brainstorming and decision-making method used to generate and prioritize ideas in a group setting.

36
Q

What is joint application development (JAD)?

A

A structured workshop approach where stakeholders, developers, and users collaborate to define project requirements and solutions.

37
Q

What is quality function deployment (QFD)?

A

A systematic process that translates customer requirements into product or service design specifications. (Voice of the customer)

38
Q

What are user stories?

A

User Stories are short, simple descriptions of a feature or functionality from the perspective of the end-user. They help Agile teams understand what the user needs, why they need it, and how it benefits them.

39
Q

What is a context diagram?

A

a high-level visual representation of a system and its interactions with external entities (such as users, other systems, or organizations).

40
Q

What is prototyping?

A

an iterative process of creating a preliminary version of a product or system to gather feedback, validate requirements, and refine designs before final development. It helps stakeholders visualize functionality and improve the final product.

41
Q

What is requirements documentation?

A

Describes how individual requirements meet the business needs for the project.

42
Q

What is the acceptance criteria for a user story (Agile)?

A

Given, when, then

43
Q

What are iterative releases (Agile)?

A

A development approach where a product is delivered in small, incremental updates, allowing for continuous feedback and improvement.

44
Q

What is a product backlog (Agile)?

A

a prioritized list of features, enhancements, bug fixes, and technical work that serves as the single source of work for an Agile team.

45
Q

What is a product owner (Agile)?

A

A key Agile role responsible for defining, prioritizing, and managing the Product Backlog to deliver maximum value.

46
Q

What is the project scope statement?

A

Description of the project and the product scope and major deliverables.

47
Q

What are boundaries?

A

The defined limits of a project, system, or process that clarify what is included and excluded.

48
Q

What is acceptance criteria?

A

What we need to fulfill for the product ot be accepted by the project sponsor, business, or customer.

49
Q

What is multicriteria decision analysis?

A

A way to make decisions by ranking the options against outcomes from 1 to 5. Might be used for scope decisions against criteria of meeting requirements, schedule, budget, and resources.

50
Q

What is product analysis?

A

Used to define products and services. Used for translating high-level product or service descriptions into meaningful deliverables.

51
Q

What is user story mapping?

A

a visual technique used to organize and prioritize user stories based on customer journeys, workflows, or business value.

52
Q

What is a deliverable?

A

Any unique and verifiable product, result or capability.

53
Q

What is the product backlog (Agile)?

A

List of features that meet our customer requirements. These are later broken down into user stories to complete pieces in a sprint.

54
Q

What is a product roadmap (agile)?

A

Similar to a schedule, this lists the features on a timeline so we can see the order (and sometimes timeframe) they will be done in.

55
Q

What is the work breakdown structure (WBS)?

A

a hierarchical decomposition of the total project work into smaller, manageable components.

56
Q

What is a scope baseline?

A

The approved project scope, including the scope statement, WBS, and WBS Dictionary, used as a reference for scope management.

57
Q

What is a work package?

A

The smallest unit of work in a Work Breakdown Structure (WBS), representing a specific deliverable or task.

58
Q

What is decomposition?

A

A technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.

59
Q

What are project exclusions?

A

define what is NOT included in the project scope, ensuring clarity on deliverables, boundaries, and stakeholder expectations. Exclusions help prevent scope creep and misunderstandings.

60
Q

What is an epic?

A

A high-level user story or feature that is too large for a single sprint and must be broken down into smaller user stories.

61
Q

What is a feature?

A

a distinct functionality that delivers value to users and supports business objectives. In Agile project management, a Feature is larger than a User Story but smaller than an Epic, and it often represents a complete capability that can be delivered in one or more iterations.

62
Q

Variance analysis

A

Used to compare the scope baseline to the actual results, see if the variance is within threshold amounts, or if corrective or preventative action is needed.