Preview Mode Links will not work in preview mode

Software Process and Measurement Cast

The Software Process and Measurement Cast provides a forum to explore the varied world of software process improvement and measurement.  The SPaMCast covers topics that deal the challenges how work is done in information technology organizations as they grow and evolve.  The show combines commentaries, interviews and your feedback to serve up ideas, options, opinions, advice and even occasionally facts. 


Oct 2, 2022

SPaMCAST 723 features our essay on neglected WIP. Work that has been started and is now just sitting around is neglected. Running a team or organization above their natural level WIP for any length of time causes flow velocity (throughput) to slow and flow time (cycle time) to increase. When there is too much work, people try all sorts of techniques to get work done. Multitasking is the grandfather of them all and we all know how that turns out (need a hint – badly). In the end, all approaches to trying to do too many ends up with some things being juggled and ignored. That is neglected WIP.

We also have a visit from Jon M Quigley and his Alpha and Omega of Product Development Column. In this column Jon and I discuss time. Speaking of time, this is a lost episode…we started the episode discussing snow, last year's snow. We talked last week and were discussing when the first snow will be this year. Sometimes time flys and sometimes it doesn’t.

Re-read Saturday News

This week we reread Chapter 10 of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate link The chapter is titled Coach as Coordination Conductor. The two most important items for me during this read of chapter 10 are found in the first part of this chapter. Reflecting back on my previous cover-to-cover read, I think that the number of great facilitation techniques in this chapter caused me to overlook two very important concepts. The first is an approach for differentiating collaboration and coordination. The approach is simple but very powerful. Why would any coach care about observing the difference? Because the two concepts are different and are useful in different scenarios. 

Logistics Note:  We have three more chapters in this book which we will follow with a recap before starting. Extraordinarily Badass Agile Coaching: The Journey from Beginner to Mastery and Beyond (Amazon Associate Link – buy your copy soon and start reading). Buy a copy now and start reading. 

Remember to buy a copy of  Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line and read along!

Previous Installments

Week 1: Logistics and Introduction - 

Week 2: Will I Be A Good Coach - 

Week 3: Expect High Performance - 

Week 4: Master Yourself - 

Week 5: Let Your Style Change - 

Week 6: Coach as Coach-Mentor - 

Week 7: Coach as Facilitator - 

Week 8: Coach As Teacher - 

Week 9: Coach As Problem Solver - 

Week 10: Coach As Conflict Navigator - 


A quick advertisement:

Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. We recently delivered the workshop at the 2022 Path to Agility in Columbus, OH to rave reviews. Interested? Email us at or


Next week we will feature an interview with Indus Khaitan, Founder & CEO at Quolum. Indus and I talked about SaaS, controlling SaaS spending, and serial entrepreneurship.