Step 4. Bring the work to the teams - Building a Cloud Operating Model

Step 4. Bring the work to the teams

We don't recommend building an entire Cloud Enablement Engine to support the whole business all at once. Instead, we recommend, think big, but start small. This gives your team and its customers the opportunity and to build and learn iteratively and incrementally, as they scale adoption.

The Cloud Foundation Team is the first product team. The team should be cross-functional, and represents all the roles and capabilities that will eventually scale into a full Cloud Enablement Engine. In staffing a product team, you are looking to balance four concerns or perspectives:

  • Viability: A customer and business perspective

  • Desirability: Of the products being created and the change being driven through the organization

  • Feasibility: A technical delivery perspective

  • Operability: Of the products in production

As cloud adoption grows, the Cloud Foundation team will need to increase and scale to support the pace and direction of your AWS customer journey. While every customer journey is different, a general pattern of successful cloud adopters follows a subdivide and specialize approach. In this approach the initial Cloud Enablement Engine is typically split into four product teams, one for the CBO and three in the CPE. For large organizations this process of subdivide and specialize continues again in line with the backlog of work.

The key roles required in the Cloud Foundation Team are:

  • Product Owner: Singularly accountable for the Cloud Enablement Engine's vision and its viability from a business perspective

  • Cloud Architects: Translates customer, business, and governance requirements into product architectures. You may have overall Cloud Architecture, or architects that represent Platform, Operations, and Security.

  • Cloud Engineers: Since the Cloud Platform Engineering teams run in a DevOps, you build it, you run it model, the Engineers on the team are responsible for both Development and Operations across the Platform, Operations, and Security domains.

Additional roles that are typically added (though may be part time) include:

  • Financial Analyst: Responsible for financial budgeting, tracking and reporting; show-back/charge-backs and cost optimization

  • Organizational Change Management Specialist: Responsible for making the move to cloud desirable for the organization through workforce preparedness, communications, training, resource and career management plans

  • Scrum Master: Facilitates Agile process and ensures forward progress towards business outcomes by the team