How It Fits Your Sprint

Your tracking tool records what happened to each ticket. AgileNotes.AI sits alongside the Scrum events and records why — the blockers, decisions, risks and actions raised in the room, the daily state of the work, and your team's own history.

Every Scrum event has a place to put something in, and something the tool hands back. This page walks one Sprint from Planning to Retrospective and shows both sides at each stop. If your team runs Kanban, the same loop applies with flow vocabulary — see the iteration version at the end.

One Sprint, left to right. Backlog Refinement is dashed because it happens during the Sprint rather than at a fixed point. Closing the Sprint leads straight into the next Planning.

For each Scrum event

Scrum event	You do this in AgileNotes.AI	It gives you back
Sprint Planning day 1	Press Start Sprint, write the Sprint Goal, mark PTO and holidays on the Capacity calendar, and capture the planning conversation as notes: decisions, risks, dependencies.	Forecasted points from your tickets or synced tool, the team’s available days, and a confidence dial that opens at your real track record rather than a guess.
Daily Scrum every day	Record each ticket’s status for the day on the WIP grid and capture what was raised: blockers, risks, actions, open questions.	Dashboard tiles, WIP age and cycle time, the live Sprint Risk Radar, and a Daily Standup card you can edit and post to Slack.
Backlog Refinement as needed	Tag notes to the Refinement event: what was split, sized, clarified or dropped.	Unplanned-work and scope-change signals in Insights, with the reasoning kept for later.
Sprint Review last day	Log accomplishments, decisions and stakeholder questions, and record whether the Sprint Goal was met.	Done vs Forecasted, predictability and velocity, the Sprint Overview narrative, and the Sprint or Stakeholder Report as a PDF or share link.
Sprint Retrospective last day	Open the Retro Prep brief and the coaching lenses, capture observations and actions, close out risks with an outcome, then Close Sprint.	Rule-based pattern insights, trend charts, action items that carry their age across Sprints, and open tickets rolled into the next Sprint.

Between Sprints

Close the current Sprint before you start the next one. Start stays unavailable until the previous Sprint is closed, and recording only happens inside a started Sprint, so your history stays clean and every metric lines up with a real timebox. Closing rolls any still-open tickets into the next Sprint for you. See starting and closing a sprint.

Coaching happens between the events

The Charts, Insights and AI analysis exist for the conversations you have outside any ceremony — with the team, one person, or the Product Owner.

Ask in your own words. Ask AgileNotes what happened and why: what did we accomplish this Sprint, why did predictability drop, what should I raise at the PO Sync. The answer is drawn only from your team’s notes, tickets and memory, scoped to the Sprint or PI you are looking at, and every claim shows where it came from.
Put the trend on the screen. Open Charts or Insights together and point at the Sprint where a habit started — WIP against cycle time, predictability over the last six Sprints, when blockers tend to surface, tickets that keep rolling over. The team sees the consequence for itself instead of hearing an opinion.

Always running

Connect your tracking tool — Jira, Azure DevOps, Rally or Agility — and, if you use them, Microsoft Teams or Zoom meeting recaps. Tickets and daily state stay in sync; meeting recaps land as Summary notes in the right Sprint; and team memory grounds every AI surface and cites its sources.

If your team runs Kanban

Kanban teams follow the same loop with flow-window iterations instead of Sprints, and AgileNotes.AI speaks flow vocabulary there: throughput, WIP, cycle time, lead time and SLE. See Scrum vs Kanban for how the two are set up.

Moment	You do this in AgileNotes.AI	It gives you back
Start of an iteration	Press Start Iteration and capture the replenishment conversation as notes. Work that is still in progress flows in on its own — nothing to roll over.	WIP by column, aging work items, and where the flow is stalling.
Daily	Record each item’s status for the day and capture blockers, risks, actions and questions.	Cycle time and lead time as they develop, items approaching or exceeding the SLE, and the Daily Standup card.
Review and retrospective	Log accomplishments, decisions and observations; close out risks; press Close Iteration.	Throughput, flow efficiency, the iteration report, the Retro Prep brief and the coaching lenses.

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