Nov 3, 2019
SPaMCAST 571 features our essay titled the Art of Saying No. I recently presented a workshop on saying no -- a simple word that is very difficult to say. During the session, three specific reasons why participants could not say no generated a huge debate. Today we ask you to decide how you feel about the impact of a history of performance, interruptions, and demands. Feel free to share your opinion.
We will also have a visit from Jeremy Berriault. In the QA Corner this month, Jeremy provides observations about outside interests and their ability to improve focus and reduce burnout. Jeremy’s outside interests are Jiu-Jitsu and his family. Jeremy can be reached at Berriault and Associates Consulting Group or by email at Jeremy.Berriault@Berriaultandassociates.com.
We had planned to have Michael Larsen on the cast this week, however, Mr. Larsen was affected by power outages in the Bay Area of California due to wildfires.
Re-Read Saturday News
In this week’s installment of our re-read of Thinking, Fast and Slow we consider Chapter 25, Bernoulli’s Errors. When I first read the chapter I struggled with how Kahneman’s ideas translated to process improvement and change programs. I was naive enough to believe that the majority of outcomes could be predicted based on the economic outcome. After seeing more than one change program fail even though they could have had a positive return on investment, it dawned on me that the context and preexisting conditions as described in Chapter 25 should play a part in planning for change.
Remember, if you do not have a favorite, dog-eared copy of Thinking, Fast and Slow, please buy a copy. Using the links in this blog entry helps support the blog and its alter-ego, The Software Process and Measurement Cast. Buy a copy on Amazon, It’s time to get reading!
The current installment of Re-read Saturday
SPaMCAST 572 will feature our interview with Michael Larsen -- assuming the fires and Santa Ana winds cooperate. Michael and I will discuss testability. Anyone that has participated in delivering software EVER has wrestled with this problem. Michael brings fresh and actionable insights into how to assure testability.