Using Cumulative Flow Diagrams in User Education

re: Using Cumulative Flow Diagrams in User Education

Monty — Wed, 27 Mar 2013 14:24:53 GMT

Link is broken

Re: Using Cumulative Flow Diagrams in User Education

Lara — Tue, 10 Feb 2009 21:44:55 GMT

How do I download the spreadsheet? I can't find a link on the page.

Thanks.

re: Using Cumulative Flow Diagrams in User Education

vstsuetb — Tue, 06 Feb 2007 01:50:14 GMT

Hi Jim,

Fundamentally we report on how many topics move to the last state in the stats section. So if the last state is "Ready for Tech Review" we report on how many topics made it to tech review.

Hope this helps,

David Chesnut

Content Lead

Questions about using CFD with Visual Studio Team System

Visual Studio Team System User Education — Tue, 21 Mar 2006 18:40:11 GMT

Daniel sent in a few questions regarding my previous post about using cumulative flow diagrams&nbsp;(CFD)...

re: Using Cumulative Flow Diagrams in User Education

Jim Sowers — Fri, 10 Feb 2006 07:02:58 GMT

What stats do you report on with your stats spreadsheet?

re: Using Cumulative Flow Diagrams in User Education

Rob Evans — Wed, 18 Jan 2006 19:12:35 GMT

This is *very* helpful. Thank you.

re: Using Cumulative Flow Diagrams in User Education

vstsuetb — Tue, 17 Jan 2006 02:12:12 GMT

Hi Jiho,

Great question! Unfortunately in trying to keep the blog post under 12 pages, I left out lots of detailed discussions about things such as capacity.
We use capacity to plan our next sprint. We do not estimate by costing each topic. Estimation takes time, and we've found it fairly inaccurate for our purposes. But if we average around 100 topics per sprint, we get a pretty good idea that we'll probably deliver around 100 topics in the next sprint (barring any unusual changes).
There is variance as you point out, and topics in one sprint may be more difficult than another. We buffer for this variance to be sure we can deliver by agreeing to deliver slightly less than our average capacity. So we may agree to do 90 topics in one sprint even though our capacity is 100 (a buffer of 10).
David Anderson's book, "Agile Management for Software Engineering," has excellent explanations of using buffers if you are looking for more information on this.
Hope this helps,
David

re: Using Cumulative Flow Diagrams in User Education

Jiho Han — Thu, 12 Jan 2006 19:17:29 GMT

One question I have is what does it mean for your team's capacity to be of some number? It doesn't make sense to me when you say, for example, your team's capacity is 100 topics per sprint. Surely, each and every one of your topic is different in its complexity and the time it takes to complete.
Is it possible that you can have a capacity of 50 in a sprint, then have 100 next, then 30, etc.? If so, what does it prove?

Really, I am a developer/team lead who's beginning to look for ways to improve our process and recently started looking into things and found David Anderson's website and TOC and the whole agile movement.

Thanks

Thanks