his trend from the original graph, as in figure 4. "Here's my projected end. I've taken the serial lifecycle graph we had originally and extrapolated out. What do you think?"
|Figure 4: Tristan's projected trend of project complete|
Dan looked and said, "Well, I'' like to think you were being pessimistic, but this is what happens. We finish a little and then finish a lot at the end, and then the testers are overwhelmed, as is the doc group and the rollout group. I have to admit, I much prefer the graph we had where the timeboxes helped us even out the progress." (See figure 3.)
Tristan grinned and added, "Yeah, and if we use timeboxes the whole way through, we can make progress all the time. I bet we could have shortened the project."
Dan frowned, "Well, I'm not sure of that. But I do like seeing the real progress of how many features are done on the project." I'll take this data to the rest of my PMO and see if we can't try a few more agile projects from the beginning."
Data Helps Explain What's Happening in Your Project
If you are considering a transition to agile, or if you're wondering why things are taking so long, consider cumulative flow diagrams. They help you and the entire team see what's going on and what's getting finished in the project-or not. And, if you're considering a transition to agile, the data is a great selling point.
I thank Esther Derby, George Dinwiddie, and Don Gray for their comments.