tag:blogger.com,1999:blog-1338078043432413205.post5890363439842547661..comments2010-02-04T08:51:00.929ZComments on Chris's TechBlog: Starting with Kanban Q&AChrishttp://www.blogger.com/profile/06822657682662520386noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1338078043432413205.post-55782843674373470622010-02-04T08:51:00.929Z2010-02-04T08:51:00.929ZI was thinking more along the lines of story sizes...I was thinking more along the lines of story sizes not breaking the service level agreement (eg 'cards are done within 3 days'), but I see where you are coming from - it's exactly the same way as they were doing with their "traditional" story planning. "Large" stories tended to get broken into multiple, smaller stories during the Planning Game. Here they would be split when the story epic was played.Chrishttp://www.blogger.com/profile/06822657682662520386noreply@blogger.comtag:blogger.com,1999:blog-1338078043432413205.post-42454103273209601052010-02-03T22:32:21.612Z2010-02-03T22:32:21.612ZAbout the problem of forecasting:
But the proble...About the problem of forecasting:<br /><br /><i> But the problem is the extensive backlog. There is no guarantee that the stories are correctly sized...</i><br /><br />One possible solution: You can have the team estimate the stories in the backlog using T-shirt sizes S, M, L, XL. Then, you measure the cycle time for stories and calculate an average for each category. Record these average values and calculate how long the rest of your backlog will take.Matthias Bohlenhttp://www.mbohlen.denoreply@blogger.com