From Dev Opps to DevOps
summary
Converted a large Windows-centric monolith into hundreds of deployable components, built a platform-agnostic packaging system (the Mitchell package manager written in Python) and a visible CI/CD pipeline, cutting deploys from hundreds of minutes to minutes and moving from nightly war rooms to deployments on every check-in. Developer coding time rises from 40% to 60% coding, the team earns a celebrated white week of no outages, and remaining work focuses on DB schema automation and Windows tool gaps.
AI-written summary · about
chapters (4)
- 0:00Start
- 7:10EPISODE 2: AGILE CULTURE
- 13:26CICD / DevOps Challenges * Monolithic legacy enterprise applications - Availability of CKD tools that support Windows * Undocumented architecture and orphan components Departmental silos in release processes - Micro-cultures in different teams
- 25:38INITIAL RESULTS
related talks
39mPutting the Ops in DevOps
07mWhat we learned moving 65,000 Microsofties to DevOps...
44mDevOps at Microsoft: Our Internal Transformation Story
05mDevOps over time
33mFrom 0 to DevOps in 80 days
49mOur DevOps journey – Microsoft’s internal transformation story
01h 01mA team's transition to Continuous Delivery
30mWhat's It Like When DevOps Is Just Another Day at the Office?
