Beyond Kanban: Lean Thinking for Agile Teams
-
Upload
avpereira -
Category
Technology
-
view
3.691 -
download
6
description
Transcript of Beyond Kanban: Lean Thinking for Agile Teams
![Page 1: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/1.jpg)
Lean Thinking for AGILE Teams Beyond Kanban
Ana Valente PereiraAGILE Portugal 2011 - Porto
1
![Page 2: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/2.jpg)
The interest in KANBAN is growing in the AGILE Community... is LEAN taking over AGILE? is KANBAN replacing SCRUM?
2
![Page 3: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/3.jpg)
LEAN has it's roots in the auto industry
3
![Page 4: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/4.jpg)
Reducing LEAN to KANBAN is likedriving just half of your car
KANBAN
4
![Page 5: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/5.jpg)
Lean processes have 2 major pillars : Just in Time and Built In Quality Kanban is just a visual tool to implement Just In Time.
Just In Time Built In Quality
KANBAN
5
![Page 6: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/6.jpg)
Lean thinking is about understanding the management principles behind both pillars...
Just In Time Built In Quality
6
![Page 7: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/7.jpg)
...and also the principles behind people development and problem solving
holding both pillars together.
Just In Time Built In Quality
People and Problem Solving
7
![Page 8: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/8.jpg)
Base your management
decisions on a long term philosophy,
even at the expense of short term goals.
Generate Value for the Customer, Society and Economy.
Evaluate every function on the company in terms of its ability to
achieve this.
Principle #1
8
![Page 9: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/9.jpg)
Lean Practice: Value Stream Mapping
9
![Page 10: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/10.jpg)
Create Continuous Process Flow to
bring problems to surface.
Redesign processes to achieve high-value added, continuous
flow. Create flow to move material and information fast as
well as to link processes and people together.
Principle #2
10
![Page 11: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/11.jpg)
11
![Page 12: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/12.jpg)
Lean Practice: WorkCells
12
![Page 13: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/13.jpg)
Use Pull Systems to avoid
overproduction
Minimize WIP and inventory by stocking small amounts and frequently restocking based on what the customer process actually takes away.
Be responsive to shifts in customer demand rather than rely on schedules
Principle #3
13
![Page 14: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/14.jpg)
Lean Practice: Kanban
14
![Page 15: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/15.jpg)
Level out the workload. Work like the tortoise, not the
hare
Eliminate overburden (MURI) to people and equipment and unevenness (MURA) in the schedule
Eliminating waste (MUDA) is just 1/3 of the Lean equation
Principle #4
15
![Page 16: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/16.jpg)
Lean Practice: Heijunka
16
![Page 17: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/17.jpg)
Build a culture of stopping to fix problems, to get
quality right the first time
Build into your organization a support system to quickly solve problems and put
in place countermeasures
Principle #5
17
![Page 18: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/18.jpg)
Lean Practices:Andon
Jidoka,Poka yoke
18
![Page 19: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/19.jpg)
Standard work is the foundation for continuous
improvement and employee empowerment.
Allow creative and individual expression to improve the standard, then incorporate into
new standard
Principle #6
19
![Page 20: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/20.jpg)
Lean Practice: Standard Work Sheet
20
![Page 21: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/21.jpg)
Use Visual Control so no problems are hidden.
Use simple visual indicators to help people if they are deviating from a standard
condition
Principle #7
21
![Page 22: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/22.jpg)
22
![Page 23: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/23.jpg)
Technology support:
Use only reliable, tested technology that serves your
people and processes.
Often it is best to work out a process manually before adding technology to
support the process
Principle #8
23
![Page 24: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/24.jpg)
Lean Practice: Jidoka (Autonomation)
24
![Page 25: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/25.jpg)
"Before we build cars, we build people"
25
![Page 26: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/26.jpg)
Grow leaders who thoroughly understand the work, life the philosophy and teach it to others
The leader's job is to develop people.
Prin
cipl
e #9
26
![Page 27: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/27.jpg)
Develop exceptional People and Teams who follow your company's philosophy.
Make an ongoing effort to teach individuals how to work together as
teams toward common goals. Workgroups are the focal point for solving problems
and control of standardization
Use cross functional teams to improve quality and produtivity and enhance flow
Prin
cipl
e #1
0
27
![Page 28: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/28.jpg)
Respect your extended network of Partners and Suppliers by challenging them and helping them to improve
Pr
inci
ple
#11
28
![Page 29: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/29.jpg)
Genchi Genbutsu: Go see for yourself to thoroughly understand the situation
Solve problems and improve processes by
going to the source and observing and verifying
data
Prin
cipl
e #1
2
29
![Page 30: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/30.jpg)
Lean Practice: Onno Circle
30
![Page 31: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/31.jpg)
Make decisions slowly by concensus thoroughly considering all the options; implement decisions rapidly
Namawashi is the process of discussing
problems and potential solutions with all of the affected to collect their ideas and agree on a
path forward.
Prin
cipl
e #1
3
31
![Page 32: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/32.jpg)
Lean Practice: A3 Report
32
![Page 33: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/33.jpg)
Become a Learning Organization through reflection (Hansei) and continuous improvement (Kaizen)
View errors as
opportunities for leaning. Rather than
blaming individuals, take corrective actions and distribute knowledge
about each experience
Prin
cipl
e #1
4
33
![Page 34: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/34.jpg)
Practical Problem Solving
34
![Page 35: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/35.jpg)
"we don't build cars, we build software"Lean Principles for Software Development
35
![Page 36: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/36.jpg)
Lean Principles in SCRUM
36
![Page 37: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/37.jpg)
Principle#1 Long Term Philosophy: Value for the Customer
SCRUM promotes Value Driven Development and the Product Owner optimizes ROI (Value/cost) .. The process is optimized so that teams don't waste much time in non value added activities such as meetings ... but nobody is focused in removing waste from the process..
37
![Page 38: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/38.jpg)
#2 Continuous Process Flow.
SCRUM is designed to flow the work in small batches. The team organized like a work cell and the Scrum Master helps to remove impediments to Flow during the Sprint
38
![Page 39: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/39.jpg)
#3 Use Pull Systems to avoid overproduction.
SCRUM limits WIP by allowing teams to pull from the Product Backlog the items to be worked during the Sprint. Once they start working on them, the previous process should strive to have the next batch of PBIs groomed.
39
![Page 40: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/40.jpg)
#4 Level out the workload.
SCRUM fits customer demand into leveled schedules (sprints) aligning it to team capacity and promoting a sustainable pace of work
40
![Page 41: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/41.jpg)
#6 Standard Work:
SCRUM relies in empirical process control so standard tasks and times have no application but the Definition of Done defines the standard by which Product Backlog items are evaluated when “Done”. The team is empowered to improve this standard in Sprint Retrospectives
41
![Page 42: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/42.jpg)
#7 Visual Controls:
SCRUM makes problems visible in burndown charts ... Some teams use task boards to visualize task progress and impediments
42
![Page 43: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/43.jpg)
#9 Grow Leaders #10 Develop Teams #11 Respect Partners
The team is challenged to self-organize and decide how to achieve the sprint goals. The Scrum Master provides support for the team and Leads by mentoring and teaching. The PO manages relation with upstream processes
43
![Page 44: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/44.jpg)
#12 GoSee:
Scrum meetings provide an observation point for the process
44
![Page 45: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/45.jpg)
#13 Concensus #14 Reflection and Continuous Improvement
Sprint Planning is about gathering consensus on what to build in the next Sprint. Sprint Retrospectives provide points for reflection and continuous improvement of the process. Unfortunately knowledge is not shared beyond the project
45
![Page 46: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/46.jpg)
Lean Principles & KANBAN
46
![Page 47: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/47.jpg)
Principle#1 Long Term Philosophy: Value for the Customer
Using a Kanban System for Software, Value is Optimized with Classes of Service (SLAs). Work is scheduled by Cost of Delay
47
![Page 48: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/48.jpg)
#2 Continuous Process Flow..
Visualise Workflow: Map the Value stream as it exists and draw the card wall. Limit WIP to reduce lead times. Define, as well, limits for queues and buffer bottlenecks. Adjust empirically.
48
![Page 49: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/49.jpg)
#3 Use Pull Systems to avoid overproduction.
Pull work from the system only when there is capacity to do so.
49
![Page 50: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/50.jpg)
#4 Level out the workload.
Balance Demand against throughput. Make a study of the demand and allocate capacity by Work Item Type or Class of Service
50
![Page 51: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/51.jpg)
#6 Standard Work:
Make process policies explicit.
51
![Page 52: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/52.jpg)
#7 Visual Controls:
Cumulative Flow diagram shows work in progress at each stage in the system. Teams track also Lead Time , Due Date Performance and Defect Rates.
52
![Page 53: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/53.jpg)
We saw how LEAN management principles are broad enough to be applied in agile software development frameworks
53
![Page 54: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/54.jpg)
Agile frameworks leverage Lean to implement Just in Time processes and make problems visible...
54
![Page 55: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/55.jpg)
... But why don't we leverage Lean to solve thecauses of the problems as well ????
55
![Page 56: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/56.jpg)
#5 Stop and Fix, #8Technology support
Agile teams should focus on technology that automates software integration and testing... Stop to fix problems should be our mindset. We developed a continuous integration tool that shows teams their
technical debt: http://www.peakplatform.net/56
![Page 57: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/57.jpg)
#13 Concensus #14 Reflection and Continuous Improvement
Improve retrospectives with Root Cause Analysis and A3 Thinking to get visibility of Process Improvement (PDCA for the process and not only for the
product,...)
57
![Page 58: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/58.jpg)
LEAN is about developing People to solve Problems(if we were truly agile we should start here....
People over Processes...right???)
58
![Page 59: Beyond Kanban: Lean Thinking for Agile Teams](https://reader030.fdocuments.us/reader030/viewer/2022020110/54bd3cf34a7959ba1f8b4606/html5/thumbnails/59.jpg)
Ana Valente PereiraThank You
[email protected], twitter/apvpereira
Pictures (the good ones...not my drawings): © Ben Heine @ Flickr
59