Change is not an event, its a process and mentality (Jimmy Janlén, Crisp)
•
2 gefällt mir•1,401 views
Ett mini-seminarie om att initiera och driva förbättringar i både det lilla och det stora. Hur initierar man ett förbättringsarbete. Hur lyckas man? Hur synliggör man resultatet? Hur gör man förändringen beständig? Om Agile och Kanban som ett förändringsverktyg. Om Kaizen. Om ryttaren och elefanten. Om att våga sätta djärva mål men också om att våga misslyckas ofta och tidigt. Exempel och historier från verkligheten och konsultlivet.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Empfohlen
Empfohlen (20)
Change is not an event, its a process and mentality (Jimmy Janlén, Crisp)
- 2. Soarian® 600+ people, 35 teams, Jimmy Janlén 5 countries • Agile/Lean Coach • Scrum Master • Agile Testing • Courses • Seminars 2
- 5. Change is not an single event, it’s a process and a mentality 2012-08-31 Jimmy Janlén 2012 5
- 6. Kaizen ≈ Continuous Improvement 2012-08-31 Jimmy Janlén 2012 9
- 7. Kaizen ≈ Improve for improvements’ sake, endlessly. 2012-08-31 Jimmy Janlén 2012 10
- 8. 11
- 9. The Red Queen Effect 2012-08-31 Jimmy Janlén 2012 12
- 10. “The Red Queen Effect” “In the future standing still Scott Bedbury will be lethal to any brand.” Global Branding Expert (Nike's "Just Do It”) 2012-08-31 Jimmy Janlén 2012 13
- 11. “The Red Queen Effect” “If you want to get somewhere else, you must run at least twice as fast as that!" 2012-08-31 Jimmy Janlén 2012 14
- 12. Kaizen ≈ Improve for improvements’ sake, endlessly. 2012-08-31 Jimmy Janlén 2012 15
- 13. Challenge Status Quo 2012-08-31 Jimmy Janlén 2012 17
- 14. Challenge Status Quo 2012-08-31 Jimmy Janlén 2012 20
- 15. Challenge Status Quo 2012-08-31 Jimmy Janlén 2012 22
- 16. Challenge Status Quo 2012-08-31 Jimmy Janlén 2012 23
- 17. Challenge Status Quo 2012-08-31 Jimmy Janlén 2012 24
- 18. Challenge Status Quo 2012-08-31 Jimmy Janlén 2012 26
- 19. Challenge Status Quo 2012-08-31 Jimmy Janlén 2012 27
- 20. Challenge Status Quo 2012-08-31 Jimmy Janlén 2012 29
- 21. Challenge Status Quo 2012-08-31 Jimmy Janlén 2012 31
- 22. Challenge Status Quo “I don’t know… That’s how things are done around here.” “That won’t work, we’ve already tried it.” 2012-08-31 Jimmy Janlén 2012 32
- 23. Challenge Assumptions 2012-08-31 Jimmy Janlén 2012 33
- 24. Challenge Assumptions “We are not allowed to do pair programming.” ReallY? 2012-08-31 Jimmy Janlén 2012 34
- 25. Challenge Assumptions “We can release a new feature within two days!” ”test 2 days? How do you dare to release code that often of unknown quality?” 2012-08-31 Jimmy Janlén 2012 35
- 26. 2012-08-31 Jimmy Janlén 2012 36
- 27. Where to begin? 2012-08-31 Jimmy Janlén 2012 37
- 28. Pain Boring tasks Delays Bottlenecks Waste Frustration 2012-08-31 Jimmy Janlén 2012 38
- 29. #1 - Never be to busy for improvements… 2012-08-31 Jimmy Janlén 2012 39
- 30. Make sure to KISS 2012-08-31 Jimmy Janlén 2012 40
- 31. Don’t ask for permission… Trust your feelings luke! 2012-08-31 Jimmy Janlén 2012 41
- 32. Don’t ask for permission… Automated Talking Scrum Wall 2012-08-31 Jimmy Janlén 2012 42
- 33. also… The bigger the immediate proposed change - the stronger the resistance. 2012-08-31 Jimmy Janlén 2012 43
- 34. let the PAIN guide you 2012-08-31 Jimmy Janlén 2012 44
- 35. Let the pain guide you Soarian® Hmmm… Setup dev. env. Gerilla scripts and - 5 days (novice) automation - 2 days (expert) 4 hours 2012-08-31 Jimmy Janlén 2012 45
- 36. Let the pain guide you Soarian® Setup dev. env. Gerilla scripts and Did calculations Spent 1 month Setup dev. env. - 5 days (novice) automation and presented optimizing, - 30 minutes - 2 days (expert) 4 hours for head of IT… re-factoring, automation, + Continuous Teams x Hours scripts, Integration Cost configurable in 5 minutes with XML (with automatic deploy) 2012-08-31 Jimmy Janlén 2012 46
- 37. Try visualization to reveal the Truth 2012-08-31 Jimmy Janlén 2012 47
- 38. Why isn’t this on the Is this ready System test for system environment testing? already? I don’t know The acceptance What to do testers wants today… higher quality delivered… Why aren’t we making progress ON System Testing? 2012-08-31 Jimmy Janlén 2012 49
- 39. 2012-08-31 Jimmy Janlén 2012 50
- 40. 2012-08-31 Jimmy Janlén 2012 51
- 42. Fail Early. Fail Fast. Fail Often. 2012-08-31 Jimmy Janlén 2012 53
- 43. Don’t be afraid to experiment 2012-08-31 Jimmy Janlén 2012 54
- 44. Adam Killander Blixttal: Krydda din demo med rollspel Problem: Too few stakeholders bothered to go to the sprint demo. Theory: The demos are boring Experiment: Making the Demos more fun “Drama Driven Demo” 2012-08-31 Jimmy Janlén 2012 55
- 45. Don’t panic if you don’t see immediate improvements 2012-08-31 Jimmy Janlén 2012 56
- 46. The Improvement Curve 2012-08-31 Jimmy Janlén 2012 57
- 47. The Improvement Curve 2012-08-31 Jimmy Janlén 2012 58
- 48. The Improvement Curve 2012-08-31 Jimmy Janlén 2012 60
- 49. The Rider and the Elephant 2012-08-31 Jimmy Janlén 2012 61
- 50. 2012-08-31 Jimmy Janlén 2012 62
- 51. “The Elephant” “The Rider” - Emotional - Rational - Instinctive - The Planner - The Doer - Thinker - Short term - Long-term Powerful together, but if the rider has to control and master the elephant, the elephant eventually always wins… 1) Direct the rider 2) Motivate the elephant 3) Shape the path 2012-08-31 Jimmy Janlén 2012 63
- 52. Set clear Motivating Goals 2012-08-31 Jimmy Janlén 2012 64
- 53. 2012-08-31 Jimmy Janlén 2012 65
- 54. Long Test phase 25 people. 3 teams. 1 product. “Poor respect/care for quality” Huge defect-list legacy (avg. age ~ 100 days) Long time between releases (~2/year) Delays opened up for Scoop creep… 66
- 55. 00 0 0 2012-08-31 Jimmy Janlén 2012 67
- 56. Strategy? Release every Rotating Joint Testing Bug alarm Sprint! Responsibility Result? “Higher respect/care for quality” Less Defect-legacy (avg. age 30 days) More frequent releases (4-6/year) Jimmy Janlén 2012 68
- 57. Joint testing - Release race: During two days, all three teams helped out with testing, packaging, defects, documentation, etc. All work tasks were put up and then they were up for grabs. 2012-08-31 Jimmy Janlén 2012 69
- 59. Revolution through Evolution with Scrum Kanban 2012-08-31 Jimmy Janlén 2012 72
- 60. Making changes Stick 2012-08-31 Jimmy Janlén 2012 73
- 61. Change don’t spread through Wikis nor through Lessons-Learned-Reports Lessons Learned 2012-08-31 Jimmy Janlén 2012 74
- 62. Change is like a virus, spreading through people 2012-08-31 Jimmy Janlén 2012 75
- 63. The Adoption Curve/Lifecycle Find your allies! How do you reach the early majority Who are theY? How do you transfer it How can the INto a virus? 2012-08-31 leaders help? Jimmy Janlén 2012 82
- 64. Daily Kaizen 2012-08-31 Jimmy Janlén 2012 83
- 65. Daily Kaizen 2012-08-31 Jimmy Janlén 2012 84
- 67. 2012-08-31 Jimmy Janlén 2012 87
- 68. Thank You! 2012-08-31 Jimmy Janlén 2012 88
- 69. Jimmy Janlén @ Online Blogg: Den Scrummande Konsulten Crisp http://jimmyjanlen.wordpress.com http://www.crisp.se/konsulter/jimmy-janlen Twitter: JimmyJanlen http://twitter.com/#!/jimmyjanlen LinkedIn: JimmyJanlen http://se.linkedin.com/in/jimmyjanlen Email: jimmy.janlen@gmail.com YouTube: JimmyJanlen http://www.youtube.com/user/JimmyJanlen 2012-08-31 Jimmy Janlén 2012 89
- 70. Recommended reading… 2012-08-31 Jimmy Janlén 2012 90