Scrum board features for calmer project delivery.
CalmBoard combines a focused 5-state Scrum board, sprint planning, backlog grooming, delivery reports, and AI project management agents. This guide shows how to use Scrum board features, how to read the reports, and how to apply Scrum board best practices without adding process noise.
Visual aid
A focused 5-state workflow
CalmBoard starts with Backlog, Ready, In Progress, Review, and Done. Teams can track work without turning the board into a complex process map.
Backlog
Ready
In Progress
Review
Done
Everything needed to plan, track, review, and learn.
Task management
Create tasks, edit descriptions with markdown, add checklists, upload attachments, assign users, set due dates, mark blocked work, and pin important cards for quick access.
Sprint planning
Create planned, active, and completed sprints, assign tasks to sprint windows, inspect active sprint progress, and move unassigned completed tasks into the current sprint when appropriate.
Backlog grooming
Use the Backlog and Ready columns to separate ideas from committed work. Keep task names clear, descriptions specific, and checklist items small enough to review.
Board Assistant
Ask questions about tasks, sprints, users, board progress, velocity, throughput, risks, and next actions from a chat modal connected to board context.
Fast daily work
Use keyboard shortcuts, inline add buttons between cards, filters, fixed cards, and mobile menus to move quickly without losing board structure.
AI settings
Turn board AI features on or off, choose favorite agents, and control cron-generated insights per board while still allowing manual insights when needed.
A simple operating rhythm
CalmBoard works best when the board reflects real decisions. Keep Backlog open for ideas, Ready for shaped work, In Progress for active work, Review for validation, and Done for completed outcomes.
1. Groom the backlog
Clarify task names, add acceptance details, attach supporting files, and split large work before it enters a sprint.
2. Plan the sprint
Choose a sprint goal, pull only ready tasks, confirm capacity, and use estimates or WIP time depending on how your team works.
3. Run the board daily
Move cards when the state changes, add short comments for decisions, and review blocked or aging work before adding more WIP.
4. Inspect and improve
Use Sprint timeline, reports, and AI insights to understand what shipped, what slipped, and which next action matters most.
Sprint timeline, delivery intelligence, and executive visibility.
CalmBoard includes reports for teams that use sprints and teams that run continuous flow. When sprint data is missing, several insights can fall back to week-based analysis.
Burndown
Remaining work
Velocity
Sprint or week
Throughput
Done tasks
Gantt
Timeline view
Scope & Change Report
- New tasks added vs completed
- Work inflow vs outflow
- Repeatedly expanded tasks
- Scope creep summary
Delivery Intelligence
- Average cycle time per list
- WIP per member
- Blocked ratio
- Reopened task percentage
- Throughput per week
Predictability
- Monte Carlo forecast
- Completion probability
- Overcommitment detection
- Sprint reliability score
Team Dynamics
- Uneven workload detection
- Hero syndrome detection
- Context switching index
- Private coaching digest support
Weekly Executive Report
- What shipped during the week
- What slipped and why
- Top delivery risks
- Delivery confidence
- Next week focus
AI insight reports
- Daily summary for active sprints
- Sprint health insight
- Sprint review and retrospective insight
- Developer Coaching Digest for private growth feedback
Agents that turn board activity into focused recommendations.
Learn more about the value of these agents in Values delivered by CalmBoard AI Agents.
Practical habits for better flow.
Keep work small
Split large tasks before sprint planning. Small cards move faster, are easier to review, and make blockers visible sooner.
Use Ready as a quality gate
Only move work to Ready when the team understands the outcome, acceptance details, and dependencies.
Limit active WIP
If In Progress keeps growing, stop starting and start finishing. Review throughput before adding more work.
Make blockers explicit
Mark blocked tasks and leave short comments explaining the dependency. AI insights become more useful when context is clear.
Review reports weekly
Use Scope & Change, Delivery Intelligence, Predictability, and Team Dynamics to inspect system health, not to rank people.
Let AI suggest, not decide
Use Board Assistant and insight cards to surface signals, then keep prioritization and scope decisions with the team.
Start with a real board
Use CalmBoard to plan your next sprint with less overhead.
Create a project, open the first board, add a few backlog items, and enable AI insights when you are ready to inspect the work.