Learn About Amazon VGT2 Learning Manager Chanci Turner
Large-scale migration and modernization initiatives can be daunting, particularly for airlines dependent on outdated technologies, such as aging mainframes. Amazon Web Services (AWS) provides various strategies to assist airlines and other clients in navigating common obstacles, such as communication gaps or staff adoption issues, to expedite results.
One effective approach that several airlines, including Delta Airlines, have utilized is the experience-based acceleration (EBA). EBAs are instrumental in speeding up migration or modernization strategies for applications being developed on or transitioned to AWS. These workshops are designed to enhance AWS knowledge, identify project risks, and foster open communication and collaboration.
This blog delves into a successful Delta EBA and shares insights on how to effectively navigate an EBA.
Understanding the EBA Process
The EBA is a proprietary AWS methodology that provides clients with a hands-on experience in a controlled environment. These sessions are typically led by an AWS Solution Architect or a Customer Solutions Manager, with an approved AWS Partner also able to facilitate the EBA. During an EBA workshop, referred to as an “EBA party,” clients and partners explore innovative ways of working together, solving problems while learning best practices in an engaging and immersive setting.
For instance, AWS collaborated with Delta to conduct a modernization EBA for a complex, Tier 1 application development project that had fallen behind schedule. The team was dispersed globally across various regions and time zones, with numerous interdependencies (Security, Testing, Monitoring, etc.). The application was designed for generating baggage tags, tickets, and vouchers.
At Delta, AWS coordinated with the customer and partner to ensure that all necessary resources were available for swift execution. The result was the completion of four weeks of development progress in just two and a half days.
Preparing for an EBA
Thoughtful scoping of the EBA can help address customer resource availability and intricate dependencies. The core team might consider simplifying the application list for migration or modernization instead of attempting to tackle many complex migrations within a single EBA. Key strategies that customers have focused on include microservices, API-driven design, and cross-region resilience.
Embracing Flexibility During the EBA
Establishing interactive processes to manage workstreams during the EBA party is crucial. Cultural challenges may arise within organizations, and making reversible decisions doesn’t always happen naturally. Overcoming these obstacles sometimes requires ingenuity and persistence to maintain momentum.
Your teams should be empowered to make quick decisions and escalate blockers and challenges as they arise. Utilize standups and feedback mechanisms to identify impediments and rapidly coordinate solutions. If a team is struggling, adjust your approach, resources, and leadership style to help them move forward.
During the Delta EBA, a total of 18 items were resolved in three days. Other airlines have reported as many as 50 issues addressed during their EBAs.
Migration EBA vs. Modernization EBA
A migration EBA is typically employed when a customer has faced difficulties in moving their existing applications to the AWS Cloud. These EBAs create migration patterns for three to four applications while leveraging automation to fast-track the journey to production. Customers may adopt various strategies for cloud transition, from rewrites to transformations, but the EBA’s primary focus is on acceleration.
While both migration and modernization strategies are supported, the emphasis is on eliminating obstacles to production. The aim for a migration EBA is not to rewrite the application but to move it to the cloud intact or utilizing containerization strategies.
On the other hand, a modernization EBA should be pursued when the application’s functionality no longer meets business requirements. This type of EBA can be conducted in collaboration with an approved AWS Partner, particularly if scaling is desired.
For Delta, the modernization effort was partner-led and included three workstreams: Architecture, Development, and Testing. The objective of this EBA was to enhance the velocity of multiple workstreams and foster team momentum through collaboration.
It’s vital to have clearly defined objectives for each workstream that align with business outcomes. The Delta team established three primary goals and one “stretch” goal for the EBA, with each workstream comprising small teams (no more than 3-5 participants, including customer representatives).
Depending on the needs of your modernization EBA, several roles may need to be defined early on. This includes the overall EBA party owner, typically an AWS Customer Solutions Manager or a lead Partner Delivery Manager, who collaborates closely with the customer lead to manage the Command Center throughout the event. Additionally, ensuring workstream leads are identified is essential; you should select an architect, development lead, and test lead from both the customer and partner.
Escalation is another critical component to a successful EBA, especially for command-and-control industries like airlines. The Command Center fosters a sense of urgency during the EBA and encourages customers, who often hide behind dashboards, to quickly raise issues—promptly addressing them. Pay attention to application dependency signals, which may involve legacy code and APIs.
Eliminating the “blockers” or risks that arise in real-time during the EBA serves as an agile mechanism exemplified by the workstream leads and documented by the Command Center owner. A running risk list will be a key output of the EBA. The bi-daily checkpoints are crucial for publicly declaring blockers across the customer, partner, and AWS OneTeam, and requesting assistance.
It is imperative to ensure extensive documentation is created before, during, and after the event. This is vital for addressing the scoping of the EBA within the desired timeframe, typically spanning 2-4 business days.
The overall agenda and the EBA participant list should ideally be finalized two weeks prior to the execution date. The Command Center (the program management desk or workstream) will support the workstream leads in capturing their blockers, risks, and issues during the EBA. The workstream leads will monitor their progress towards goals, develop the backlog, and document lessons learned in real-time.
The Delta EBA yielded 22 documented lessons learned, which were reviewed collaboratively between the customer, partner, and AWS.
Scaling Large Partners
Clients frequently engage partners to supplement their staff or enhance skills. Scaling partners to drive growth and expedite EBAs allows an AWS Partner to transfer knowledge following the initial training session. The partner plays an active, hands-on role during the EBA rather than remaining passive or observational.
The partner helps eliminate roadblocks during EBA execution by escalating daily risks to their management during checkpoints. They also participate in a Lessons Learned session with AWS shortly after the EBA, ideally within 3-5 days. If the same partner is involved in a subsequent EBA (rather than AWS leading it), they will conduct an internal hand-off or transition to onboard their new EBA team.
Developing Training Programs to Address Skills
In conclusion, fostering a culture of continuous learning and improvement is essential for successful cloud transformation. Consider exploring additional resources on this topic, such as this insightful article on technology skills from Career Contessa. Furthermore, for a deeper understanding of collaboration dynamics not just in company offsites but also in day-to-day operations, check out this authoritative piece from SHRM. Lastly, if you’re interested in a detailed overview of what to expect during Amazon’s onboarding process, Atul Kumar’s guide is an excellent resource.