Creating a Cloud Center of Excellence - AWS Migration Whitepaper

Creating a Cloud Center of Excellence

The following are guiding principles for the creation of a CCoE.

  • The CCoE structure will evolve and change as your organization transforms. Diverse, cross-functional representation is key.

  • Treat the cloud as your product and the application team leaders as your customers. Drive enablement, not command and control.

  • Build company culture into everything you do.

  • Organizational change management is central to business transformation. Use intentional and targeted organizational change management to change company culture and norms.

  • Embrace a change-as-normal mindset. Change of applications, IT systems, and business direction is expected.

  • Operating model decisions will determine how people fill roles that achieve business outcomes.

Structure the CCoE to Prepare for Migration at Scale

Designing a CCoE to include people from across impacted business segments, with cross-functional skills and experiences, is important for successful migration at scale. you build subject matter expertise, achieve buy-in, earn trust across your organization, and establish effective guidelines that balance your business requirements. There is no single organizational structure that works for everyone. The following guidelines will help you design a CCoE that represents your company.

A CCoE is comprised of two functional groups: the Cloud Business Office (CBO) and Cloud Engineering (see Figure 4). The functions of each group will help you determine who to include in each group and in the larger CCoE.

The CBO owns making sure that the cloud services meet the needs of your internal customer, business services. Business services, and the applications that support them, consume the cloud services provided by IT. IT should adopt a customer-centric model toward business application owners. This tenet represents a shift for most organizations. It is an important consideration when developing your cloud operating model, CCoE, and cloud team approach.

The CBO owns functions such as organizational change management, stakeholder requirements, governance, and cost optimization. It develops user requirements, and onboards new applications and users onto the cloud. It also handles vendor management, internal marketing, communications, and status updates to users. You will select IT Leadership responsible for the cloud service vision, Organizational Change Management, Human Resources, financial management, vendor management, and enterprise architecture. One individual may represent multiple functional areas, or multiple individuals may represent one functional area.

The Cloud Engineering group owns functions such as infrastructure automation, operational tools and processes, security tooling and controls, and migration landing zones. They optimize the speed at which a business unit can access cloud resources and optimize use patterns. The Cloud Engineering group focuses on performance, availability, and security.

The following figure shows the functional groups that require representation within your company’s CCoE.

Functional organization of a CCoE

Figure 4: Functional organization of a CCoE