Teams using Kanban workflow in Atono focus on continuous flow rather than fixed iterations. Work moves from a team's backlog into progress as capacity allows, and planning uses cycle time and estimated completion dates to forecast when items will be completed.

When you create a team and choose Kanban workflow, you get access to pages optimized for visualizing work in progress and maintaining steady delivery.

How Kanban works in Atono

Kanban teams organize their work around continuous delivery:

Cycle time and estimated completion dates - Instead of planning in sprints, Kanban teams track how long items take to complete (cycle time) and use that data to project when future work will be done. This helps you set realistic expectations with stakeholders.
Continuous flow - Work moves into progress whenever the team has capacity. There are no fixed iteration boundaries—items flow from the backlog through your workflow steps and into completion as they're ready.
WIP management - Teams focus on limiting work in progress to maintain flow and identify bottlenecks. The goal is steady, predictable delivery rather than committing to a fixed scope.

Kanban team pages

Kanban teams have two dedicated pages designed around continuous flow:

Backlog

Prioritize and organize your product backlog for continuous planning. The backlog shows all 'To do' items, allowing you to reorder work by priority and decide what the team should pull next. Learn more

In progress

Track active work as it moves through your workflow. This page shows the 20 most recent 'To do' items plus all work in progress, with list and board views to help you manage flow and spot bottlenecks. Learn more

Key differences from Scrum

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

No sprints - Work flows continuously rather than being scheduled into fixed iterations.
Estimated completion dates - Planning uses cycle time data to forecast when items will be done, rather than story points and velocity.
Pull-based workflow - The team pulls the next priority item when capacity is available, rather than committing to a sprint scope.
Continuous planning - Backlog refinement and prioritization happen ongoing, not just at sprint boundaries.

Getting started with Kanban

Prioritize your backlog - Visit your team's Backlog page and order items by priority. The top items are what your team should pull into progress next.
Set capacity limits - Consider how many items your team can realistically work on at once. Limiting work in progress helps maintain flow and surface blockers early.
Pull work as ready - When someone finishes an item, they pull the next priority item from the backlog into progress. No need to wait for an iteration boundary.
Monitor cycle time - Watch how long items take to complete. If cycle times increase, it may signal bottlenecks or capacity issues that need attention.
Review projected dates - Use estimated completion dates to communicate with stakeholders about when work will be done. These update automatically as your team's cycle time changes.

Tips for Kanban teams

Limit work in progress - Resist the urge to start too many things at once. Finishing work is more valuable than starting it, and limiting WIP helps your team maintain steady flow.
Keep the backlog prioritized - Regularly review and reorder your backlog so the team always knows what to pull next. Clear priorities prevent confusion and reduce context switching.
Track cycle time trends - If items are taking longer than expected, investigate why. Common causes include unclear requirements, technical complexity, or too much WIP.
Refine continuously - Don't wait for a special ceremony to refine your backlog. Break down upcoming work and add details as you learn more, keeping a steady pipeline of ready items.