Approach 1.
Full/Hybrid Cloud Adoption
Riverland Reply presents a possible scenario of the full approach in which there are multiple DevOps teams of around nine members each. All team members have access to the provisioning system and the deployment platform. Also, each one of them affects the security of the application, offers support service and is entitled to change the production environment.
Riverland Reply presents two different methodologies based on knowledge sharing that can be applied to the Full/Hybrid Cloud adoption approach.
COMPETENCE CENTER METHODOLOGY:
The first methodology is about the concept of “competence center“, by which
groups of people across teams are sharing their knowledge and compare their ideas on a specific topic. In the picture below, the competence centers are highlighted with the cross-team boxes. Having a specific center of competences allows facilitating the communication among the teams. This is a benefit for managing the software lifecycle. For competence centers within a full approach,
automation everywhere is a key success factor.
ORIENTATION SPLIT METHODOLOGY:
The second methodology focuses on the teams’ expertise. The aim of the methodology is to
figure out which team is more likely to be efficient upon a specific technological topic. The example below shows one team is oriented in infrastructure automation, another one in feature development, etc. In the presented case, the concept of the competence center is also applied, but in this case it is needed to
keep all the teams enable to work on all the possible implementation topics.
