How much detail is enough? How much is too much? When it comes to Product Backlog Items, it can be challenging to find that “Goldilocks Point” of getting it “just right”.
In this Responsive Advisors Lightning Round question, PST's Jason Malmstadt, and Gregory Crown and I tackle this issue with some disagreement among the group! Which one makes the most sense to you?
We use a Definition of Ready for everything but support tickets from production. but it basically boils down to Reproduction steps coupled with acceptance criteria. if we have those two pieces then the developer can make it happen again and know what needs fixing, from a bug sense.
for feature type stuff the full DoR is required including steps to show the work is completed, acceptance criteria, screen mock-ups if needed, and refinement usually drags the rest out of the BAs and POs as far as the extras that might be needed to get the job done. We don't get hung up if all the info isn't in the ticket, but make sure we are 85-90% there.
