AfterAgile™
Lens
Get the PDF

The Playbook

AfterAgile™

Product Engineering Teams Building with AI Driven by CX

The model at a glance

Six Steps, One Continuous Cycle

Every cycle starts with the customer need and ends with what customers actually did. What CX learns at Thursday's Collab becomes Monday's Intent, and Friday stays open.

Every session in AfterAgile™ is a remote meeting, captured from start to finish. AI turns each one into decisions, intentions and actions, with a name on every action, so no one takes notes. It's true of every session in this playbook, so it isn't repeated.

Why this playbook exists

Should We Build It?

AI changed the pace of building. A feature scoped for a two-week sprint can now ship in an afternoon. What didn't change is how long it takes to decide what's worth building, and to know whether it worked.

Agile and Scrum were designed for a world where building was slow and expensive. Their structure lived in time – sprints, standups and ceremonies on a calendar. Much of that friction was also where quality came from. It was where a designer caught the broken flow, QA found the edge case, and someone asked, "Should we build this at all?"

AfterAgile™ moves that structure into the system instead – a written Intent, a small team of Definers, sessions that document themselves, and a Dashboard the core team can see. Each Definer sets what "right" means for their part, and tests against it, no matter how fast anyone moves.

Customer-centric

CX

Gets to the bottom of the customer need, and identifies the most pressing customer challenge each week.

The translator

Product

Turns the customer need into a business case, and defends it.

The experience

UX

Defines the brand, the UI and the workflow, and how it feels to use.

Machines own execution. Humans own intent, care, and aesthetic.
  1. 1. Why This Playbook Exists
  2. 2. Six Steps, One Continuous Cycle
  3. 3. Definitions
  4. 4. One Week, One Full Cycle

Inside this playbook

Contents

  1. Six Steps, One Continuous CycleThe whole model on one page
  2. DefinitionsRoles, Ceremonies, Actions and Tools
  1. One Week, One Full CycleThe six steps, around the week
  2. At a GlanceEvery session, who's in the room, and what it generates
  3. Monday – Set Intent and Intent ReviewClean up the AI drafts, then defend them until 80% consensus
  4. Tuesday – Coding Day + TestingCoding Day step by step, Engineering and testing
  5. Wednesday – ShipFinal Review, the rollback plan, and shipping safely
  6. Thursday AM – KPI LearningsSolo, no meeting – each Definer reads their layer
  7. KPIs in LayersHow Thursday reads slow KPIs
  8. A Scenario – Paying a Bill OnlineThe layers, in a real example
  9. Thursday PM – The CollabThe hours, the agenda and the AI moderator
  10. Every Artifact, Generated or LinkedWhat AI writes, what the team links, who owns each
  11. Ground Rules for the WeekSeven rules the whole team keeps
  1. Whoever Defines It, Tests ItThe Definers, and the gates to ship
  2. Three Ways to Understand the CustomerWhere CX, Product and UX overlap
  1. Engineering GuardrailsThe rules AI builds inside, and the customer prompt
  2. AI Safety and ReproducibilitySafe, traceable, repeatable AI work
  3. When AI Gets It WrongCorrect the source, not just the output
  4. Crisis ModeWhen production breaks
  5. The IDE HandbookThe stack, and how the team works in it
  1. The DashboardThe week, and live customer activity
  2. Hear What's Working, Early"Was this better?" and the First Circle
  1. Bringing an Existing Product AcrossThe cutover, one area at a time
  2. A One-Week PilotOne team, one week
  3. Need an Executive Sponsor?Who to pitch, talking points and the pushback
  4. The Business Case in NumbersSalaries, AI licenses and the savings
  5. FAQThe common questions, answered
  1. The IntentDrafted by AI, cleaned up by CX and Product
  2. The Collab BriefGenerated Thursday afternoon, vetted by CX
  3. The AI Moderator ScriptWhat AI asks Thursday afternoon, with its sources
  4. A Roadmap for SuccessWhat to have in place before the first Monday
  5. A Week, Role by RoleAn example calendar for each of the five roles