Sprint Planning and At-Risk Sweeps
Start sprints, review planning sessions across projects, and get a daily sweep that flags at-risk work with a stated reason.
These images are illustrations of the concept, not screenshots of the actual product.
Overview
Sprint Planning and At-Risk Sweeps is the part of the PlanMagnet concept that covers the life of a sprint once the backlog is ready: starting a sprint, seeing every planning session across projects in one list, and keeping watch over committed work while the sprint runs. It sits in the Work & Sprints area next to the task board and is reached from the Sprints and Projects entries in the main sidebar.
The problem it addresses is familiar to most delivery teams. A sprint rarely fails on its last day; it drifts. An item waits on a blocker nobody escalated, a ticket stops moving while its owner juggles other work, or one person quietly carries more points than their capacity allows. By the time a burndown makes the slip obvious, there are few options left for recovering it.
Across the three illustrations, the design moves from structure to vigilance. The Start Sprint page appears mid-load inside the standard PlanMagnet shell, and the Planning Sessions page under Projects counts sprints across all projects and shows its empty state before any exist. The third illustration is the at-risk view for a sprint in progress: a daily sweep, labeled AI-assisted, that lists flagged items with a severity marker and a plain-language reason for each, summary tiles for flagged items, newly blocked work and burn-rate, and controls to run the sweep on demand or leave it running autonomously.
The design is deliberately cautious about what automation decides. A notice at the top of the sweep states that flags are suggestions with a stated reason and that raising a formal risk requires confirmation. Each flag links to its item and to any blocking item, so a scrum master or engineering lead can open it, judge it and then choose whether to raise it. The same sprint data is meant to feed the dashboard forecasts and the scheduled velocity reports elsewhere in the product.
What this concept shows
- A Start Sprint page reached from the Sprints entry in the main sidebar, inside the shared workspace and project context
- A Planning Sessions list that counts sprints across all projects, with a clear empty state when none exist
- A daily at-risk sweep, labeled AI-assisted, showing when it last ran, with a sprint selector that shows the current day of the sprint
- Summary tiles for flagged items, newly blocked items and how many points the sprint's burn-rate is behind
- Flagged items with a severity marker and a written reason, such as a long-running blocker, a stalled status or an over-committed assignee
- An Autonomous sweep toggle alongside a Run now button for an on-demand check
- Per-item actions to open the item, jump to its blocking item and raise the flag as a formal risk after confirmation
How it works
- Open Sprints from the main sidebar to start a sprint for the project chosen in the workspace and project context switcher.
- Go to Projects, then Planning, to review planning sessions and the number of sprints across all projects.
- While the sprint runs, open its risk sweep and read the flagged items, newly blocked and burn-rate tiles.
- Read the stated reason on each flagged item, then open the item or its blocker to judge whether the flag holds.
- Raise a confirmed flag as a risk, or select Run now to re-check the sprint after the team has acted.
Who it's for
- Scrum masters and delivery leads
- Engineering managers
- Product owners
- Team leads in cross-functional squads
Illustrations
3 illustrations of this concept. Select one to view it full size.
Start Sprint Page
This illustration shows where sprint work begins in the PlanMagnet concept. The Sprints entry is highlighted in the left sidebar, which groups the product's own modules (Dashboard, Products, Projects, Tasks, Sprints, Reports, Team, Workspace and Analytics) above a separate list of shared workspace modules such as calendar, files and groups. A breadcrumb trail runs from Home through Sprints to the Start Sprint page. The content area is shown in a loading state, with a single progress spinner where the sprint setup will appear, so the view demonstrates the page's place in the navigation and its loading behavior rather than the setup form itself. The top bar carries the workspace and project context switcher, a product switcher, a language selector, search, help, notifications and a theme toggle, and a footer lists product, resource and legal links.
Planning Sessions Across Projects
The Planning Sessions page sits under Projects in the sidebar, alongside All Projects, Active and Milestones, with the Planning sub-entry highlighted. The heading reads Planning Sessions, and a line beneath it counts sprints across all projects, which in this illustration is zero. Below, a centered message explains that no planning sessions were found: the empty state a new workspace would see before its first sprint is planned. The design treats planning as a portfolio-wide view rather than a page buried inside each project, so a delivery lead can see every sprint being planned in one place. The breadcrumb traces the path from Home through Projects to the Planning page, and the same top bar, context switcher and footer frame the page as elsewhere in the product.
AI-Assisted At-Risk Work Sweep
This illustration shows the risk sweep for a sprint in progress. Its breadcrumb runs from Sprints through the sprint to the sweep, and a selector at the top right names the sprint and how many days into it the team is. The At-risk work heading carries an AI-assisted badge and notes a daily sweep with the time of its last run, beside an Autonomous sweep toggle and a Run now button. An amber notice states that flags are suggestions with a stated reason and that raising a risk requires confirmation. Three tiles summarize flagged items, newly blocked items and how many points the burn-rate is behind. Each flagged row has a red or amber marker and a reason: a long-unresolved blocker, no status change while the assignee juggles other work, a burn-rate that misses the sprint end, a commitment above capacity, or a new blocker. The first row adds a chip for its blocking item, an Open item link and a Raise as Risk button.
Topics
- sprint planning tool
- start a sprint
- sprint risk detection
- at-risk work items
- blocked tasks in a sprint
- sprint burn-rate
- over-committed team members
- AI sprint health check
- agile sprint management
- sprint planning sessions
Related concepts
Task Board and AI Work Breakdown
The board where work moves, the form that adds to it, and an assisted breakdown that turns a paragraph of intent into reviewable work items.
3 illustrations
Dashboard, Delivery Analytics and Forecasting
One place to open the day: a delivery dashboard, project health metrics, and an AI-assisted forecast of when work lands.
3 illustrations
Scheduled Reports
Configure recurring delivery reports by type, project and schedule, and see how many are scheduled or have run today.
2 illustrations
Project Portfolio and Milestones
A portfolio view that runs from every project, to the ones in flight, to the milestones they are judged by — plus a form to start the next.
4 illustrations