AfterAgile™
Lens
Get the PDF

Bringing an Existing Product Across

The cutover, one area at a time

Most teams don't start fresh. They have a live product, a backlog and customers who depend on it. Don't flip a switch – run both ways side by side, and move the product over one area at a time.

The Cutover, at a Glance · an illustrative timeline

  1. Week 0Get ready2 3 4
  2. Weeks 1–2Side by side1
  3. Weeks 3–6Area by area5
  4. Week 7+One way7

Sprint team finishes its work

AfterAgile™ grows each week

  • Billing
  • Onboarding
  • Account
  • Reporting

6 Customers covered the whole way

  • Run the old way
  • Run the AfterAgile™ way
  • Area switches over

The weeks are illustrative. A small product might move in a month. A large portfolio moves one product line at a time.

The Cutover, Step by Step

  1. 1

    Weeks 1–2

    Side by Side

    Run both ways at once, never a big switch. The sprint team finishes the work it already committed to. New Intents run the AfterAgile™ way, starting with low-risk areas behind feature flags.

  2. 2

    Week 0 · CX

    Tickets to Concerns

    Don't migrate the backlog. CX reads every open item for the customer concern behind it. Most tickets close or merge. What's left joins the live queue of customer concerns.

  3. 3

    Week 0 · AI

    AI Reads What Exists

    The platform learns the product before the first Intent. AI reads the existing code and documents to generate the first context files and decision records. UX's current brand assets seed the design system AI project. Existing research becomes personas, approved by CX.

  4. 4

    Week 0 · Product

    Baselines

    Measure today before changing anything. Capture current KPIs for every area, so KPI Learnings has something to compare against.

  5. 5

    Weeks 3–6

    Area by Area

    Hand over one product area at a time. An ownership map shows what has moved. An area switches when a Definer owns it, and its tests and gates are in place.

  6. 6

    The whole way

    Customers Covered

    Customers shouldn't notice the switch. Honor commitments already made, keep contracts and support on track, and keep release notes going out.

  7. 7

    Week 7+

    Done, or Pause

    Know when it's finished, and when to slow down. When the last area has moved, retire the sprint ceremonies. If something isn't ready, pause that area – the flags stay on, and it can roll back.

Ready to move an area

  • A Definer owns it
  • Context files exist for its code
  • Tests and gates run on every change
  • Its baseline KPIs are captured

Slow down if

  • Customers notice the switch
  • Rollback is being used often
  • The old backlog keeps coming back
  • Intent Review can't keep up with both ways

A Whole Portfolio?

Move one product line at a time, using this chapter for each. For larger transitions, the AfterAgile™ Transition Playbook is coming – or call us to plan it with you.