DEVOPS DAYS MTL 2018 - Jesse Hurkens
summary
Technology and a shiny pipeline do not fix culture, so the rollout starts with an initial assessment and executive sponsorship, selecting a complex-domain pilot team, isolating it as a start small incubation, and giving it authority outside heavy governance. Limit handoffs, adapt processes to regional strengths, and let practices emerge. Concrete results: release cadence goes from six months to biweekly, monoliths migrate toward microservices, teams operate as product+ops+engineering units with shared tooling, and incidents move to “fix forward” instead of rollbacks.
AI-written summary · about
chapters (7)
- 0:00DevOps fails without culture
- 1:25DevOps journey story
- 9:01Executive sponsorship key
- 12:42Classifying project complexity
- 17:23Building DevOps blueprints
- 23:09DevOps culture signs
- 24:56DevOps transformation results
related talks
27mInstilling DevOps Ways of Working in Large Enterprise...
22mEvolving DevOps Teams and Flexible Organizational Culture
01h 02mThe Enterprise DevOps Challenge
38mDevOps transformation – the good, the bad and the ugly
34m(Re)building an Engineering Culture: DevOps at Target
30mAdopting DevOps? You are aiming at the wrong target!
34mYou only have to change one thing to do the DevOps
59mTech leadership, one year after