You may not have the kind of resources you need when you start.

Your people have to spend a lot of time supporting the on-going development and release so they don't have the time to work on automation.

Your architecture may not be as clean and well defined as you would like.

You just started with test automation and your coverage is still very low.

Above all, your customer and delivery partners are doubtful of the new initiative and are not willing to change.

In this talk, I will share the story of a successful DevOps implementation in a traditional organization with many these constraints. My experience in leading this journey taught me that if you can take a realistic assessment of your situation and plan your implementation carefully, it is entirely possible for a traditional organization with large and complex computing environment to adopt DevOps practices, in order to deliver software faster with significantly better quality, and at the same time do it in a way that makes peoples? lives much easier.