The Product Backlog is a key feature of Agemba that helps Product Owners prioritize and manage their product development process.
By using the Product Backlog, Product Owners can easily prioritize which features should be developed first based on the needs of the customers, the business goals, and the technical feasibility. They can also collaborate with the development team to estimate the effort required for each item on the backlog and make informed decisions about which items should be included in each development sprint.
The Product Backlog allows Stories, Ideas and Issues to be planned and prioritized within specific Releases, Sprints, Kanban Lanes or Preplanned Lists, providing transparency for everyone involved.
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 the 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 that enable items to be planned and prioritized.
Kanban Lanes
Kanban lanes can be configured to match the states the desired workflow requires. Start and completion criteria are identified, and each intermediary step has its own implementation criteria.
Inherited Planning
When an Epic is planned for a Release, this typically represents high-level planning, which needs further qualifications. Unless they are planned themselves, all Stories beneath this Epic will inherit this planning and be regarded as “indirectly” planned for 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 Storymap, thereby giving a good overview of whether all Stories have been planned to Sprints.
Preplanned Lists
Preplanned lists are simply containers used to organize stories that are awaiting to be planned into Releases, Sprints or Kanban lanes.
How-to Video
This video offers a “how-to” go-through of the Product Backlog
