Loading Profile...
Twitter,
Facebook, or email.
Hello
New year, new tricks. I'm currently combining kanban ideas to scrum. Web GUI already supports that pretty well but to improve it I'd like also to follow lead time of PBIs (quicker is better). Would it be possible to generate such report from PBI creation to the date when it has been done. Report could contain average PBI lead time in release, by steps (open, in progress and done) and maybe compare it to PBI size . Information is there (PBI history) but it should be combined and showed somehow.
Thanks
Jaakko
I’m
thankful, excited, happy
Lead time / Cycle time report for PBIs
-
Hi Jaakko,
We've had an idea for such a report for quite a while. In the lean world, this is often called "cycle time", so i updated the title of your post to reflect that.
I'm curious if others would find this useful.Comment -
-
Question on this report for you.
Would you want lead time calculated from the creation date of the PBI, or if the PBI was created a long time ago, would you want to the lead time based on the release start date?
I can see a lot of value in basing it on the release start date since the item, while old, may not have become a priority until it was prioritized into a particular release for execution.
Thoughts?
-- Victor-
Hi,
Could there be option which way to use? Or maybe there could be more dates in the report: one for the creation and one for the release start date. -
-
-
-
-
Hi Victor
I was thinking that calculation would be divided by steps so average lead time for creation -> in progress, in progress -> done and average of those. I agree that some lo prio stories will make lead time to look much worse than it actually is so starting calculation from release start date would be good fix for those problems. Additionally user could deselect some stories that affect average too much but that is not very important.
Jaakko -
-
This report is now available as part of ScrumWorks Pro 4.5:
http://danube.com/scrumworks/pro/rele...
Happy Scrumming! -
EMPLOYEE
