Preparation - AWS Prescriptive Guidance


The preparation stage of the migration consists of these steps:

  1. Set up two 2-pizza teams as scrum teams. These teams are made up of internal resources from workstreams that are defined in the readiness and planning phase. Group the teams based on the underlying functional/technical roles. Together these teams are responsible for driving adoption, enabling initial migrations, and preparing the organization for running enterprise-scale migrations.

    • 2-Pizza Team 1 structure and resources – advisory, business case, program governance, people skills, and center of excellence (CoE).

    • 2-Pizza Team 2 structure and resources – app discovery/migrations, landing zone, security, and operations integration.

  2. Kick off a planning meeting with both scrum teams to review the results from the migration readiness assessment.

  3. Identify 10 to 30 applications to migrate from on premises to AWS in Wave 1.

  4. Set up a backlog. Prioritize the use of "pre-baked" epics for all workstreams from existing migration patterns. Here are a few examples:

  5. Assign a scrum leader and a product owner, who are responsible for managing the backlog.

  6. Set up eight two-week sprints for migrating applications.

  7. Build a migration plan with resources, a backlog (epics, user stories), a risk/mitigation log, and a roles and responsibilities matrix (for example, a RACI matrix). You can use this plan to manage the risks that occur during the project, and to identify ownership for each resource involved.