.svg "logo-sketch-development"){kind=logo}
In an earlier engagement, Sketch Development Services provided the client with a Cloud Enablement strategy, laying out a plan to productize the Cloud Center of Excellence's (CCoE's) services and tools for easier cloud adoption by the client’s development teams. In tandem with that is a ramped-up roll out whereby a CCoE Migration Team (or Teams) would assist dev teams in integrating these IaC tools, identifying any gaps or issues with CCoE’s toolset along the way.
The client asked Sketch to help establish a migration team, establish some standard processes and best practices, then start moving Centene applications into AWS.
Sketch and the CCoE team spent time prior to this engagement building some prerequisites:
The migration team’s goal was to start porting some applications into AWS using these tools and products. As this was the first integration of these tools with teams outside of the CCoE scope, it was expected that the road would be bumpy, but this team would smooth things out for future iterations of the IaC integration.
Sketch brought some veteran AWS developers who also have a wide range of experience in automation, CICD pipelines, DevOps tools, IaC, system integrations, and programming languages. The primary goal was to find commonalities and patterns to make each migration repeatable (in other words, “fast!”). Still, because no two teams are identical, we worked closely alongside the client’s team members to gain an understanding of their specific needs to find the best path forward for migration into AWS.
Throughout this engagement, we were able to accomplish the following:
Sketch Development Services got the ball rolling by migrating three teams’ applications into AWS using the new templates and enhanced CDKtf products. We found patterns in these initial migrations that were then baked into the IaC templates for easier repeatability.
Through a knowledge transfer consisting of discussions, Confluence documentation, team seminars, and code reviews, Sketch imparted the skills the CCoE team needed to continue with dev team migrations at an ever-increasing scale.
We hope these are the kinds of outcomes you were looking for. If you want to learn more about the work that went into this project, we're happy to answer your questions.
Better yet, let's talk about whichever project you were mulling over that brought you here. We love to talk shop, and the first few conversations are always free.
