Listen Now

We began the Re-Read Saturday feature in 2014 with a re-read of John Kotter’s classic Leading Change. The list of books we have re-read is quite long — I am going to have to create a list. All that said, last week a person that regularly comments on the podcast indicated they really did not know what Re-Read Saturday was all about. So today to commemorate spring in the northern hemisphere (and the fact that it snowed) and the kick-off of the latest re-read (Why Limit WIP by Jim Benson) I am going to share an audio version of this week’s entry.  As we always say, buy a copy of the book and read Jim Benson’s Why Limit WiP (buy a copy using our Amazon Affiliate link get reading) along with us.

The written version: 

This week we also have a visit from Jeremy Berriault, who brings his QA Corner to the podcast.  Jeremy and I explored the difference between relative and absolute time. 

Listen Now!

Organizational design often collides with getting work done; generating friction that causes all manner of problems. No one goes out of their way to make things difficult, however poor operating metaphors and one size fits all solutions are never optimal. There is a way for agile and team leaders to coexist, but can you take that path?

Also this week, Jon M Quigley and his Alpha and Omega of Product Development column make time for the cast. In this installment, we talk about time (including a few time-related puns).


Progress is easy to visualize when we use the yardstick of calendar time. My wife and I spent 17 days in Europe. There are 197 shopping days until Christmas (as of June 12, 2018) — I expect presents this year. How long it takes to deliver a piece of work, in days, is something nearly every human can understand. Over the past few months, I have been cataloging questions I have heard. Well over 70% of work-related questions center on how long a piece of work will take and whether the answer to that question has value. Cycle time metrics are ways to generate answers to ‘how long’ questions in a manner that is valuable and predictable. (more…)


The simple cumulative flow diagram (CFD) used in Metrics: Cumulative Flow Diagrams – Basics  and in more complex versions provide a basis for interpreting the flow of work through a process. A CFD can help everyone from team members to program managers to gain insight into issues, cycle time and likely completion dates. Learning to read a CFD will provide a powerful tool to spot issues that a team, teams or program may be facing. But to get the most value a practitioner needs to decide on granularity, a unit of measure, and time frame needed to make decisions.