Investigate slow checkout API response times
Profile the checkout endpoint under load and identify the top 3 bottlenecks.
Engineering
Sprint Planning Board
Sprint Planning Board: Kanban Template for Engineering Teams
Planning a sprint shouldn't mean scattered spreadsheets and forgotten commitments. This Sprint Planning Board Kanban Template gives engineering teams a clear five-column workflow, from raw Backlog ideas through Sprint Ready commitments, active In Progress work, In Review checks, and a tracked Done column. Each column ships with realistic sample tasks so you can see exactly how work should flow, and the whole board is designed to work with Kanboard's MCP server so an AI agent can help triage backlog items, move tasks as work completes, and keep your sprint honest without manual busywork.
kanboard.io/templates/sprint-planning
Template preview
Sprint Planning Board
5 columns
Backlog
3Holds all candidate work not yet committed to a sprint, ranked loosely by priority.
Add dark mode toggle to settings page
Design and implement a user-facing dark mode switch persisted in local storage.
Upgrade Postgres to latest minor version
Test compatibility in staging then schedule a production upgrade window.
Sprint Ready
3Tasks the team has committed to for the current sprint, fully scoped with estimates.
Fix flaky checkout integration test
Stabilize the test that intermittently fails due to a race condition in payment mocking.
Implement rate limiting on public API
Add per-IP rate limiting middleware and return 429 responses with retry headers.
Write migration script for user roles table
Create a reversible migration that adds a roles column and backfills existing users.
In Progress
2Tasks actively being worked on right now by an engineer during the sprint.
Build CSV export for admin dashboard
Stream large datasets to CSV without loading the full table into memory.
Refactor authentication middleware
Consolidate three auth checks into a single reusable middleware function.
In Review
2Completed work waiting on code review, QA, or stakeholder sign-off.
Review PR for new webhook retry logic
Verify exponential backoff behavior and confirm test coverage before merge.
QA the updated onboarding email flow
Manually test all onboarding email triggers across three test accounts.
Done
2Work completed and verified during the current sprint, kept for velocity tracking.
Ship password reset rate limiting
Deployed and confirmed limiting works correctly in production.
Deploy new health check endpoint
Added /healthz endpoint and verified monitoring picks it up correctly.
How to run this board
Step 1
Groom the Backlog column weekly, adding new task ideas and archiving anything no longer relevant.
Step 2
During sprint planning, move committed tasks from Backlog into Sprint Ready and add estimates via update_task.
Step 3
As engineers pick up work, move tasks from Sprint Ready into In Progress, keeping only actively worked items there.
Step 4
When implementation is complete, move tasks to In Review for code review or QA sign-off before merging.
Step 5
Once verified, move tasks into Done so the team can track sprint velocity and celebrate what shipped.
AI agent usage
Run it with AI agents
This playbook lets an AI agent connect to the Kanboard MCP server and manage a Sprint Planning Board on your behalf, moving tasks from Backlog through Sprint Ready, In Progress, In Review, and Done. The agent uses get_board and list_tasks to understand current state, create_task and update_task to add or refine sprint commitments, and move_task to reflect daily progress, keeping the board synced with actual engineering work without manual upkeep.
# Sprint Planning Board Agent Rules
- Board columns: Backlog, Sprint Ready, In Progress, In Review, Done.
- Before sprint planning, call list_tasks on Backlog and move committed items to Sprint Ready.
- Only move tasks into In Progress if they already sit in Sprint Ready.
- Use update_task to add estimates or acceptance criteria before moving a task out of Backlog.
- Never exceed the free plan limit of 25 tasks per project; check list_tasks count before create_task.
- When a task passes review, move it to Done rather than deleting it, so velocity stays trackable.Pull all tasks currently in Backlog and suggest which ones fit into next sprint based on priority labels.
Move every task marked done in In Review over to the Done column and summarize what shipped this sprint.
Create a new task in Sprint Ready for fixing the flaky checkout test and assign it a short description of the failure.
Learn more about the board-centric workflow in Kanban for AI Agents or open the MCP guide.
Frequently asked questions
How many tasks can I put on this Sprint Planning Board?
The free plan supports 1 project with up to 25 tasks total, which comfortably covers a typical two-week sprint. If your team needs more capacity, the Pro plan at $12/mo or $96/yr removes that limit.
Can I customize the column names shown here?
Yes. Backlog, Sprint Ready, In Progress, In Review, and Done are a starting point. You can rename or add columns directly on the kanban board to match your team's workflow, as long as you stay within 3-6 columns.
How do I move tasks between columns quickly?
You can drag tasks on the kanban board, use keyboard shortcuts to jump between columns, or open the command palette to move a task without touching the mouse.
Can an AI agent manage this board for me?
Yes. The MCP server exposes get_board, list_tasks, create_task, update_task, and move_task so an agent can plan sprints, update task details, and shift work through columns automatically.
Is there an API if I want to build my own integration?
Yes, a REST API is available alongside the MCP server, so you can script sprint planning updates or connect the board to other internal tools.
Does this template work outside a browser?
Yes, the macOS app supports the same kanban board and columns, so engineers can update sprint tasks without keeping a browser tab open.
Related templates
Ready to create this board?
Sign in and use the template to create a project with columns and sample tasks.