DEEP Product Backlog
Agile Prioritization

DEEP Product Backlog

DEEP acronym for Agile Product Backlog, consisting of Detailed Appropriately, Estimated, Emergent and Prioritized principles.
Read more
Get PDF
Tags
Agile DEEP Detailed Appropriately Emergent Estimated Prioritization Prioritized Product Product Backlog Product development
Article

DEEP Product Backlog


How DEEP is your Product Backlog?

Product backlog is an ordered list of the known things that need to be done in a product. The backlog is a living artefact and that is why ensuring that the Product Backlog is DEEP requires regular refining or grooming it.

Detailed Appropriately

Items in the Product Backlog that are on the top should be the more detailed in comparison with the items that are lower. The top ones should be smaller and detailed enough, so they can be completed in the following iteration.


Estimated

Because the Product Backlog is also used for planning, the items at the top should be estimated more accurately compared to the items at lower levels, which are rougher and should be re-estimated as more is known.


Emergent

A Product Backlog is a living artefact, evolving over time. With the progress on the Product the items in the Backlog are added, removed, or rearranged as more is learned.


Prioritized

Priority is based on the value that the items in the Product Backlog brings to the customer. This is the way the Backlog is maximizing value by keeping the highest priority items at the top.


Resources
mountaingoatsoftware.com productplan.com visual-paradigm.com linkedin.com kubairshirazee.com

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.