Getting Started

AgileNotes.AI turns Sprint chaos into clear memory, coaching insights, and leadership-ready summaries.

It syncs your Sprint data, tracks flow metrics like WIP and cycle time, and lets you capture the decisions, blockers, and risks from any conversation — an event, a hallway, Slack, or a voice note from your phone on the way out of the room. The AI-powered coaching insights and polished reports follow automatically. It isn’t a wiki replacement; it’s the Sprint Intelligence Layer that sits between what actually happened and what everyone half-remembers a week later.

• Syncs with your APM tool — Jira, Azure DevOps, Agility, or Rally — or enter your Sprint data by hand.
• Capture from anywhere — events, hallways, Slack, or voice notes on your phone.
• Built for facilitation, coaching, and data-driven retrospectives.

What “AI-Native” means here

The .AI in the name isn’t decoration. AgileNotes is AI-native: the AI doesn’t sit off to the side as a chatbot you have to prompt — it’s woven through the product, and three things make it trustworthy.

• Grounded in your data, not made up. Every AI summary, insight, and coaching lens is built from your real tickets and notes. Where an insight is tied to specific work, a Why? button appears — open it to reveal a “Grounded in:” strip of the tickets and notes behind that card. If it can’t ground a claim in your data, it doesn’t make the claim.
• It builds team memory. Behind the scenes AgileNotes keeps a memory of each team — baselines, working agreements, open risks, and recurring patterns — so its observations carry context from sprint to sprint instead of starting cold every time.
• It learns from you. Wherever the app shows AI-generated text, you’ll see 👍 / 👎 buttons. A thumbs-up tells it to keep that framing; a thumbs-down tells it not to repeat it. Your feedback feeds straight into the next generation, so the AI gets more useful to your team the more you use it. You can also edit any AI text directly (the pencil icon) and your wording sticks.
• It’s proactive. Instead of waiting to be asked, it raises signals — a risk that’s gone stale, a dependency that’s overdue, a pattern that’s getting worse — at the top of the Insights view.

You’ll meet each of these in context as we go: the 👍 / 👎 feedback and Why? evidence show up on the Dashboard standup card and across the Insights view.

The rest of this guide walks through every view using the built-in Demo organization, so each screenshot is the real app on real-shaped data — a working preview before you bring your own teams in. The Demo has three teams you’ll see throughout:

• Dragons and Tigers — Scrum / SAFe teams (sprints, velocity, predictability).
• Juggernauts — a Kanban team (flow windows, cycle time, aging WIP).

Following along live? Open app.agilenotes.ai in another tab. The Demo account is read-only — you can click into every view, but changes won’t be saved, so explore freely.

The layout

Two controls frame every screen:

• The header (top) holds the Team, PI (Program Increment), and Sprint / Iteration selectors. Switching any of them re-scopes the whole app at once.
• The bottom navigation switches between views, in order: Home, WIP, Capacity, Notes, Capture, Insights, Stats, Charts, and Summary. (When you’re viewing an ART, a Program Board entry replaces WIP.)

The help panel

Press ? anywhere in the app to slide open a context-aware help panel for the view you’re on. This manual is the long-form companion to that panel — same wording, more room to breathe.

Keyboard shortcuts

On Mac, Quick Capture uses ⌃Q (Control), not ⌘Q — macOS reserves ⌘Q to quit the browser.

Next, let’s look at how teams, sprints, and PIs fit together — the scope that everything else hangs off of.