Management and Change - avoiding the rocks
Management and change are key concepts to successfully run businesses on the 21st century. The Lean Flow Paradigm requires a cultural change about how companies and teams are managed. The Kanban approach to change is evolutionary. Kanban simple practices are easily to adopt and effectively raise teams awareness of problems and leverage points. This talk is about how management and change work together to create the evolutionary environment road to success helping Change Agents to answer questions like: - Why Kanban? - How to deal with people's natural resistance to change? - What is tribal behavior? - Some unusual flow problems... With more than 3 years experience with Kanban on small, medium and big companies in Brazil, Rodrigo Yoshima will share on this talk several problems and solutions he faced on the field.
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (14)
Andere mochten auch
Andere mochten auch (17)
Ähnlich wie Management and Change - avoiding the rocks
Ähnlich wie Management and Change - avoiding the rocks (20)
Mehr von Rodrigo Yoshima
Mehr von Rodrigo Yoshima (10)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Management and Change - avoiding the rocks
- 1. ManagementManagement and Changeand Change avoiding the rocksavoiding the rocks Rodrigo Yoshima
- 2. Rodrigo Yoshima Software Developer since 1994 RUP (1999 – now) Agile (2003 – now) Kanban (2009 – now) LKU Trainer and Coach Creator of FlowKaizen and Wiphub Sailing addicted
- 13. Capacity 20th century Time Status Quo New Status Quo
- 14. Capacity 20th century “Revolution” Time Status Quo New Status Quo
- 15. Capacity 20th century “Revolution” Time Status Quo New Status Quo
- 16. Capacity 20th century “Revolution” Time Status Quo New Status Quo 21st century
- 17. Capacity KAIKAKU 20th century “Revolution” Time Status Quo New Status QuoKAIZEN 21st century “Evolution”
- 18. Capacity KAIKAKU 20th century “Revolution” Time Status Quo New Status QuoKAIZEN 21st century “Evolution” J-Curve of ChangeJ-Curve of Change Virginia Satir’s Change Process Model
- 26. Management Tool Demand Bug Tracking Bugs 32 168 What would you do? ?????
- 29. Management Tool Demand Bug Tracking Bugs 32 168 The real problem: - HIGH WIP ?????
- 30. TEST!DEV!
- 33. Management Tool Demand Bug Tracking Bugs 32 168 How do you feel about these numbers? ?????
- 39. WIP
- 41. $ 300/pound $ 600/pound $ 2.500/pound Example - Boeing 777 Engineer Supervisor Program Manager
- 43. Sprint Backlog Pronto Em Andamento You will take care of the boring demand on this Sprint.
- 44. Sprint Backlog Pronto Em Andamento Remark: The Cost-of-delay was sensitive
- 46. Sprint Backlog Pronto Em Andamento Bad Performance What would you do?
- 48. (5) Next Done (5) In progress We need explicit policies Manager The policy is up to you. I just need it defined.
- 49. (5) Next Done (5) In progress We need explicit policies Manager New policy: After doing 3 pink tickets you will select the next team member to do the 3 tickets
- 52. “People don't resist change. They resist being changed.” Peter Senge
- 55. IOS Android C++ Java Ruby Rails Module 1 Module 2 Module 3 Module 4 ... Module 17
- 57. ...
- 58. ...
- 59. ...
- 60. ...
- 61. ...
- 62. ... Process Perspective: Everything's OK!!! Management Perspective: It sucks!!!
- 63. Module 1 Module 2 Module 3 Module 4 ... Module 17 Work-in-progress (WIP)
- 64. ... CHAOS!!!!
- 66. Module 1ule 2
- 67. Module 1ule 2
- 68. Module 1ule 2
- 69. Module 1ule 2 To do Doing Done
- 70. Module 1ule 2 To do Doing Done
- 71. Module 1ule 2 To do Doing Done
- 72. Module 1ule 2 To do Doing Done
- 73. Module 1ule 2 To do Doing Done
- 75. Tribal Behavior People's identity and self-esteem Decentralization Level
- 76. Module 1ule 2 To do Doing Done
- 77. Module 1ule 2 To do Doing Done Problemas: Tribal Behavior Low Utilization (slack)
- 78. Module 1 (OK) To do Doing Done Module 3 Module 2 To do Doing Done
- 79. Module 1 (OK) To do Doing Done Module 3 Module 2 To do Doing Done
- 80. Module 1 (OK) To do Doing Done Module 3 Module 2 To do Doing Done Tribal Behavior: Solved with “Time”