Driftless is 35 purpose-built tools grounded in the 2020 Scrum Guide and a 10-dimension maturity framework. Here's how it actually works — and why that matters.
Driftless lives as a Chrome extension sidebar next to your board. Nothing to set up. No API credentials to configure on day one. It reads the page the same way you do — by looking at what's on screen.
The content script extracts structured ticket data: IDs, titles, assignees, story points, status columns, blockers, labels, and carry-over signals. No data is stored on our servers. The read happens in your browser.
This is where Driftless differs from a general AI tool. The data is not sent to a generic "analyze this sprint" prompt. It is routed to one of 35 specific tools — each one written to look for a particular class of signal. Board Maturity Scan looks at 10 coaching dimensions. Team Load Analysis looks at assignee distribution. Sprint Risk looks at carry-overs and blockers older than 5 days. Each prompt is grounded in a specific Scrum Guide accountability or Agile Manifesto principle.
Every output follows the same structure: what to do first, why it matters, how to have the conversation, what the evidence is, and which Scrum Guide section it connects to. The framework comes last — because numbers are evidence, not the product. The conversation is the product.
Every tool response can be saved to the Sprint Journal — a scoped memory that travels with your team profile. Over multiple sprints, patterns become visible. The same blocker type. The same person quietly struggling. The Journal gives Driftless context that makes each subsequent analysis more relevant.
The Board Maturity Scan assesses your sprint across 10 dimensions, each scored L0–L4. The dimensions were built from real sprint patterns and mapped back to specific Scrum Guide accountabilities — not invented from theory.
AI coaching tools that make things up are worse than no coaching at all. Driftless grounds every tool output in one of two authoritative sources.
Every tool in Driftless maps to a specific Scrum Guide accountability — Scrum Master, Product Owner, or Developers. When Driftless flags a blocker pattern, it connects it to the SM's accountability to remove impediments. When it surfaces a sprint goal misalignment, it references the Scrum Team's shared commitment. The framework is visible, not hidden.
The 12 principles and 4 values of the Agile Manifesto sit underneath every coaching recommendation. "Individuals and interactions over processes and tools" is not a tagline in Driftless — it is the reason the output always leads with a person to talk to, not a metric to fix.
The extension organizes its tools into two categories that match how coaching actually works: clearing the path so the team can move, and being present in the room when it counts.
Driftless reads your board inside your browser. No ticket data, team names, or sprint content is stored on Driftless servers. Board reads happen via your browser's content script and are sent directly to the Anthropic API for analysis. Sprint Journal entries are stored locally in your browser or optionally synced to your own account — never aggregated or analyzed across users.
If your organization has data residency requirements, reach out before starting a trial and we will walk through the architecture with you.
We're in beta and happy to walk through the architecture, the data handling, or anything else with you before you commit to a trial.
Join the Beta → Get in Touch