DevOps and Agility with Visual Studio, Azure and Scrum
summary
Argues that success needs concrete practices not buzzwords, showing teams who ship every 30 days versus ones with no source control who edit code on production servers (fails); cites a product with 90 teams across 12 locations in 9 countries as a coordination anti-pattern and an insurance shop with 600 devs and 400 testers as evidence that lack of automation breaks delivery. Recommends continuous integration and delivery, definition of done and quality bar, and treats DevOps as a pickable toolkit (feature flags, telemetry, bridge to ALM).
AI-written summary · about
chapters (36)
- 0:00Intro
- 3:17Amateur vs Professional
- 3:45Callabula
- 4:13Working software
- 5:29Agile Scrum
- 6:36Feel to Deliver
- 7:08Scrum Rules
- 10:44Scrum Checklist
- 11:18Product Owner
- 12:15absentee product owner
- 14:31stretch goals
- 15:32product owners
- 17:25telephone game
- 18:54scrum master
- 19:53vanity metrics
- 23:43focus on engineering
- 23:53engineering standards
- 24:11code reviews
- 24:52compile deploy
- 28:16get feedback
- 30:53quality
- 34:54no ops
- 36:27DevOps words
- 36:50Tech debt
- 38:03Engineering practices
- 38:25We dont have values
- 38:57We need courage
- 39:26Focus
- 40:18Commitment
- 41:10Respect
- 42:27Open
- 44:29Professional
- 44:39Common Sense
- 45:22Scrum Guides
- 47:44Questions
- 50:32Application Lifecycle Management
related talks
01h 00mDevOps – Value at Speed
54mEffective DevOps for Organizations
47mArchitecting for DevOps and Continuous Delivery
39mPutting the XP in Scrum
45mMarried to DevOps
30mA Story of DevOps Transformations
48mContinuous Delivery: Tales from Windowsland
01h 02mBuild a DevOps Culture: Microsoft's Journey to adopt an Agile Mindset and DevOps culture