Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Agile Project Management > Scrum Framework > Flashcards

Scrum Framework Flashcards

Definitions and history, scrum pillars and values, the framework, the teams and key scrum events, and

1
Q

Define Scrum

A

SCRUM is a framework within which people can address complex ADAPTIVE problems, which productively and CREATIVELY delivering products of the HIGHEST POSSIBLE VALUE.

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

In 1986, these authors released scrum framework in “The New New Product Development Game”.

A

Hirotaka TAKUCHI and Ikujiro NONAKA

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

In “The New New Product Development Game”, what did the authors define as being important?

A

For the best results, new products can be developed in a new way through small cross-functional teams, similar to a scrum in rugby where a team of specialized individuals supports each other.

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

Scrum was more formally introduced by DeGrace and Stahl in which book?

A

Wicked Problems, Righteous Solutions.

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

Who are the two people regarded as the creators of Scrum in the 1990s?

A

Ken SCHWABER and Jeff SUTHERLAND

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

What year did the Agile Manifesto get released?

A

2001

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

What are the three pillars of empiricism (i.e., philosophy) in the scrum framework?

A

(TIA) Transparency, Inspection and Adaptation.

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

What are the three components of the Scrum Framework?

A

(ARE) Artifacts, Roles and Events

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

What are the five scrum values?

A

(CORFC) Courage, Openess, Respect, Focus, and Commitment

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

What are the three Scrum artifacts (e.g., objects)?

A

Product Backlog, Sprint Backlog and Increment

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

Define the Product Backlog

A

A prioritized list of items (e.g., features, fixes, Enhancements and Non-functional Requirements) that together form the Product roadmaps, documenting how it will evolve, the outlined budget and that the product aligns with expectations.

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

Define Sprint

A

An iteration that contains all sprint activity in a container or timebox.

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

Define Timebox

A

A period of time that shouldn’t be exceeded.

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

Define Sprint Backlog

A

A set of items or tasks that will be worked on in a sprint that is derived from the product backlog items. All the items in the sprint backlog contains all the work that will help build a product increment.

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

What is the sum of all completed product backlog items during the current sprint including the reviewed and realized value of all the increments in previous sprints?

A

The product increment

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

What are the three main scrum roles?

A

Product Owner, Development team, and Scrum Master.

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

Whose role is it to manage the product backlog and represent all stakeholders of the project?

A

The Product Owner

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

Who is responsible for managing the Sprint backlog in order to achieve the Sprint Goal and has the skills to build and deliver the product increments?

A

The cross-functional, self-organizing Development team.

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

Who is responsible for implementing the scrum framework and removing impediments to the team’s performance?

A

The Scrum Master

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

What are the four scrum events?

A

Sprint planning, daily scrum, sprint review, sprint retrospective.

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

What are the two parts/artifacts of sprint planning?

A

The Product Backlog (What will be built and why items are prioritized) (1 hour per week of sprint up to 4 hours)
The Sprint Backlog - the details and estimates and how things will be built. (1 hour per week of spring up to 4 hours)

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

What happens in a daily scrum?

A

Synchronizing of sprint work and progress and the identification of sprint impediments.

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

Define Sprint Review. How long should this take?

A

A product-centric ceremony occurring at the end of each sprint that involves evaluating and improving the product as well as validating the status of the original sprint goal. This should take one hour per week of sprint up to a maximum of four hours.

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

Define Sprint Retrospective. How long should this take?

A

A process-centric ceremony occurring after the sprint review and before the next sprint planning event that allows the team to identify best practices and areas of improvement. (45 minutes for every week of sprint up to 3 hours).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
What is product backlog grooming?
A collaborative process between the product owner and team to refine the product backlog to **add details, estimates and order to items in the backlog**. This is an unofficial event.
26
Define Sprint
An **iteration** that contains **all scrum activity** that is **timeboxed** from one to four weeks (max 30 calendar days) and has **all four scrum events**.
27
Who is responsible for collecting requirements and forming the product backlog?
Product Owner
28
Who creates and updates the product backlog?
Product Owner
28
Who is responsible for prioritizing work?
Product Owner
29
Who communicates the product vision and product backlog to the team?
Product Owner
29
Who works with the team to declare the official sprint goal
Product Owner
30
Who is responsible for dealing with all stakeholders, customers and the steering committee
Product Owner
31
Who has the skills to deliver the product increment of a sprint?
Product Team
32
Who is accountable for achieving the sprint goal and sharing the workload?
Product Team
33
Who are the self-organizing and self-managing members of the team?
Product Team
34
What is the optimal size of a product team?
7 +/- 2 team members (between 5 - 9 members)
35
Who create and maintains the sprint backlog?
The product team
36
Who tracks the sprint effort?
Product Team
37
Who are the main participants in the daily scrum?
Product Team
38
Who prepares for the Sprint Review?
The product team
39
What is a sprint review?
A demonstration of the results of the work that contributes to the product increment.
40
Who ensures that the team is applying scrum rules, techniques and practices in the best possible way.
Scrum Master
41
Who helps to resolve conflicts, remove impediments and cheer the team on?
Scrum Master
42
Who keeps the team focused on the sprint goal?
Scrum Master
43
Who facilitates scrum activities?
Scrum Master
44
Who protects the team from external "noise" and distractions?
Scrum Master
45
Who is the "servant leader"?
Scrum Master
46
Who clarifies product backlog items?
Scrum Master (as servant leader to the PO)
47
Who helps to improve communication with the development teams?
Scrum Master (as servant leader to the PO)
48
Who promotes learning?
Scrum Master (as servant leader to the PO).
49
Who helps the product owner effectively prioritize work?
Scrum Master (as servant leader to the PO)
50
Who helps to facilitate meetings like sprint planning, sprint review and retrospective?
Scrum Master (as servant leader to the PO).
51
Who coaches the team in a self-organizing and cross functional manner?
Scrum master (as servant leader to the team)
52
Who helps the team to create high value products by removing impediments?
Scrum Master (as servant leader to the team)
53
Who helps to facilitate scrum events, such as sprint planning, scrum or retros?
Scrum Master (as servant leader to the team).
54
who supports the team in organizational environments where scrum is not the norm?
The scrum master (as the servant leader to the team).
55
Who protects the team to allow them to focus on their sprint goal and their work?
The Scrum Master
56
In Sprint planning part 1, are observers allowed?
No
57
What are the objectives of sprint planning part one?
Determining for the next increment **"what"** requirements and **"why"** they are needed.
58
What are the mandatory key inputs for sprint planning part one?
A **prioritized backlog** and the projected **sprint capacity** of the team.
59
What are the optional Key inputs for sprint planning part one?
**Results** of the previous sprint, **team's performance** and **any thing learned** about impediments /improvements from the previous sprints.
60
A main activity in sprint planning part one is organizing the meeting and ensuring the timebox is respected. Who does this?
The Scrum Master
61
Who presents the up-to-date Product backlog items and priorities at the Sprint planning part one meeting?
The product owner
62
In sprint planning part one, who questions, clarifies and refines the product backlog content, priorities and purpose?
Everyone.
63
During sprint planning part one, who reviews the last sprint team performance, impediments/improvements lists?
Everyone.
64
During sprint planning part one, who provides a high-level estimate of the product backlog items to form the sprint increment?
The Product team
65
During sprint planning part one, who checks/confirms sprint duration, team availability, capacity and capabilities?
Everyone
65
What is the key output at the end of sprint planning part one?
A tentative sprint goal with the highest priority product backlog items.
66
What is the optional Key output of sprint planning part one?
A reprioritized/refined product backlog.
67
What artifact summarizes the desired and expected outcome of a sprint?
The Sprint Goal
68
Who creates the sprint goal?
Written collaboratively between the Product Owner and team
69
What are the two key benefits of a sprint goal?
It facilitates the **prioritization** of work and promotes **effective team work**.
70
What are the secondary benefits of a sprint goal?
Allow the team to **maintain alignment** between the work and the sprint goal, assists with stakeholder **communication** and sets **clear expectations**.
71
Who participates in sprint planning part 2?
The team and scrum master.
72
Who are the optional participants in sprint planning part 2?
The PO and any other SMEs
73
What is the focus of sprint planning part 2?
Determining **how** the team will **deliver** the sprint increment as per the sprint goal and **how long** each item will take.
74
What is the mandatory key input for Sprint planning part 2?
The tentative sprint goal.
75
What is the optional key input for sprint planning part 2?
The product backlog.
76
In sprint planning part 2, who ensures the meeting is organized and respects the timebox?
The scrum master.
77
In sprint planning part 2, who converts the Product Backlog items into the sprint backlog with a detailed-task list with estimate?
The team
78
In sprint planning part 2, who confirms (or renegotiates) the forecast, sprint goals and sprint duration?
Everyone.
79
In sprint planning part 2, who explains the spring backlog work and self-organizes to achieve the sprint goal?
The team.
80
In sprint planning part 2, who commits to the final sprint goal?
Everyone.
81
What are the mandatory key outputs of sprint planning part 2?
The **sprint backlog** (with tasks and estimates) and the **final sprint goal**.
82
What are the optional key outputs for sprint planning part 2?
A **reprioritized/refined** product backlog, and an **updated** sprint **duration** (*rarely*)
83
Define Swarming
When team members with capacity and appropriate skills collectively work (AKA Swarm) on an item that has been started by another team member but not finished.
84
Who are the mandatory people in the daily scrum?
Team, Scrum master
85
Who are the optional participants in the daily scrum?
The PO and any additional SMEs. They only observe.
86
What are the objectives of the daily scrum?
**Sync** sprint activities, **create** a plan for the next 24 hours and **track** progress.
87
What are the mandatory key inputs to the daily scrum?
**Sprint backlog** (tasks and estimates) and the sprint **burndown** chart.
88
What is the optional input to the daily scrum?
The sprint goal.
89
What happens at a daily scrum?
* Identifying **blockers** * **Updating** the sprint **backlog** * Identifying what **work** was **done**, and * What **work** will be **completed** for the **next** daily scrum.
90
What are the mandatory key outputs of the daily scrum?
Updated backlog, and updated sprint burndown chart.
91
What are the two optional key outputs of the daily scrum?
Updated sprint goal (rarely) and an impediments list.
92
What is a sprint burndown chart?
A **chart** with the remaining hours on the Y axis and sprint duration on the X axis that **depicts the trend of the work effort remaining** in the sprint.
93
Who are mandatory at the sprint review?
PO, team, Scrum Master, Stakeholders such as end users.
94
What are the objectives of the sprint review?
**Demo**, **inspect** and capture **feedback** on a completed product increment.
95
What are the key inputs for the sprint review
Mandatory: completed sprint results, committed sprint goals (and Product Backlog items). Optional: Sprint backlog and product backlog.
96
List the activities in a sprint review from start to finish.
* **Preparing** (team) * **Organizing and respecting** the time box (Scrum Master) * Presenting the **sprint goal** and committed and actual PBI (Team) * Providing **feedback** on demos (PO and Stakeholders) * Inviting **stakeholders** to **provide feedback** (PO) * Answering **questions** and noting **improvements** (team) * Discussing **potential backlog updates** (PO) * Announce **acceptance or rejection** (partial or full) of increment (PO) * Announcing place and **date for next sprint review** (Scrum Master)
97
Who participates in a Sprint Retrospective?
Mandatory: Entire Scrum team, Dev Team, PO Optional: external facilitator in place of the Scrum Master.
98
What is the main objective of sprint the sprint retro?
**Evaluate sprint performance** and identifying what worked well and improvement areas.
99
What are the key inputs in a retro?
Mandatory: **Completed** sprint **results** and **committed sprint goal** Optional Key Inputs: Sprint Backlog and product backlog
100
What are the main activities of a sprint retro?
* **Organizing** the retro (Scrum Master) * **Identifying improvements**/what went well (All) * Prioritizing improvements (All) * **Identifying actionable improvements** for the next sprint (All) * **Capture** and **distribute** retrospective **results** (Scrum master or external facilitator
101
What are the two main outputs of a sprint retro?
Improvements list (mandatory) Product Backlog (optional)
102
What are the four benefits of a sprint retro?
**PCQC** Enhanced **quality** Enriched **capability** (knowledge sharing/transfer) Increased **productivity** Improved **capacity**
103
What is the Scrum of Scrums (SoS)?
Allow multiple teams to connect to discuss work, particularly those that overlap. Not a replacement for each teams scrum. One team member from each product team will attend the Scrum of Scrums
104
What is the primary benefit of Scrum of Scrums?
Ensures and facilitates coordination, communication and synchronization.
105
In the unlikely event that a sprint is cancelled, what is the first step?
Conduct a new **sprint planning meeting** to review the reason for the sprint cancellation.
106
Who can cancel a sprint?
The PO
107
Why might a sprint be cancelled?
If circumstances negate the sprint goal or make it obsolete (e.g., change in strategic direction, or market or tech changes. The team may cancel a sprint if they feel unable to meet the sprint goal.
108

Agile Project Management (11 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions