Sprints & Backlog
Sprints and the backlog are the planning layer for teams working in Scrum. The backlog holds work that isn't scheduled yet; a sprint is a time-boxed batch of stories you commit to for a period.
The backlog
Open PM → (your project) → Backlog. The backlog view shows:
- your sprints (those in planning and the active one), each with a progress bar, and
- a Backlog section with every story that isn't assigned to a sprint.
Drag stories between the backlog and a sprint lane to plan what goes where. You can add a story directly from the backlog with the Add Story form, and use search and filters to find work quickly. The backlog is ordered by priority first (critical → high → medium → low), then by your manual ordering.
Sprints
Open PM → (your project) → Sprints to see every sprint and its status:
| Status | Meaning |
|---|---|
| Planning | Being filled with stories; not started yet. |
| Active | Currently running. Only one sprint can be active per project at a time. |
| Completed | Finished. |
Each sprint card shows its story count, total and completed story points, a progress bar, and the velocity.
Starting a sprint
Click Start Sprint on a planning sprint to make it active. Because only one sprint can be active per project, you must complete the current sprint before starting another.
Completing a sprint
Click Complete Sprint on the active sprint. Any stories that aren't finished are returned to the backlog automatically (their sprint assignment is cleared) so you can pull them into the next sprint.
Burndown and velocity
When a sprint starts, Hubrix begins tracking a burndown — the remaining story points over time — and updates it as stories are completed and when the sprint closes. Velocity is the number of points completed, and it is averaged across your completed sprints to inform future planning and the AI sprint planner.
Burndown and velocity rely on story points and the board timestamps. For accurate charts, estimate your stories in points and keep their status up to date as work progresses.
Kanban without sprints
If your project uses the Kanban methodology, you don't have to use sprints at all — work simply flows across the board. Sprints and the backlog are there when you want them, but they're optional.
Was this helpful?