3. Monitor
Operate
Working software
in production
Value realization
4. What is it?
• A methodology of automation
• No more unexpected problems at
deployment time Solution
• A quality enhancer
• Early fails are the best way of understanding
systems’ complexity
• A business driver
• You spent a hour fixing a bug, but the fix won’t
be out before the first patch (average
waiting?)
5. What is it not?
Continuous
It doesn’t deploy!
Integration
Problem
Continuous Deployment
Deploy is tied to a certain environment
8. There is more to be added
• Web.config transformations
• Custom MSBuild tasks
• Custom WF activities
• They might incur in friction!
9. Link: Community TFS Build
Extensions
• Community-driven workflow activities
• Tons of contribution from Blue Badges
and MVPs (Mike Fourie, Richard Fennell,
Ed Blankenship)
• http://tfsbuildextensions.codeplex.com/
10. Case study: ACME Corp
ACME Corporation is a company willing to
employ the newest technologies in the
market to maximize earnings
They invested in Windows Azure with
satisfaction...
...they want more, with Visual Studio ALM
2012
11. Technical scenario
• Windows Azure Web Sites
• ASP .NET
• Visual Studio ALM 2012
• Visual Studio 2012 Ultimate
• Team Foundation Service
• Team Build 2012
12. Team Foundation Service + Azure
• We can link a Team Foundation Service
team project to a Windows Azure website
• Automatic deploy, redeployments, etc.
14. On premise…and in the cloud
• On premise we can get 100% flexibility,
but with a higher complexity rate
• The cloud avoids this giving us some
infrastructural constraints
15. No friction
• Continuous Delivery allows to create the
most friction-less process for software
development
• Technologies can be a great aid
(VSTLM…)