Minimum Viable Transformation (MVT)

Minimum Viable Transformation (MVT) is a nimble approach to cloud adoption that works for organizations of all sizes, from small teams to enterprises.

The key to MVT is to start very small, learn from the experience, and then scale up. In this blog post, I will describe the MVT approach and how organizations can use it to make the transition to the cloud.

Phase 1: Build a Cloud Tiger Team

The first step in MVT is to build a three-person Cloud Tiger Team, consisting of a Cloud Champion, Lead Architect, and Lead Engineer. These individuals will work together to write the first Vision for Cloud and migrate the first workload.

The first workload should be a “Favourite Child,” a product that is relatively straightforward and directly valuable to the organization’s core mission. This will allow the cloud journey to have a meaningful story from the beginning.

As contrast, I have seen some select the pilot workload based on least risk. While this also will give your team valuable experience, the lack of interest from other units will make it more difficult to grab attention, secure resourcing and get others involved.

Phase 2: Expand the Cloud Tiger Team

Once the first workload is in the cloud, the Cloud Tiger Team can be expanded into a Cloud Center of Excellence (CCoE). The CCoE should include additional roles, such as Cost Optimization Lead, Security Lead, and Platform Lead.

The extended team will write the first release of the cloud governance model and prepare for the first wave of migrations, which should include 2-4 products. An Application Operations Team may also be necessary if the product teams are inexperienced, but this may be eventually phased out as the teams mature to a DevOps operating model.

These events should be described as high level in your Vision for Cloud. This of it as a your Cloud Journey synopsis, which helps you set expectations and communicate the over approach.

Phase 3: Re-platform and Document the Cloud Operating Model

The recommendation is to re-platform with as few changes as necessary, and initially have the CCoE support in operations. Once the first wave is in the cloud, the team will document the first version of the cloud operating model, and the Platform Lead will establish their own Cloud Platform Team to support individual product teams in operations.

Remember that the Cloud Operating Model (COM) is a living document. Do not attempt to perfect it, but rather focus on achieving utility value.

This is also why I recommend against trying to write the COM before having migrated and operated something in the cloud; it is one thing to write a theoretic model, and a whole other thing to describe your actual actions in a consistent way.

The COM, then, is not a plan. It is a description of reality: this is how we operate our workloads in the Cloud.

Phase 4: Scaling the Operation

The next phase is scaling the operation. The CCoE will continue to support new migration waves and establish cloud best practices, such as Golden Images. Individual leads will also establish their own teams, such as the Cloud Security Team, who are responsible for establishing security guardrails and policies at the organizational level.

As individual Product Teams mature from traditional operations to DevOps, they will either optimize their product using a Distributed DevOps operating model or develop new features aggressively using a Decentralized DevOps model. The product teams will develop and operate the stack of their product as outlined in the Cloud Operating Model, which you should continue to update as the teams mature and acquire new capabilities.

In conclusion, MVT is a nimble approach to cloud adoption that can help organizations of all sizes make the transition to the cloud. By starting small, learning from experience, and scaling up, organizations can ensure a smooth and successful migration to the cloud.

Are you ready to start your Minimum Viable Transformation journey to the cloud? What are some of the challenges you foresee in making this transition? Share your thoughts in the comments section below.

Minimum Viable Transformation (MVT) is a highly effective and actionable approach to cloud adoption. It emphasizes starting with small, quick wins to achieve the necessary speed to avoid getting stuck in the "Valley of Despair". By focusing on the minimum viable steps required to reach the next level of maturity, MVT helps organizations move quickly and effectively towards a full-fledged cloud operating model. This approach enables companies to continuously improve and evolve their cloud operations, resulting in maximum business benefits.