1、Designing Cloud Teams How to Build a Better Cloud Center of ExcellenceApril 20242Table of contentsExecutive summary 3Deep dive 6Team size(smaller is better)7 Cross-functionality 9Team purpose(projects vs.products)11 Building the right features(Agile)14 Building those features quickly(DevOps)15 Build

2、ing those features reliably enough(Error budgets)16Team types(apps vs.platforms vs.enablers)18 App teams 19 Platform teams 20 Enabling teams 21 Different team types produce different outputs 22 And their various governance models 23 Experimental governance model 24 Cloud Center of Excellence(CCoE)go

3、vernance model 25 Governance model for scaled,self-serve cloud adoption 26 Governance model for scaled cloud adoption with full operations/SRE support 27 Governance model spanning multiple business units 28Team priorities(personas,user journeys and OKRs)30 Personas 30 User journeys 32 Objectives and

4、 key results(OKRs)34Team environments(physical vs.virtual vs.hybrid)37 Physical 37 Virtual 38 Hybrid 39The faster your IT organization can migrate your workloads and modernize them in the cloud,the shorter your time to value.And yet,we observe our fastest customers outpacing our slowest customers by

5、 an order of magnitude(10 x)when migrating similar technical solutions.Why is that?The technical skills of your staff play an important role for sure,as do the regulatory requirements of your industry.Still,they dont add up to explain the up to ten-fold difference in speed.The single biggest lever t

6、o accelerating your time-to-value is the configuration of those IT teams whom you are trusting with the execution of your cloud strategy.Said differently:before you think about how to rearchitect your software you should think about rearchitecting your teams.The standard approach to addressing this