FIXING YOUR ORG BY CONTINUALLY BREAKING IT
•
6 gefällt mir•7,413 views
The document summarizes key points from a presentation by J. Paul Reed on continually breaking and fixing an organization to promote resilience. It discusses establishing a culture of continuous experimentation through small, targeted experiments aimed at cultural alignment rather than process replication. Experiments should specify target conditions rather than solutions and focus on revealing and removing obstacles over time through reflection.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Andere mochten auch
Andere mochten auch (14)
Ähnlich wie FIXING YOUR ORG BY CONTINUALLY BREAKING IT
Ähnlich wie FIXING YOUR ORG BY CONTINUALLY BREAKING IT (20)
Mehr von J. Paul Reed
Mehr von J. Paul Reed (8)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
FIXING YOUR ORG BY CONTINUALLY BREAKING IT
- 1. FIXINGYOUR ORG BY CONTINUALLY BREAKING IT J. PAUL REED RELEASE ENGINEERING APPROACHES DEVOPS DAYS AUSTIN 2015
- 2. J. PAUL REED AKA “The Sober Build Engineer” @SoberBuldEng on Principal at Release Engineering Approaches Chief Delivery Officer at Praxisflow 15+ years in build/ release engineering
- 3. ALSO AVAILABLE ON ITUNES www.theshipshow.com @ShipShowPodcast @eciramella @buildscientist @cheeseplus @sascha_d @petecheslock@SonOfGarr @beerops
- 4. ALSO: I AM NOT THIS GUY
- 5. ALSO NOT THIS GUY
- 7. HEARD OF THIS BOOK?
- 8. IMPORTANT DETAILS The Three Ways of DevOps The Four Types of IT Work Interviews with The Business™
- 9. 3 WAYS RECAP 1. Systems Thinking 2.Amplify Feedback Loops 3.Culture of Continuous Experimentation & Learning
- 14. MIND TOO BLOWN?
- 15. MIND TOO BLOWN?
- 17. “BRB,TOO BUSY TO IMPROVE”
- 18. “WELL,THAT USED TO BE OUR WEBSITE...”
- 19. RARE IN THE WILD
- 20. CONTINUOUS...
- 26. The evidence of the last 20 years indicates that trying to copy or reproduce another company’s tools, techniques, or principals does little to change an organization’s culture. — Mike Rother
- 29. DevOps
- 32. ON “COMPANY” “CULTURE” “Move fast, break things.”*
- 34. ON “COMPANY” “CULTURE” “Context, not control.”
- 36. ON “COMPANY” “CULTURE” “A ‘Have Coffee’ culture”
- 37. Culture Is Not Important, but Cultural Alignment is critical
- 38. EXPERIMENTS, IN JUST FOUR EASY STEPS!
- 39. EXPERIMENTS OVER THE LONG TERM
- 41. “Let’s do The DevOps!” Retrospectives Continuous Integration Kanban Continuous DeliveryConfiguration Management Developers Carry the Pagers! Docker Docker Docker
- 42. THE IMPORTANCE OF A TARGET CONDITION (not your idea versus my idea about what we could do) and brings people’s efforts into alignment. — Rother [A] target condition... creates a challenge that depersonalizes a situation
- 46. CYNEFIN SIDEBAR
- 47. CYNEFIN SIDEBAR
- 49. MAN ON THE MOON
- 50. WEEKLY MEETING OF SUCK
- 51. TAKING TIME TO LOOK IN THE MIRROR
- 52. GAME ON!
- 53. PEBBLE THEORY OF CHANGE
- 54. PEBBLE THEORY OF CHANGE Drain until you can see the rocks, i.e. obstacles; then remove those obstacles
- 55. PEBBLE THEORY OF CHANGE Drain until you can see the rocks, i.e. obstacles; then remove those obstacles Don’t target the rocks you “know” are there
- 56. PEBBLE THEORY OF CHANGE Drain until you can see the rocks, i.e. obstacles; then remove those obstacles Don’t target the rocks you “know” are there Don’t dredge up the whole swamp
- 57. [T]he ability of your company to be competitive and survive lies not so much in solutions themselves, but in the capability of the people in your organization to understand a situation and develop solutions. — Rother
- 58. Operability?
- 61. Resilience. WHY?
- 63. J. Paul Reed soberbuildengineer.com @SoberBuildEng www.release-approaches.com Simply Ship. Every Time. Anonymous feedback: sayat.me/jpaulreed
- 64. Adoption of Agile & DevOps methodologies is a journey, and every person and organization’s journey is going to be different. -J. Paul Reed DevOps inPractice J. Paul Reed http://www.oreilly.com/webops-perf/free/devops-in-practice.csp