AlphaAlpha Docs

Backlog

Prioritize and groom upcoming work before pulling tasks into sprints

Backlog

The backlog is the prioritized list of all tasks that have not yet been assigned to a sprint. Use it to plan upcoming work, refine requirements, and ensure the most important items are ready when sprint planning begins.

Backlog View

The backlog displays tasks in priority order with key details:

  • Task title and ID
  • Type (Task, Bug, Story, Improvement, Ticket Escalation)
  • Priority (Low, Medium, High, Urgent)
  • Assignee (if pre-assigned)
  • Story points (if estimated)
  • Linked feature or epic

Prioritization

Drag tasks up or down in the backlog to reorder by priority. Items at the top of the backlog are pulled into sprints first during planning.

Priority levels help communicate urgency:

PriorityUsage
LOWNice-to-have; schedule when capacity allows
MEDIUMStandard priority; part of normal workflow
HIGHImportant; should be addressed in the next sprint
URGENTCritical; needs immediate attention

Grooming the Backlog

Regular backlog grooming keeps the list actionable:

  1. Review new items -- ensure titles and descriptions are clear
  2. Estimate effort -- assign story points to help with sprint capacity planning
  3. Link to features -- connect tasks to their parent feature or epic
  4. Set priority -- rank items relative to each other
  5. Remove stale items -- close or archive tasks that are no longer relevant

Moving Tasks to Sprints

When a sprint is in PLANNING status, tasks can be moved from the backlog:

  • Drag and drop tasks from the backlog into the sprint
  • Use the action menu on a task and select Move to Sprint
  • Bulk select multiple tasks and assign them to a sprint at once

Tasks moved to a sprint are removed from the backlog view. If a sprint is completed with unfinished tasks, those tasks return to the backlog unless moved to the next sprint.

Creating Backlog Items

Add new items to the backlog from:

  • The Backlog page using the New Task button
  • The Board if no sprint is active
  • Ticket escalation from the support module (creates a task with type TICKET_ESCALATION)

On this page