6. • More frequent releases
– How do we elegantly shift from long release cycles to monthly, or
even daily?
• Customer responsiveness
– How can we help set customer expectations about when bug fixes
and feature requests go live?
• Stakeholder transparency
– How can we make sure everyone understands the release pipeline
so they can do their jobs?
• Compliance & regulation
– How can we feel confident we’re properly tracking, managing, and
approving our releases?
7. • Manual
– Error prone, time consuming, does not scale!
• Different deployment processes per environment
• Coordination between Dev, Ops, and stakeholders is
difficult
8. We need the release process to be more
• Repeatable
• Predictable
• Transparent
9. Plan REQUIREMENTS
BACKLOG
Construct Operate
RELEASE
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
Performance events
Integrated release
management
Collaborate
Kanban customization
Work item tagging
Release
Load Testing as a Service
Configuration-based
deployments
10. Testing time
DEV INT QA PROD
Team Foundation
Server
Coordination
Provision
Deploy
11.
12.
13.
14. • Create release pipelines
• Define approval workflows
• Automate deployments
• Provides visibility and full traceability