Scrum teams work in fixed iterations called sprints, typically lasting one to four weeks, which are planned and tracked per team. This workflow helps teams plan predictable delivery cycles, commit to specific work for each sprint, and track progress using story points and velocity.

How Scrum works in Atono

When you create a Scrum team, Atono structures their workflow around sprint-based planning:

Sprint planning with story points - Instead of estimating completion dates for individual items, Scrum teams size stories using story points and plan sprints based on the team's velocity. This helps you commit to a realistic amount of work for each sprint.
Time-boxed iterations - Work moves into progress only during a planned sprint. The team commits to a specific set of stories at the start of the sprint and focuses on completing that scope by the end date.
Burndown tracking - During each sprint, burndown charts show your progress and project whether you'll complete the committed work on time. This helps teams adapt mid-sprint if needed.

Scrum team pages

Scrum teams have three dedicated pages designed around sprint-based planning:

In progress

Execute on the current sprint and track daily progress. This page shows only the items in your active sprint, with list and board views to help you track completion. Learn more

Backlog

Plan future sprints and organize your product backlog. The backlog groups items by sprint, allowing you to schedule work into specific sprints, create new sprints, and manage what's coming next. Learn more

Sprint calendar

View and manage all sprints on a calendar. The Sprint calendar gives you a bird's-eye view of past, current, and future sprints—perfect for long-term planning and scheduling. Learn more

Key differences from Kanban

If you're used to Kanban workflows, here's what's different with Scrum in Atono:

No estimated completion dates - Planning is based on story points and sprint capacity, not cycle time projections.
Sprint boundaries - Work is scheduled into specific sprints rather than flowing continuously from the backlog.
Velocity tracking - Teams measure how many story points they complete per sprint to improve future planning.
Burndown charts - Track daily progress toward sprint completion instead of continuous flow metrics.

Getting started with Scrum

Create your first sprint - Visit your team's Backlog page and create a sprint with a start date, end date, and name. Most teams start with a two-week sprint length.
Add items to the sprint - Drag stories from the Unscheduled section into your sprint. Use your team's estimated velocity to guide how many story points to include.
Start the sprint - Once the sprint's start date arrives, it becomes the current sprint and appears on the In progress page. Your team can begin executing on the committed work.
Track progress daily - Use the burndown chart to monitor progress and spot issues early. The projection line helps you see whether you're on track to complete everything by the sprint end date.
Complete the sprint - As stories move to 'Done', they're removed from the burndown. At the end of the sprint, review what was completed and plan your next sprint.

Tips for Scrum teams

Keep sprints consistent - Most teams benefit from consistent sprint lengths (for example, always two weeks). This makes velocity more predictable and planning easier.
Limit mid-sprint changes - While you can add work mid-sprint, it affects your burndown chart and makes velocity harder to track. Try to keep sprint scope stable once the sprint begins.
Review past performance - Use the Sprint calendar to look back at completed sprints and review their burndown charts. This helps you spot patterns and improve future planning.
Plan based on velocity - After a few sprints, you'll know your team's average velocity. Use this to guide how many story points to include in future sprints—and avoid overcommitting.