Skip to content
  • Tools
  • Training
  • Knowhow
Menu
  • Tools
  • Training
  • Knowhow
  • English
  • German
0,00€ 0 Cart
0,00€ 0 Cart
Say hi!
  • back

How DEEP is your product backlog? 🤔📋

April 13, 2022
defintion of a deep backlog

For me a great starting point is the acronym DEEP:

D-etailed enough (is the Definition of Ready for the Features for the next 2-3 Sprints clear) 🧐

E-mergent (are you, your team and your stakeholders aware the the Product Backlog can and will change over time? Here is a lot of the business agility and flexibility everyone is looking for) 🤸

E-stimated (are the user stories estimated, supporting the POs with the next word – prioritised, and it helps the team to be aware of what is coming and what is the complexity of the user stories) 🃏

P-rioritised (is your Product Backlog prioritised and what are the measurements you are using: business value, risk reduction, dependancies) 🔝

What method are you using to create an awesome product backlog? 🙇‍♂️📈

previous post Snapshot together with ELMO next post Success of a scrum team
  • Imprint
  • Data Security
  • Terms
  • Recovation
  • Shipping and Payment
  • Contact
  • Amazon
  • Imprint
  • Data Security
  • Terms
  • Recovation
  • Shipping and Payment
  • Contact
  • Amazon
  • About Ulassa
  • Manifesto Ulassa
  • Blog
  • Testimonials
  • Training
  • Tools
  • Digital Kudos
  • About Ulassa
  • Manifesto Ulassa
  • Blog
  • Testimonials
  • Training
  • Tools
  • Digital Kudos

We make teams happy!