SCRUM guide Flashcards

1
Q

What is the definition of Scrum?

A

A framework within which people can address complex adaptive problems, while 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

Why is Scrum not a process or technique?

A

It s a framework within which you can employ various processes and techniques.

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

What are the components of Scrum?

A

Scrum teams and their associated roles, events, artifacts and rules.

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

What is the purpose of Scrum rules?

A

Bind together the events, roles, and artifacts, governing the relationships and interaction between them.

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

What does it mean that Scrum is founded on empirical process control theory / empiricism?

A

Empiricism asserts that knowledge comes from experience and making decisions based on what is known.
Scrum employs an iterative, incremental approach to optimize predictability and control risk.

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

What are the 3 pillars of empirical process control?

A

Transparency, inspection and adaptation.

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

What is transparency for empirical process control?

A

Transparency requires aspects of the process to be defined by a common standard so observers share a common understanding of what is being seen.

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

Give two practical examples of transparency in empirical process control.

A

A common language referring to the process must be shared by all participants, and those performing the work and those accepting the work must share a common definition of “Done”.

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

What is inspection for empirical process control?

A

Scrum users must frequently inspect Scrum artifacts and progress towards a Sprint Goal to detect undesirable variances.

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

What care should be taken with inspections?

A

They should not be so frequent that inspection gets in the way of the work.

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

What is adaptation for empirical process control?

A

If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted.

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

What are the events included in a Sprint?

A

Sprint Planning, Daily Scrum, development work, Sprint Review and Spring Retrospective.

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

Who are the members of a Scrum team?

A

The Product Owner, the Development Team and a Scrum Master.

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

What does it mean that Scrum teams are self-organizing?

A

They choose how best to accomplish their work rather than being directed by others outside the team.

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

What does it mean that Scrum teams are cross-functional?

A

They have all competencies needed to accomplish the work without depending on others outside the team.

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

Why does a Scrum team products iteratively and incrementally?

A

To maximize oportunities for feedback and to ensure a potentially useful version of working product is always available.

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

What does the PO do?

A

He maximizes the value of the product and the work of the Dev team.

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

Who is responsible for the Product Backlog?

A

The PO.

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

What does Product Backlog management includes?

A

Clearly expressing backog items.
Prioritize the backlog items to best achieve goals.
Optimizing the value of the work the Dev team performs.
Ensuring the backlog is visible, transparent and shows what the Scrum team will work on next.
Ensuring the Dev team understands items in the backlog.

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

Who does Product Backlog management?

A

The PO or the Dev team. But the PO remains accountable for it.

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

What requirements should the Dev team follow?

A

Only those defined by the PO in the product backlog.

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

What does the Dev team do?

A

They do the work of delivering a potentially releasable increment of “Done” product at the end of each Sprint.

23
Q

What ar the characteristics of the Dev team?

A

Self-organizing.
Cross-functional.
Everybody is a developer, regardless of their work and particular domains that need to be addresed, such as testing and business analysis.
The Dev team is accountable as a whole, regardless of individual skills and areas of focus.

24
Q

What is the right size for teh Dev team?

A

At least 3 devs to ensure a potentially releasable increment, and no more than 9 devs to avoid complex coordination.

25
Q

When are the PO and Scrum master included in the dev team count?

A

When they are also executing the work on the Sprint Backlog.

26
Q

What does the Scrum Master do?

A

The Scrum master ensures that the Scrum team follows Scrum theory, practices and rules.

27
Q

What does the Scrum Master with people outside the team?

A

The Scrum Master helps those people outside the Scrum team understand which of their interactions with the Scrum team are helpful and which are not.

28
Q

How does the Scrum master serve the PO?

A

Finding techniques for effective backlog management.
Helping the Scrum team understand the need for clear and concise backlog items.
Understanding product planning in an empirical environment.
Facilitating Scrum events as requested or needed.

29
Q

How does the Scrum Master serve the Dev team?

A

Coaching the Dev team in self-organization and cross-functionality.
Helping the Dev team to create high-value products.
Removing obstacles to the Dev team’s progress.
Faciliatating Scrum events as requested or needed.
Coaching the Dev team in organizational environments in which Scrum is not yet fully adopted and understood.

30
Q

How does the Scrum master serve the organization?

A

Leading and coaching the organization in its Scrum adoption.
Working with other Scrum masters to increase the effectiveness of the application of Scrum in the organization.
Planning Scrum implementations within the organization.
Helping employees and stakeholders understand and enact Scrum and empirical product development.
Causing changes that increase the productivity of the Scrum team.

31
Q

Why are all Scrum events time-boxed?

A

To ensure an appropriate amount of time is spent without allowing waste in the process.

32
Q

What is the purpose of the Scrum events?

A

To inspect and adapt something.

33
Q

What is a Sprint?

A

A Sprint is a time-box of one month or less during which a potentially releasable product increment is created.

34
Q

What is a Sprint in terms of product development?

A

Each Sprint has a definition of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product.

35
Q

What should be avoided during a Sprint?

A

No changes are made that would endanger the Sprint goal.

Quality goals do not decrease.

36
Q

What is permitted during a Sprint?

A

Scope mau be clarified and re-negociated between the PO and the Dev team.

37
Q

Why is the maximum duration of a Sprint one month?

A

More than one month, and the definition of what is being built may change, complexity may rise, and risk may increase.
Sprints enable predictability by ensuring inspection and adaptation of progress toward a Spring Goal at least every calendar month.
Sprint also limit risk to one calendar month of cost.

38
Q

When can a Spring be cancelled?

A

Before the Spring time-box is over.

39
Q

Who can cancel a Sprint?

A

The PO, who may be under the influence from stakeholders, the Dev team or the Scrum master.

40
Q

Why should a Sprint be cancelled?

A

If the Spring Goal becomes obsolete due to company’s change of direction or market/technology changes.

41
Q

Why does a Sprint cancellation rarely make sense?

A

Because a Sprint duration is so short and cancelling it consumes resources in having to regroup in another Sprint Planning.

42
Q

What happen to backlog items when a Sprint is cancelled?

A

All completed items are reviewed and potentially rteleased given PO accpetance.
Incomplete items are re-estimated asnd put back on the backlog.

43
Q

What is done during a Sprint Planning?

A

The following questions are answered:
What can be done during this Sprint?
How will the chosen work get done?

44
Q

What are the inputs to the to the “what can be done” meeting of the Sprint planning?

A

Product Backlog, latest product increment, projected capacity of the Dev team during the Sprint, and past performance of the Dev team.

45
Q

What are the outputs of the to the “what can be done” meeting of the Sprint planning?

A

Product Backlog items that should be delivered during the Sprint.
The Sprint Goal.

46
Q

What is done during the “how the chosen work gets done” meeting of the Sprint Planning?

A

The Sprint backlog is created: Product Backlog items selected for this Sprint plus the plan for delivering them.

47
Q

Who selects the number of items of the Product Backlog to be included in the Sprint Backlog?

A

Only the Dev team can assess what it can accomplish over the upcoming Sprint, but the PO can help clarify the selected Product Backlog items and make trade-offs.

48
Q

What should the Dev team be able to do by the end of a Sprint planning?

A

Explain to the PO and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated increment.

49
Q

What is a Sprint Goal?

A

It is an objective set for the Sprint that can be met through the implementation of Product Backlog.

50
Q

What is the purpose of the Sprint Goal?

A

The Sprint Goal gives the Dev team some flexibility regarding the functionality implemented during the Sprint.
It also enables the Dev team to work together rather than on sperate initiatives.

51
Q

What should be done if the work turns out to be different than the Dev team expected during the Sprint?

A

The Dev team should negotiate with the PO the scope of the Sprint Backlog within the Sprint.

52
Q

What is a Daily Scrum?

A

It is a 15-minute time-boxed event for the Dev team to synchronize activities and create a plan for the next 24 hours.

53
Q

What should the Dev team members explain during a Daily Scrum?

A

What did I do yesterday that helped the Dev team meet the Sprint Goal?
What will I do today to help the Dev team meet the Sprint Goal.
Do I see any obstacle that prevents me or the Dev team from meeting the Sprint Goal?

54
Q

What are the purposes of Daily Scrums?

A

Inspect progress toward the Sprint Goal.
Inspect hoiw progress is trending toward completing the work in the Sprint Backlog.
Helps the Dev team understand how to work as a self-organizing team to accomplish the Sprint Goal.
Improving communication by eliminate other meetings during the day and promoting quick decision-making.