Kanban for Scrum Teams Flashcards
1
Q
List the Kanban Practices
A
VLAI
- Visualization of the workflow
- Limiting WIP
- Active management of work items
- Inspect + adapt the definition of workflow
2
Q
What is Little’s Laws?
A
Avg cycle time = Avg WIP / Avg Throughput
3
Q
Define throughput
A
Work items finished per period of time
4
Q
Define cycle time
A
The elapsed time between item start/finish within a specific workflow. *Each state of a workflow is also a wokflow.
5
Q
What are the basic metrics of flow?
A
WCAT
- WIP
- Cycle time
- Work item age
- Throughput
6
Q
Define work-in-progress (WIP)
A
Work items started but not finished
7
Q
Define work item age
A
Time from start to present of items in progress
8
Q
Explaine Littles Law
A
The more things you work on at the same time, the longer it’s going to take to finish any one of them.
9
Q
Visualization of workflow must include what?
A
- Defined start + finish points 2. Definition of work items (units of value) 3. Defined workflow states 4. Pull policies 5. WIP Limits
10
Q
What are the effects of limiting WIP?
A
PF-OF-CC
- Creates a pull system
- Improves flow
- Improves self-_organization_
- Improves focus
- Improves commitment
- Improves collaboration
11
Q
List 3 forms of active management of work items
A
- Ensure work items enter and exit the workflow at the same rate 2. Ensure work items aren’t left to age 3. Responding quickly to blocked items and items at risk of exceeding the SLE
12
Q
How is the SLE used?
A
- To find active flow issues 2. To inspect & adapt in the cases of falling below
13
Q
What are the two elemts of an SLE?
A
- A period of elapsed days 2. A probability associated with that period
14
Q
What things might be adjusted as a result of inspected and adapting the teams definition of workflow?
A
- Visualization policies 2. WIP limits 3. SLE’s 4. Batch size
15
Q
List the flow based events
A
- The Sprint 2. Sprint Planning 3. Daily Scrum 4. Sprint Review 5. Sprint Retro
16
Q
List the flow relevance of the sprint
A
- It is the heartbeat for inspection and adaptation of both product and process 2. Kanban practices can help teams improve sprint flow 3. The sprint establishes priority in reference to unplanned work
17
Q
Define batchsize
A
The amount of work done before releasing or integrating
18
Q
What flow metric is most relevant to sprint planning?
A
Throughput
19
Q
A flow-based daily scrum focuses on what?
A
- Blocked items 2. Work item age & SLE threats 3. Factors not visible on the board 4. Factors that could impact priority 5. Broken WIP limits & meeting the sprint goal
20
Q
What two flow metrics should be covered in the sprint review?
A
- Throughput 2. Cycle time
21
Q
True or false Changes to a teams definition of workflow can happen at any time.
A
True
22
Q
What flow factors should be covered in a teams retrospective?
A
- WIP Limits 2. Cycle time 3. SLEs 4. CFD 5. Scatterplot diagrams
23
Q
List two facts about the product increment in Kanban for scrum
A
- Scrum requires at least one per sprint 2. Multiple increments are encouraged
24
Q
What is Scrum?
A
A framework within which other techniques and methods can be practiced
25
WIP limit inspection belongs in which scrum events?
1. Daily scrum 2. Retro
26
Throughput inspection belongs in which scrum events?
1. Sprint planning 2. Sprint review 3. Retro
27
Work item age inspection belongs in which scrum event?
Daily scrum
28
Cycle time inspection belongs in which scrum events?
1. Sprint review 2. Retro
29
List everything that should be inspected in retro:
1. WIP limits 2. Cycle time 3. Throughput 4. SLEs 5. CFD 6. Scatterplot
30
What are leading indicators?
1. WIP 2. Work item age
31
What are lagging indicators?
1. Cycle time 2. Throughput 3. Velocity (not a flow metric)
32
List the 5 scrum values
**CCFOR**
1. Courage
2. Commitment
3. Focus
4. Openness
5. Respect
33
What are the two rules for changing the sprint backlog:
1. Changes must be compatable with the sprint goal 2. You must be able to deliver an increment at the end of the sprint
34
Name two policies that are already a part of scrum proper?
1. Sprints as a WIP limit 2. Definition of done as a pull policy
35
List the 4 affects of limiting WIP:
1. Shorter feedback cycles 2. Faster value generation 3. A more predictable process 4. A more sustainable pace
36
What 3 metrics does a CFD show?
1. Aprox average cycle time for a date 2. Exact WIP for a date 3. Average throughput for a date range
37
Define Kanban
A strategy for oprimizing the flow of stakeholder value through a process that uses a visual, WIP limited, pull system.
38
What is defined as "The number of work items 'finished' per unit of time. (measurement of the exact count of work items)"
Throughput
39
What scrum event is a way of limiting work in progress and controlling how much work a Dev Team is going to attempt during a specified period?
The Sprint
40
What is the Kanban Guide's definition of "Workflow" or "Flow"?
A shared understanding within the SCRUM Team of how work is defined (work items), the start state of the process, the active states for the work items and the finished state of the work items.
41
What is the Kanban Guide in relation to the SCRUM Guide?
It is not meant to replace or discount any part of the SCRUM Guide.
42
What kinds of changes to the policies can have a material impact on how the SCRUM Team performs overall?
Small Changes
43
Where would the SCRUM Team using Kanban also inspect and adapt the definition of "Workflow" to optimize the flow in the next Sprint.
The Sprint Retrospective
44
What is "Flow" related to Kanban?
It is the movement of customer value throughout the product development system.
45
The SCRUM Framework combined with Kanbans hyperfocus on 3 items helps to deliver optimal customer value - name the 3 items.
**TVF**
1. Transparency
2. Visualization
3. Flow
46
Who controls the what limits are and how it will apply?
The SCRUM Team
47
True or False - Each Kanban team must define its own "Flow"?
True
48
How does Kanban optimize "Flow"?
By improving the overall efficiency, effectiveness, and predictability of a process.
49
What forecasts how long a work item should take a given item to flow from start to finish within your workflow?
A Service Level Expectation (SLE)
50
What are the three foundations that uphold SCRUM Theory and Kanban Theory?
\* Transparency \* Inspection \* Adaptation
51
Must the work items correspond to the Product Backlog items or other parts of the Sprint Backlog or SCRUM?
No
52
What are the two parts of the Service Level Expectation (SLE)?
\* A time estimate \* A probability estimate Example - (85% chance this item will finish in 8 days)
53
What is the most central concept to Kanban?
The "Workflow"
54
What is the Service Level Expectation (SLE) based upon?
The SCRUM Team's historical cycle time, and once calculated should be posted to the Kanban board.
55
Does a work item have to complete each step in the "Workflow"?
No
56
Whose responsibility to ensure the continuous proactive, active, and reactive management of work items in progress?
The SCRUM Team
57
What major practice does the Kanban Guide remove as part of the SCRUM Guide?
None - the SCRUM Guide applies in its entirety.
58
What is the difference between a "Pull" system and a "Push" system?
Pull systems trigger when the SCRUM Team starts work on an item (i.e. pulls) and only when there is a clear signal that it is time to do so. A "Push" system demands that work be started on an item whenever requested.
59
When the SCRUM Guide uses "Explicit" what exactly does it mean?
That the policies are written down or visualized somehow and that the whole SCRUM Team understands them.
60
Cycle time is a lagging indicator? (True or False)
True
61
A Service Level Expectation (SLE) target reflects the Scrum Team's aspirations toward a reliable cycle time. (True or False)
True
62
When using Scrum with Kanban you can release multiple times during the Sprint? (True or False)
True
63
What are some of the impacts of reducing batch sizes?
1. Improving efficiency due to faster feedback loops. 2. Higher motivation due to seeing work getting done and delivering value earlier. 3. Lower efficiency due to overhead / transaction costs in case the batch size is too small. 4. Highlight a need to work to improve processes / infrastructure to reduce the pain frequent costly overhead.
64
The purpose of a Scrum Team's SLE is to allow teams to give each PBI a commitment to a due date as part of Sprint Planning. (True or False)
False
65
Workflow can be thought of as the "Team's policy" for how to get work to "Done". (True or False)
True
66
In a flow-based system, the number of tasks is not necessarily limited, rather then amount of value-generating work items is limited. (True or False)
True
67
Work Item Age is a leading indicator for the length of the Scrum Team's feedback loop for that (in progress) item. (True or False)
True
68
The WIP Limit can only be changed during the Sprint Retrospective. (True or False)
False
69
True or false: When using Kanban with Scrum, the Development Team can start working on ANY new work item that wasn't initially selected in the Sprint Planning meeting.
False
70
What is correct about Sprint Goals when Kanban is used with Scrum?
The Sprint Goal becomes more important because the team needs it to decide about unplanned work.
71
True or false: Limiting WIP creates a pull system.
True
72
True or False: Scrum has a WIP Limit by default, even without Kanban.
True
73
Who's responsible for setting WIP Limits?
It depends on the scope and boundaries of the subject.
74
True or false: Scrum elements (roles, events, and artifacts) do not change at all when used with Kanban.
False
75
Why might the Scrum Team change their WIP Limit?
Because they want to increase focus and collaboration
76
True or false: Reducing batch size always increases efficiency.
False
77
What types of information are visible on a Cycle Time scatterplot?
1. Cycle time outliers 2. Cycle time trends
78
True or false: When using professional Kanban with Scrum, you're not allowed to exceed WIP Limits.
False
79
Which two of the following are necessary on a Kanban board?
1. WIP limits 2. Workflow visualization
80
True or false: Little's Law can be used to forecast some flow metrics based on historical data of the other metrics.
False
81
When Scrum is used with Kanban, some of the Sprint capacity should be reserved for unplanned work.
False
82
When are we allowed to make changes to the definition of Workflow?
At any time
83
What does an 85% 7-day SLE mean?
We expect about 85% of work items to be finished in 7 days or less.
84
What two things are likely to happen when WIP is limited?
1. Shorter feedback loop 2. More sustainable pace
85
Who is allowed to increase the Sprint WIP Limits in response to emerging urgent work?
No one
86
Which two of the following should exist in every SLE?
1. A range of durations 2. A probability
87
WIP
88
Approximate average cycle time
89
Average throughput
90
Arrival time
91
More work entering than leaving
92
Age: 5
Stage: In progress
93
These zones are based on the SLE and represent the chance of meeting the SLE
94
To help the team focus on the work items that are at most risk of missing the SLE
95
4
96
50%
97
True or False: If a Scrum Development Team uses tasks, then their WIP limits should primarily apply to tasks in the Sprint Backlog.
False: Limiting tasks in progress can be useful but doesn’t replace limiting WIP at the PBI level. We care about flow of value/learning. This is the flow of PBIs.
98
True or False: The purpose of a Scrum Team's Service Level Expectation (SLE) is to allow teams to give each PBI a commitment to a due date as part of Sprint Planning.
False. SLE CAN be used in Sprint Planning to provide PO and stakeholders with an idea towards the service level that can be expected from the team. That doesn’t include providing a specific date for each PBI in the SBL. The SLE enables the Development Team to forecast a finished date at a certain confidence level once the item has been started.
99
What does the Work Item Aging chart show?
For each item on the Kanban board how long ago has it been pulled into WIP.
100
True or False: Workflow can be thought of as the “Team’s policy” for how to get work to “Done”.
True. This is similar to how the definition of Done can be considered the team’s policies for what "Done" looks like.
101
True or False: Scrum Events, Roles, Artifacts, and Rules are changed when using Scrum with Kanban. For example, the Scrum Team might choose to no longer conduct a Sprint Retrospective when using Kanban with Scrum.
False. Adding Kanban to Scrum provides a technique to help the Scrum Team focus on driving a continuous flow of activity, but does not negate value provided by the Scrum Events, Artifacts, Roles, or Rules.
102
Which of these might be true when reducing batch sizes:
1. Improving efficiency due to faster feedback loops.
2. Higher motivation due to seeing your work get done and deliver value earlier.
3. Lower efficiency due to overhead / transaction costs in case the batch size is too small.
4. Highlight a need to work to improve processes/infrastructure to reduce the pain of frequent costly overhead.
All of them
103
True or False: A Service Level Expectation (SLE) target reflects the Scrum Team’s aspirations toward a reliable cycle time.
True. Regardless of whether it is based on historical data or not, a Service Level Expectation (SLE) indeed is an expectation the team sets to themselves. It should be aspirational yet realistic and reliable. Aspiring and then missing most of the time is not what an SLE is about.
104
True or False: In a flow-based system, the number of tasks is not necessarily limited, rather the amount of value-generating work items is limited.
True. Even though multiple tasks are completed, none of them has created something of value for the customer. Only when a Product Backlog item is complete is the value it created and the feedback loop closed. Our goal when improving flow is to tighten the feedback/value loop - so we apply flow improvement techniques such as Limiting WIP to the valuable items - the the Product Backlog Items.
105
True or False: The main role of WIP Aging is to help identify flow bottlenecks; where work may be impeded or constrained.
False. While in some cases observing old age across multiple items in a certain area of the workflow can help identify bottlenecks, the main role of the Work Item Age metric is to identify specific items that are struggling and require attention. Bottlenecks/systemic constraints are typically identified by looking at the queues on the board as well as charts like the Cumulative Flow Diagram.
106
Who owns the Kanban board in the Sprint Backlog?
As the Development Team owns the sprint backlog, visualizing the workflow within the sprint is also owned by the Development Team.
107
True or False: Optimizing WIP limits will result in decreased productivity.
False. WIP limits help create focus by reducing multitasking which can in fact increase productivity. A lower WIP limit which increases focus can result in higher productivity.
108
Which metric is most valuable for Sprint Planning?
When planning a sprint our main interest is to figure out how many backlog items to pull into the Sprint. Throughput of previous Sprints is the most useful in figuring this out. An advanced technique would be to use Monte Carlo simulation using this throughput data in order to figure out confidence-levels for various amounts of items in the Sprint Backlog.
109
True or False: Cycle time is a lagging indicator.
True. You can only measure cycle time by looking at historical data. It is an indicator and point of reference but should be used carefully when predicting the future.
110
True or False: When it comes to using Kanban for the Sprint Backlog, the Development Team owns the way they work, their definition of “Done”, as well as their definition of "their Workflow".
True. The accountabilities/responsibilities defined by the Scrum Guide still apply when adding the Kanban practices.
111
True or False: When using Scrum with Kanban you can release multiple times during the Sprint.
Even with pure Scrum you can release as often as you want during the Sprint. Bringing Kanban into the picture doesn’t change this. Kanban actually helps bring to light the potential and value of reducing batch sizes e.g. for releasing and driving Scrum teams to consider releasing more often during the Sprint.
112
