RE: Re: Metrics for Product Backlog
| Newsgroups | gmane.comp.programming.scrum.general |
|---|---|
| Message-ID | <[email protected]> |
If that is the case then the only way you know whether the PO has managed the PB effectively is after the product is released. Unless the product is released, you don't really know whether the PO has managed the PB effectively. If your customers scream then it is not the right PB to be developed, it your customers give praise then it is the right PB to be developed. I like using AARRR metric for that reason. Kindest regards, Joshua Partogi http://www.leanwithagility.com From: [email protected] To: [email protected] Date: Tue, 26 May 2015 08:39:38 -0700 Subject: [SCRUMDEVELOPMENT] Re: Metrics for Product Backlog Hi, Steve, In no way do I want to compare POs! As I wrote I'm interested in understanding how PO can do better with product backlog. Prob some trivial example, if PO keeps pulling to the top low severity bugs instead of more valuable critical bugs, that I'd say something could be done differently. Or, as another example, if some PBI has been too long on backlog (lead time) and so on. One more example could be PO spending too much time on 'detailing' PBIs deep down the backlog I would suggest that improving the measures of calculating PB item business benefit would be a better subject to spend your time on.Can you suggest such measures? Anything in particular you meant there?