Overview
”Aim for the cloud! But deliver in small steps!”
Focusing on delivering customer value and shifting to continuous delivery leads to more and more autonomous teams. That is a common driver for organisations to adopt cloud. A waterfall approach trying to encompass every possible use of cloud from the moment the cloud journey starts is set for failure. The CCoE needs to be spearheading an innovative way of working.?
Autonomy requires mandate and mandate requires clear responsibilities. One of the first steps is determining who is responsible for what. If we acknowledge DevOps teams should have autonomy then old school demarcations of responsibilities, and the way the CCoE cooperates with partners, the business and other (expert) teams has to be redesigned, validated and optimised. ?
The way to work for the CCoE is in a repeating fashion, enabling constant upgrades through continuous interaction with teams. Priorities reflect those changes that add the most value.?
The CCoE will have its own Product Owner who will consult the Cloud Leadership Team, assuring the steps taken are in line with the overall strategic objectives. In most cases this way of working will be adopted by all teams involved in the transition to cloud, allowing a smoother transition in responsibilities and permissions. ?
The support of the CCoE for the purpose of increasing cloud maturity and the transition to cloud will be executed as transparently as possible. Every new minimum viable product will be demoed to interested parties and stakeholders. This way the CCoE will activate and grow the group of early adopters and move to delivering ‘earliest lovable products’; products users actually love and will tell their colleagues and even friends about!
Activities checklist
Initial:
- Adopting and implementing an agile planning process?
- Defining the mandate of the CCoE in relation to the responsibilities/tasks of surrounding teams and the rest of the (IT) organisation?
- Describing the organisational structure and WoW of the CCoE ?
- Analysing the impact on the WoW of the CCoE of the current (IT) organisation
Recurring:
- Reviewing, improving and document the way of working on a regular basis
RASCI
| cloud consultant | responsible | cloud partners | |
| cloud architect | consulting | DevOps team | consulting |
| cloud security specialist | consulting | business stakeholder | consulting |
| cloud developer | consulting | architecture | consulting |
| cloud engineer | informed | security | informed |
| cloud analyst | informed | finance | |
| product owner CCoE | informed | procurement | |
| management | accountable |