Overview
“Shedding light on the services provided by the CCoE is equally important as the services themselves”
The CCoE is essential for accelerating cloud adoption in the organisation. The CCoE’s purpose, mandate, structure and position in the organisation should be laid out in a blueprint of the CCoE. However, it shouldn’t be taken for granted that the blueprint alone is enough to communicate to the rest of the organisation what services will be provided by the CCoE.
Visibility of the CCoE and clarity as to which services they provide is crucial. The CCoE operates at a speed much faster than the rest of the organisation, when it comes to cloud related subjects. There is a huge risk of an information gap developing in the organisation in terms of what is happening with cloud. This may result in a loss of interest or worse, resistance.
The CCoE must define and communicate what services they provide to whom and how. It is important to regularly evaluate the services provided. Do they need to be improved, are other services required? The CCoE should not make the mistake of deciding what is best for the organisation. The CCoE exists to facilitate after all.
A communication plan must be drafted about what information needs to be given to which people in the organisation, when it should be given, and how. It is good practice to identify the best means of communication (such as a Wiki or Intranet) that the CCoE can present, among other things, its service catalogue and information.
A CCoE that properly performs services portfolio management will make it easier for the rest of the organisation to find them and use them as a guide on cloud matters to speed up adoption of the technology.
Activities checklist
Initial:
- Defining the CCoE’s services
- Choosing a communication medium such as the organisation’s intranet
- Identifying the organisation’s information need
- Drafting a communication plan as to how, when and to whom, which information is provided
- Publishing CCoE Catalogue
Recurring:
- Updating the information provided regularly
- Revisiting the CCoE services portfolio and keeping track of to what extent the services offered are used and valued by the rest of the organisation
- Evaluating the needs of the organisation in terms of services and information on a regular base
- Executing the communication plan
- Maintaining CCoE Catalogue
RASCI
| cloud consultant | responsible | transformation consultant | supporting |
| cloud architect | supporting | cloud partners | |
| cloud security specialist | DevOps team | ||
| cloud developer | business stakeholder | consulting | |
| cloud engineer | architecture | ||
| cloud analyst | supporting | security | |
| product owner CCoE | accountable | finance | |
| management | informed | procurement |
