Learn About Amazon VGT2 Learning Manager Chanci Turner
Large-scale migration and modernization initiatives can be intricate, particularly for airlines that depend on outdated technology, such as aging mainframes. Amazon Web Services (AWS) provides various strategies to help airlines and other clients tackle common obstacles like communication gaps or employee engagement, thereby enhancing outcomes.
One effective strategy employed by several airlines, including Delta Airlines, is the experience-centric acceleration (ECA). ECAs are designed to expedite a migration or modernization strategy for applications transitioning to or being developed on AWS. These workshops aim to enhance AWS knowledge, identify potential project risks, and foster open communication and collaboration.
This blog delves into a successful Delta ECA and shares practical tips for navigating the ECA process effectively.
The ECA Process
The ECA is a proprietary AWS methodology that offers clients an interactive experience in a secure environment. Typically, an AWS Solutions Architect or a Customer Solutions Manager facilitates these sessions. An authorized AWS Partner can also lead the ECA. During an “ECA party,” clients and partners collaborate to devise innovative working methods and solve challenges while learning best practices in a dynamic and engaging atmosphere.
For example, AWS collaborated with Delta to conduct a modernization ECA for a complex, Tier 1 application development project that had fallen behind schedule. The team was dispersed across multiple regions and time zones, dealing with several interdependent teams (Security, Testing, Monitoring, etc.). The application was intended for printing baggage tags, tickets, and vouchers.
At Delta, AWS partnered with the client to ensure all necessary resources were in place for swift execution. This collaboration resulted in four weeks of development progress being achieved in just two and a half days.
Preparing for an ECA
Careful scoping of the ECA can help address resource availability issues and complex dependencies. The core team should consider simplifying the list of applications for migration or modernization rather than attempting multiple intricate migrations in a single event. Key strategies such as microservices, API-driven design, and cross-region resilience have proven beneficial for many customers.
Flexibility During the ECA
Establishing interactive processes to manage workstreams during the ECA party is crucial. Often, cultural resistance within organizations can hinder the implementation of reversible decisions. Overcoming these challenges may require creativity and persistence to keep tasks progressing.
Your teams should be empowered to make quick decisions and escalate challenges as they arise. Utilize stand-ups and feedback systems to identify impediments and address blockers swiftly. If a team struggles, adapt your strategies, resources, and leadership style to facilitate progress. For Delta’s ECA, we saw a total of 18 items resolved during the three-day event. Other airlines have reported as many as 50 items unblocked during their ECAs.
Migration ECA vs. Modernization ECA
A migration ECA is typically utilized when clients have encountered difficulties moving their existing applications to the AWS Cloud. These ECAs establish migration patterns for several applications and leverage automation to streamline the path to production. While clients may employ various strategies, from rewrites to migrations, the ECA’s focus is on acceleration.
Modernization and migration strategies are both supported, but the emphasis lies in eliminating barriers to production. The objective of a migration ECA is not to rewrite applications but to transition them to the cloud intact or utilizing containerization strategies.
When the existing functionality of an application does not meet business needs, a modernization ECA is warranted. This type of ECA can be executed in partnership with an approved AWS Partner, especially if scaling is a priority.
In Delta’s case, it was a partner-led modernization with three distinct workstreams: Architecture, Development, and Testing. The aim was to enhance the velocity of multiple workstreams and foster team momentum through collaboration.
Clearly defined goals for each workstream, aligned with business outcomes, are essential. The Delta team identified three primary goals and one “stretch” goal for the ECA. Each workstream comprised small teams (3-5 participants including clients).
Depending on the requirements for your modernization ECA, some roles and responsibilities should be established upfront. This includes appointing an overall ECA host, typically an AWS Customer Solutions Manager or a lead Partner Delivery Manager. These roles collaborate closely with the client’s lead to manage the Command Center during the event. Additionally, workstream leads should be designated, including an architect, development lead, and testing lead from both the client and partner.
Escalation plays a vital role in the success of an ECA, especially in command-and-control sectors like airlines. The Command Center drives urgency and encourages clients, who may typically rely on dashboards, to address issues promptly—ensuring the team can respond quickly. Attention must be paid to signals regarding application dependencies, which may involve legacy code and APIs.
Addressing blockers or risks in real time during the ECA is an agile method that can be exemplified by workstream leads and documented by the Command Center owner. A running risk list will emerge as an outcome of the ECA. Regular checkpoints are critical for publicly addressing blockers across the client, partner, and AWS OneTeam, and for soliciting assistance.
Thorough documentation before, during, and after the event is crucial to meeting the ECA’s scope within the desired timeframe, generally 2-4 business days. The agenda and participant list should ideally be finalized two weeks before the execution date. The Command Center will support workstream leads in capturing blockers, risks, and issues during the ECA. The workstream leads will track progress toward goals, develop the backlog, and document key takeaways in real time.
The Delta ECA generated 22 lessons learned that were reviewed and documented collaboratively by the client, partner, and AWS.
Scaling Partnerships Effectively
Clients often engage partners to supplement their existing workforce or to enhance staff skills. Enabling partners to drive growth and accelerate ECAs allows AWS Partners to share knowledge following the initial training session. Partners take on an active, hands-on role during the ECA rather than merely observing.
Partners also help eliminate roadblocks during the ECA by escalating risks to their management during daily checkpoints. They participate in a Lessons Learned session with AWS shortly after the ECA, ideally within 3-5 days. If the same partner will lead a subsequent ECA, an internal transition to onboard their new ECA team will be established.
Developing Training Initiatives to Address Skill Gaps
By focusing on continuous learning and development, organizations can foster a more positive employee experience, which has been shown to be essential for success. According to research from SHRM, employees who experience a positive work environment are 68% less likely to leave their jobs. Additionally, for more insights on work styles, check out this blog post.
To explore the hiring process at AWS, visit this excellent resource.
Leave a Reply