This document discusses cloud adoption frameworks and provides examples. It begins by defining cloud adoption frameworks as collections of best practices to help organizations successfully migrate to the cloud and avoid common mistakes. It then provides overviews of the Microsoft and AWS cloud adoption frameworks, describing their strategic and tactical components. The document also presents three mini case studies showing how organizations have used cloud adoption frameworks to successfully migrate applications and infrastructure to the cloud. It concludes that cloud adoption frameworks provide both a high-level strategic view and tactical guidance for a successful cloud migration.
43. “The architecture, technical practices, and cultural
norms that enable us to…
Increase our ability to deliver applications and
services…
Quickly and safely, which enables rapid experimentation
and innovation, and the fastest delivery of value to our
customers…
While ensuring world-class security, reliability and
stability…
… so that we can win in the marketplace”
Gene Kim, DevOps Enterprise Summit, October 2018
54. Challenges
• Fintech scale-up with recent Aviva investment
• 10x UK growth targets, plus international plans
• Physical datacentre infrastructure
• Limited operational capabilities
Solution
• Everything-as-code cloud migration
• Database re-platforming into Azure SQL
• Ongoing modernisation of .NET systems
• 24x7 application platform operations service
Result
• Robust, scalable and performant cloud platform
• FCA and GDPR compliant
• Accelerated product development and speed to market
Solid foundations for rapid growth
55. Challenges
• ‘CSS Disease’ – Can’t Ship ‘Stuff’
• 9 month release cycle
• Not meeting business requirements
Solution
• Everything-as-code cloud migration
• End-to-end DevOps pipeline
• Introduction of Agile methodologies
Result
• 9x acceleration in release cycles
• 60% reduction in testing time
Accelerated Software Delivery
56. Challenges
• Hard deadlines to exit 5 global datacentres
• Migration falling further behind schedule tackling the ‘long tail’
applications
• Strong desire to maintain engineering principles
Solution
• Automated VM migration of Windows systems
• Containerisation of Linux systems
• Retro-fitted CloudFormation scripts all source controlled
Result
• Successful migration, back on schedule
• Unlocked savings in excess of $12.5 million
• Successfully migrated challenging legacy applications
Successful Exit of Five Global Datacentres
Where you start across the DevOps pipeline is very dependent on the organisation
Where is your constraint?
Where you start across the DevOps pipeline is very dependent on the organisation
Where is your constraint?
The reality is that the Agile bit has gotten a lot better… and the bottleneck (the constraint to delivering value) was rapidly becoming the Ops bit…
Lead times for servers too slow (even in virtualised environments)
Too busy fighting fires
Badly designed processes
Too many silos even within operations
And of course the biggest bottleneck – outsourcing…
Confluence of migration triggers/catalysts [including outsourced datacenter contract expirations, integrating acquisitions, urgent capacity needs, software and hardware refresh, end of support, security threats (e.g., Spectre), compliance (e.g., GDPR), Need to deliver applications faster]
2018 will be a big year for cloud migration. This is a secular trend.
Essential Characteristics
Service Models
Deployment Models
What does a modern cloud look like <click>
The Azure Dublin datacentre (EU West)
Or in the words of Sir Isaac Newton…
Also – it is a move away from something that is just a commodity
Microsoft’s is a bit of a halfway house between a CAF and a CMF…
Teams that adopt both Cloud and DevOps together report an 81% acceleration, compared to a 52% or 53% boost for DevOps or Cloud in isolation. 2
When we merge technology and working practices in this way, the things we’re seeing are:
Everything-as-code
This is the foundational practice that everything stems from
Operability-by-design
Operability requirements, or non-functionals, become first class citizens
Considered at design time, not just transition time
Cloud-native services
Use of technology and automation to do things better, faster and cheaper
Agile and lean practices
Small batch sizes
Fewer queues, fewer handoffs
With risk managed by repetition
Aligned goals
less conflict between individual incentives or team/functional incentives, and the things that really matter
2 https://www.ca.com/us/modern-software-factory/content/devops-and-cloud-better-together.html
Click
Click
Click
Click
Click
So when we looked patterns practices and cultural norms we found they broke down into 5 key areas – which leads to what’s called the CALMS model of DevOps <click>
What they found was that high performing IT organisations were different in 5 key areas…
Culture – they embraced change, were more autonomous and more empowered
Automation – they were leveraging the latest automation tools like Puppet, Chef and Ansible
Lean IT – they were embracing Lean IT principles borrowed from manufacturing (particularly automotive and the Toyota Production System e.g. Kanban) but more importantly focussing on small batch sizes and the flow of work through the system
Measurement – they were using advanced measurement techniques to provide constant feedback on their customer needs, and the impact of their IT initiatives. Less opinion, more data science!
Sharing – a focus on breaking down silos between departments and sharing knowledge and best practice, often using ideas drawn from open source software development.
Let’s quickly drill down into 2 of those in a bit more detail – breaking down the silos and the flow of work… [click]
Where you start across the DevOps pipeline is very dependent on the organisation
Where is your constraint?
The idea of a DevOps product delivery team is that they own a defined product from initial design and development right through into production deployment AND operations – Dev & Ops together in a vertically integrated team.
The product owner is empowered to prioritise the backlog of work, based on the organisational goals, customer needs and the fast feedback of data from customers and product (remember the M for measurement in CALMS).
The goal here is to balance out the “user stories” (new features) with the “Operability stories” (things that make it easier to manage, reduce outages or cloud hosting costs etc).
All of this underpinned by a focus on automating as much as possible, to free up time for higher value work.
Cloud Enabled
DevOps Optimised
Integrated Systems API’s
Agile & Lean Process
Skilled Workforce
Changing behaviour is hard but behavioural change moves in a fairly predictable way.
What we often see is what we call the Icecream sandwich model of organisational change
C suite want it because they don’t want to end up like Paul Pester…
Engineering want it because they want to learn all those shiny new skills (cos we like shiny!)
Middle Management… are terrified of letting go of command & control because they don’t know how to LEAD so they are frozen in fear…