Agile Latte
Agile Latte
  • Home
  • Framework
  • Resources
  • More
    • Home
    • Framework
    • Resources
  • Home
  • Framework
  • Resources

Sense & Play Overview

How It Works

The problem

"We trained everyone, launched the new ways of working, and a year later teams are back to old habits."

What it is

Sense & Play is an adoption framework for Agile transformations. It combines three ideas: a team change path (the Adoption Path), a game layer that teams design themselves, and a sensing layer that reads how adoption is really going. Sense & Play builds on Agile Latte's Play to Adopt approach.

It works in three stages:

  • Engage: build purpose and pull, so the why lands.
  • Equip: build practice that holds under pressure, so teams can do it on real work.
  • Embed: turn the practice into habit and spread it, so it survives the next reorg or hard quarter.

The Adoption Path

Each stage has two checkpoints. Teams rate them in a six-question pulse each sprint, and the first weak checkpoint is usually the barrier point.

  • Engage, Purpose: "We know why this matters."
  • Engage, Pull: "We want to be part of it."
  • Equip, Practice: "We can do it."
  • Equip, Pressure: "We still do it when delivery gets tight."
  • Embed, Habit: "It's just how we work now."
  • Embed, Spread: "Other teams are picking it up from us."

The Adoption Path is written for teams rather than individuals, and it treats doing the practice under pressure and spreading it to other teams as part of adoption.

The Sense layer and the barrier point

Under all three stages sits the Sense layer. Each sprint, it compares a short team pulse with nine signals from the work itself to find the barrier point: the stage where adoption is stuck. The next game mechanic goes there.

What you'll see

Healthy

  • Teams choose to take part in challenges
  • The pulse and the work tell the same story
  • One clear play per cycle, with a review date
  • Leaders ask about barriers

Struggling

  • Participation is mandated or quietly ignored
  • Teams report confidence the work doesn't show
  • Many initiatives at once, none measured
  • Leaders ask who is behind

Plays that work

Start small: one team, three signals, one mechanic for 30 days. Scale through a 90-day rollout once the first team would recommend it to another.

Watch for

Scoreboard creep: the moment a leader asks to rank teams, the game stops being trusted. Compare each team to its own baseline only.

Example (illustrative)

A team in a Fortune 500 insurance business reports that a new refinement practice is working. Its work signals show late scope changes and vague acceptance criteria. The barrier point is in Equip. The team runs a two-sprint refinement boss battle with a win condition it wrote itself, and the signals move.

Related

The Sense layer · Principles · Engage · The Big Picture

Sense & Play is an Agile Latte framework. For usage and permissions, contact us.

Back to the Big Picture

Copyright © 2026 Agile Latte - All Rights Reserved.

  • Privacy Policy
  • Terms and Conditions

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

Accept