Start from the Scrum project template in Manager: refine the backlog, plan sprints to capacity, review the increment and improve with every retrospective, while an agent keeps the books.
Stories are ordered by value, sliced small, given acceptance criteria and estimated in points before planning starts.
Each sprint takes on as many points as the team finished in the last one. No guessing.
Every retrospective ends in tasks with an owner, so improvements land in the next sprint.
Scrum organizes complex work into sprints of one month or less. The Product Owner orders the backlog, the Scrum Master helps the team use Scrum well, and the Developers deliver a usable increment every sprint.
Each sprint starts with planning toward a sprint goal, checks progress in a 15-minute Daily Scrum, and ends with a review and a retrospective. The template adds story points and velocity, common practice beyond the Scrum Guide.
The template builds Scrum from the backlog and one milestone per sprint. Here is where each part lives.
| Scrum | In Manager |
|---|---|
| Product Backlog | The Backlog view, ordered by drag and drop or by the refine-backlog skill. |
| Sprint | A milestone with the sprint's start and end date. Its committed stories are its members. |
| Sprint Goal | One sentence in the sprint milestone's description. |
| Daily Scrum | Scope the board to the sprint; blocked cards show a red badge. |
| Increment | Stories in Done that meet their acceptance criteria, judged by the sprint-review skill. |
| Story Points and Velocity | Points field, Fibonacci by default. Velocity is recorded on the sprint milestone, whose page draws the burndown. |
| Definition of Done | Keep it on a wiki page; the done guard can require its checkboxes. |
Connect your AI agent over MCP and let it create the project from the Scrum template.
Say to your agentManager: Create a new project from the Scrum template and interview me about the product.
Capture the work as stories under epics. The agent orders and splits them, adds acceptance criteria and estimates points.
Say to your agentManager: Run the refine-backlog skill on the stories at the top of the backlog.
Give a goal and your capacity. The agent opens the sprint milestone and commits the top ready stories up to that many points.
Say to your agentManager: Let's plan the next sprint with the sprint-plan skill, and ask me for the goal and our capacity.
Stories and tasks move across the board to Done. Spikes time-box the unknowns, and bugs get a severity.
Say to your agentManager: Which stories in the current sprint are blocked or not started yet?
Only finished stories that meet their criteria count toward velocity; the rest return to the backlog. The retro files improvements as tasks with owners.
Say to your agentManager: Run the sprint-review skill, then the sprint-retro skill.
A project created from the Scrum template starts with these work item types and statuses. You can adapt all of them to your team later.
A large body of work that breaks down into user stories.
A feature or requirement from the user's perspective.
A concrete unit of work, finishable in a single session.
A defect or unexpected behavior that needs to be fixed.
These skills come with the template in Manager:
refine-backlogOrders, splits, adds acceptance criteria and estimates stories before planning.
sprint-planOpens the sprint milestone, sets the goal, commits stories to capacity.
sprint-reviewAccepts finished stories, records velocity, closes the sprint and returns unfinished ones to the backlog.
sprint-retroWrites a blameless retrospective and files improvements as owned tasks.
Each story in a sprint keeps the day it joined, so the review tells the original commitment apart from work pulled in later.
Scrum fits fixed sprints toward a goal, Kanban fits continuous work like support. The default Manager template suits agent-driven projects without a fixed cadence.
Unfinished stories leave the sprint when it closes, listed there as removed, and wait in the backlog for the next planning. Stories close with their last task; the review still checks criteria.
Each sprint milestone keeps goal, commitment, progress, velocity and retrospective together, so the team sees itself improve.
Get early access