Kaizen in Practice

Regional Scrum Gathering Nepal 2019 - Presentaion

1. Kaizen in Practice ]
3. Kiro Harada - 原田騎郎 ✤ Agile Coach / Domain Modeler ✤ Attractor Inc.
5. Objectives: ✤ A practical advice to improve your own process ✤ A guideline to evaluate your kaizen ideas/actions
6. Kaizen Patterns 改善模式 Build Personal Skills Create Slack Set-based Design Creating Skills Matrix Mapping Value Stream Team Dialogue Small Experiments One by One Team Good Approaches Facts vs. Opinion Sharing with other teams Team Standards Eliminate Rearrange Agree on Issues Combine Member Mentoring Simplify Continuous Learning Design Measurements Dynamic Stable Process Find Defects Early Ask for Help Build Quality-In Visualize Analyze Defects Continuous Improvements https://hub.attractor.co.jp/slides/19
7. Quick Overview of Kaizen 改善
9. http://commons.wikimedia.org/wiki/File:1924_NonStop_Shuttle_Change_Toyoda_Automatic_Loom,_Type_G_1.jpg
10. TWI To Make Your Work ✤ Make your process easier and safer Easier and Safer
11. TWI created a video called “Improvement in 4 steps”. It was shown in Japan in 1950 with the title “Kaizen Eno yon Dankai”. 「改善への四段階」
12. Eliminating Wastes In Manufacturing ✤ 7 Wastes / 7 浪费 / 7 फोहोर ✤ Transportation / 运输 / यातायात ✤ Inventory / 库存 / सूची ✤ Motion / 运动 / गित ✤ Waiting / 等待 / पखर्ँदै ✤ Over Production / 过度生产 / अिधक उत्पादन ✤ Over Processing / 过度过程 / प्रकृया भन्दा बढी ✤ Defects / 过度过程 / दोषहरू
13. Is Software Development Manufacturing?
14. Deployment process can be like a factory
15. Software Development? By Lisamarie Babik - Ted & IanUploaded by Edward, CC 表示 2.0, https://commons.wikimedia.org/w/index.php?curid=9546406
16. What are Wastes in Software Dev? 软件开发中的浪费? सफ्टवेयर िवकासमा फोहोरहरू के हुन्? http://agilemodeling.com/artifacts/classDiagram.htm
17. Our Resource is Limited
18. Processing Power?
19. Storage?
20. Network?
21. Is Time your dominant Resource? ✤ Giving much time to developers would not improve results unfortunately.
22. Attention is your constraint
23. System 1 vs. System 2
24. https://medium.com/@ryansheffer/founders-need-to-think-slow-move-fast-6b683e94c110
25. System 2 for Software Dev By Lisamarie Babik - Ted & IanUploaded by Edward, CC 表示 2.0, https://commons.wikimedia.org/w/index.php?curid=9546406
26. How long can you keep Your Attention? 你能保持多久注意力? तपाइँ कितन्जेल आफ्नो ध्यान राख्न सक्नुहुन्छ?
27. Attention Span is 40 seconds
28. Your Attention is easily distracted 注意力分散 ध्यान िवचिलत
29. Interrupts 中断 अवरोधहरू Office Space (1999)
30. रातो पहेंलो िनलो कालो
31. रातो पहेंलो िनलो कालो
32. 红蓝⻩⿊
33. 红蓝⻩⿊
36. Lack of Attention can Kill You 缺乏注意会杀了你
37. Where to pay your Attention? Pay Attention to Your Products / Quality / Customers. Pay Attention to creating a process that doesn’t need much attention. A process that needs a lot of attention is expensive.
40. Simplicity--the art of maximizing the amount of work not done--is essential. 以简洁为本,它是极力减少不必要工作量的艺术。 सरल्ता - नगरेको काम को मुद्रा बढाउने कला- जरुरी छ
42. Sleep restores your Attention Restore your Attention ✤ A picture of sleeping people
43. Limiting Distraction
44. http://commons.wikimedia.org/wiki/File:1924_NonStop_Shuttle_Change_Toyoda_Automatic_Loom,_Type_G_1.jpg
45. Experiment: ✤ Turn off your smartphones ✤ Airplane mode helps
46. How do you feel?
47. How existing practices save your attention
48. Limiting WIP TODO PBI #1 PBI #2 PBI #3 PBI #4 PBI #5 DOING DONE
49. Kanban (in manufacturing) is to hide long-term plan
50. Stop the Line Andon Cord https://blog.toyota.co.uk/andon-toyota-production-system
51. Scrum as an attention saving framework
52. ¶8 Collocated Team ¶9 Small Teams ¶15 Stable Teams
53. ¶35 Sprint Review
54. ¶54 Product Backlog
55. ¶82 Definition of Done
56. https://code.likeagirl.io/programmer-on-duty-eeab5a8ea6b7
57. Getting Things Done
58. “A wealth of information creates a poverty of attention.” Herbert A. Simon
59. Huge Product Backlog?
60. Manual Deployment Processes?
61. Add a PBI to delete a feature #99 n a e t Dele e r u t a e F d unuse
62. Unnecessary Attentions ✤ Large Product Backlog ✤ Long List of Definition of Done ✤ Manual Procedures (coversheet?) ✤ Multitasking ✤ Too many retrospective action items ✤ Kaizen Case Studies / Kaizen Examples
63. Slack, Slack, Slack Slack / 松弛
64. Curiosity is your KPI if you still have enough attention Curious? 好奇?
65. https://www.attractor.co.jp/
No comments...
アジャイルコーチ、ドメインモデラ、サプライチェーンコンサルタント。認定スクラムプロフェッショナル。 外資系消費財メーカーの研究開発を経て、2004年よりスクラムによる開発を実践。ソフトウェアのユーザーの業務、ソフトウェア開発・運用の業務の両方を、より楽に安全にする改善に取り組んでいる。

Related Slides