3. Build on one person’s machine Code and debug for weeks (months?) Manually deploy parts via file copy Run manual tests against deployed app

4. Build on one person’s machine Code and debug for weeks (months?) Manually deploy parts via file copy Run manual tests against deployed app Infrequent releases reducing business agility Inability to reliably reproduce builds Tedious and error-prone due to missing dependencies Code and debug for weeks (months?)

5. …so that was painful, but now we are in production Where the fun really begins

6. Uptime

7. AgilityQualityDevOps

9. The Microsoft Solution

10. Plan REQUIREMENTS BACKLOG RELEASE Operate Construct WORKING SOFTWARE Develop Operate Agile portfolio management Team Room Git Code Information Indicators.NET memory Dump Analyzer Visual Studio and System Center integration Build | Measure | Learn Integrated release management Collaborate Kanban customization Work item tagging Release Performance events Continuous Delivery Load Testing as a Service Configuration-based deployments Added in VS/TFS 2013

11. Plan Develop & testRelease Monitor & learn All stakeholders Developers & testers Operations

12. Any code commit may be released to customers at any point Feature toggles hide new features from some or all users until they are complete Cross-functional teams can help identify and remove bottlenecks