Agemba’s Product Backlog is a planning tool which links the customer to those creating the deliverable the customer order. It typically contains specifications, product descriptions, infrastructure initiatives and other activities that define customer requirements and convey the scope and nature of what is to be produced.
The Product Backlog allows Stories, Ideas and Issues to be planned and prioritized within specific Releases, Sprints, Kanban Lanes or Preplanned Lists, providing total organizational transparency.
Releases and Sprints
Each Release is a milestone with a deadline, visible to all stakeholders. Releases may contain multiple Sprints. Both Releases and Sprints are shown as containers in the Product Backlog and Story Cards can be dragged into these containers to plan them.
Prioritizing and Planning Stories
The left pane of the Product Backlog contains tools for filtering and sorting existing items. They can be sorted by multiple criteria including: level of complexity, effort or value estimate, title or timestamps and filtered by item type such as: “Stories,” “Epics” (or both) “Issues,” “Ideas” etc. There is also a Text Search for locating items using keywords or phrases. The tools allow the user to create highly refined lists enabling items to be planned and prioritized to optimum effect.
Kanban lanes can be configured to match the states required by the desired workflow. Start and completion criteria is identified and each intermediary step has its own implementation criteria.
When an Epic is planned to a Release this will typically represent a high level planning, which needs to be further qualified. All Stories beneath this Epic will – unless they are planned themselves – inherit this planning and be regarded as “indirectly” planned to this Release. When the user wishes to plan these Stories in detail, Detailed Planning in the left pane will show the tree structure of the Epic with all stories beneath it like the one in the Story Map, and thereby give a good overview of whether all Stories have been planned to Sprints.
Preplanned lists are simply containers used to organize stories that are awaiting to be planned into Releases, Sprints or Kanban lanes.