This document discusses engineering culture and approaches to organizational change. It suggests starting with small experiments focused on principles rather than big projects or estimates. Changes to engineering practices and team organization are recommended before attempting broader cultural shifts. Experiments should be tracked and reviewed through retrospectives to effectively learn and reinforce changes. Patience is advised as people changes are more difficult than technology changes.

1. DevOps / Lean / Agile 2016 - Part 3
Diego Pacheco
diegopacheco
@diego_pacheco

2. @diego_pacheco
❏ Cat's Father
❏ Principal Software Architect
❏ Agile Coach
❏ SOA Expert
❏ DevOps Practitioner
❏ Speaker
❏ Author
diegopacheco
http://diego-pacheco.blogspot.com.br/
https://goo.gl/eEqvzl
About me...

3. Water-Scrum-Fall

4. Modern Agile

5. Experiments

6. 2016

7. Engineering Culture - Silicon Valley

8. Engineering Culture - Silicon Valley

9. Deliver Team VS Engineering Team
Delivery
Engineering
❏ Business CODE
❏ Day by-day work
❏ Dates and Scope
❏ Guidance
❏ Support and Tools
❏ Engineering for Engineers
❏ Open Scope AND Time and Materials

10. Engineering Culture

11. Engineering Culture

12. Mob Programing == Diego Pacheco's Story Dojo

13. Event Storming

14. HOLACRACY

15. HOLACRACY

16. Sociocracy

17. #noEstimates

18. #noProjects == Product Culture

19. Where to Start?
❏ Internal -> External
❏ Focus on Principles and Experiments.
❏ Retrospectives.
❏ Low Hanging Fruits
❏ Existent Problems
❏ Tech changes is easier than People changes
❏ Suggestion:
❏ Engineering / Tests
❏ Team Organization
❏ Techniques
❏ Change Patterns
❏ Katas / Change Canvas / Plan
❏ Small Experiments
❏ Implementation Retrospectives / Clinics
❏ Patience, Effective Learning and Reinforcement.

20. Change Canvas

21. Change Canvas

22. Experiment Tracker

23. Diego Pacheco
diegopacheco
@diego_pacheco
DevOps / Lean / Agile 2016 - Part 2