Driftless.
Install Driftless
How it works

This isn't a chatbot with a Scrum prompt.

Seven things happen in a run. Here they are, on a real board.

A run, step by step

  1. A Jira sprint board, Mobile Team Sprint 11

    Open a board

    Any Jira Cloud or Rally board in Chrome. Click the Driftless icon. Sign in once with an emailed code.

  2. The Board tab: sprint status, flow signal, blocked work, scope movement

    Driftless reads the visible work

    Tickets, columns, assignees, points, the Sprint Goal. It shows you what it found. Reading costs nothing.

  3. The Tools tab, grouped: Before the sprint, During the sprint, With the team

    Choose a tool

    30+ tools in five groups, each written for one question. See every tool.

  4. Today's coaching focus: a blocked ticket with another depending on it

    It names the board signals

    The ticket that hasn't moved. The person carrying too much. Specific ids and names, not generalities.

  5. Observed and Why this matters, labeled separately, with the interpretation marked as one possible reading

    Evidence is kept apart from interpretation

    What the board states is labeled observed. What Driftless infers is labeled as such and phrased as a question.

  6. The Human Play: the move, then Try saying with the exact words

    It ends with The Human Play

    The move, the words to say, and the Scrum Guide line it rests on. Driftless suggests. The Scrum Master decides.

  7. The Journal tab with a saved People Pattern Coaching entry

    Save it to the Journal

    Every run is filed to the team's Journal. Patterns show across sprints, and each new run gets that context.

One run. One tool click or one follow-up. Reading, switching teams, and Demo Mode use none. A failed run isn't charged. Every new account starts with 20 free runs.
The maturity framework

A baseline before you coach anything.

Board Maturity Scan scores eight dimensions of board transparency and discipline and places the team on a five-level scale, L1 to L5.

It's a coaching baseline, not a grade. Runs in your browser. Uses no run.

What the dimensions look at

  • Sprint structure: name, written goal, real columns
  • Blocker visibility and age
  • Load distribution across assignees
  • Work in progress per person
  • Estimation and story clarity
  • Carry-over from previous sprints
  • Backlog readiness and delivery rhythm, from Journal history
Why it's grounded this way

Every output traces back to a source.

  • The Scrum Guide, cited in every output
  • The Agile Manifesto underneath it
  • Your board, your profile, your Journal
Your data

What happens to the board content.

Sent to Driftless's server and to Anthropic for that run. Not retained afterward. Never used to train models. Full policy.

Try it without a board

Demo Mode opens a mock Jira board with every output ready to read. No runs, nothing sent.

Install Driftless Watch the reel