Forum Discussion

GarryLSPope's avatar
GarryLSPope
Copper Contributor
Jan 20, 2024

Backlog ordering vs Sprint ordering

Hello,

I’m using Azure Dev Ops and would like some help please.

 

When I look at the backlog and put it in a nice order, all my items are correct. But when I bring some items into a sprint and order them, my backlog order is then unordered. 

Our backlog structure is like this:

  • Epic A
    • Feature A1
      • PBI Hot
      • PBI Medium
      • PBI Cold
    • Feature A2
      • PBI Hop
      • PBI Skip
      • PBI Jump
  • Epic B
    • Feature B1
      • PBI Cat
      • Spike Dog
      • PBI Mouse
    • Feature B2
      • Spike Slide
      • PBI Swing

The problem happens when I have the PBIs and Spikes from both EpIcs in a sprint and I need to order them by priority. 


How can I stop the ordering of a sprint from changing the order in my backlog please?

 

Any help would be greatly appreciated. 

Garry

1 Reply

  • Try below:

     

    1. Use a Separate Sprint-Only View:
      • When prioritizing within a sprint, avoid changing the backlog order directly. Instead, use the drag-and-drop feature within the sprint view. This lets you visually organize sprint tasks without affecting the backlog.
    2. Tagging for Sprint Prioritization:
      • Use tags or custom fields to manage priority levels within the sprint without altering the backlog:
        • Add a custom tag like "Sprint Priority: High" or "Sprint Priority: Medium."
        • Filter and sort by this tag within the sprint view.
    3. Custom Queries for Backlogs and Sprints:
      • Create distinct queries for backlog and sprint management.
        • For the backlog, keep the original hierarchy intact (Epics → Features → PBIs/Spikes).
        • For the sprint, generate a prioritized list using a custom column or field.
    4. Linked Work Items:
      • Instead of moving the same PBIs/Spikes into the sprint, create "linked work items" that reference the backlog items. This allows you to manipulate sprint priorities independently while keeping the backlog untouched.
    5. Separate Boards for Sprint Management:
      • Consider creating a dedicated Kanban or Taskboard for sprint management. This allows for independent prioritization without disrupting the backlog order.

Resources