Use Cases

Backlog Refinement

Refine a perpetual backlog board in Table view — break down, estimate, link dependencies and rank — so sprint planning is a pull from the top.

Setting

The team keeps its backlog as a perpetual Backlog board in its folder, next to its sprint cycles. Refinement happens weekly, in Table view, with the Product Owner driving and the team estimating. Everyone needs Editor access to the folder and edit rights on the items.

Steps

  1. Open the backlog in Table view. In Plan Delivery, open the Backlog board and click Table view. Under Options → Table columns, show Item Type, Point Estimate, Time Estimate, Relationships, Blocked Reason and Assignee. Save it as a View called Refinement so the layout is one click next week.
  2. Add what's new. Click Import to bring in items created in Map Value since last time (filter Status New), or Item to create something new directly — it goes into the workstream you choose and onto the backlog.
  3. Clarify and break down. Open a row (click the item) to tighten the description. For an epic too big for a sprint, turn on Show hierarchy and create children under it; with Child items inherit their parent's sprint and team on, children follow the parent's board. Only the level you will plan should stay on the backlog — a parent and its child are not both imported into a sprint.
  4. Estimate. Edit Point Estimate (or Time Estimate) in place; use the keyboard to move down the column. Board Totals in the footer shows the backlog's total size as you go.
  5. Link dependencies. Select the rows that depend on something and use Edit → Relationships → Add Dependencies, or click a card's relationship icon. Dependencies on other teams' items will later appear in the sprint's External Dependencies row.
  6. Rank. Clear any sort, then drag rows into priority order (or use Sort & Rank → Rank). Rank is shared; sprint planning imports from the top.

Definition of ready

An item is ready when its row has: a clear title and description, an item type at the right level, an estimate, its dependencies recorded, and a position in the rank. Sort the Point Estimate column ascending to surface the unestimated rows.

Next

Plan a sprint pulls from this board. For the Table view's hierarchy, rank and bulk-edit controls, see Track and move work with board views.