In the Software Process and Measurement Cast 767,  we continue our summer dive into critical thinking.  In this installment, we consider research and evidence. The discussion of research and evidence ties into this week’s installment of Re-Read Saturday (Chapter 4 of Made to Stick: Why Some Ideas Survive and Others Die which is about credibility). Research and evidence provide credibility and that is not always a good thing.

Tony Timbol brings his To Tell A Story column to the podcast. In this installment, Mr. Timbol continues to unravel the mystery of the agile requirements and user stories.

Re-Read Saturday News

Credibility is the fourth requirement for maximum stickiness (short of Gorilla Glue) discussed in  Made to Stick: Why Some Ideas Survive and Others Die. Credibility is defined as the quality or power of inspiring belief or trust. Without credibility, the attributes of simplicity, unexpectedness, and concreteness crumble. 

Buy a copy of the book and then catch up on the logistics of this re-read:

Week 1: Announcement and Logistics – https://bit.ly/46tn5Bz 

Week 2: Introduction – https://bit.ly/46CLmp1 

Week 3: Simple – https://bit.ly/3PZLWaq 

Week 4: Unexpected – https://bit.ly/43zfkaB 

Week 5: Concrete – https://bit.ly/3qcn1Gg 

Week 6: Credible – https://bit.ly/3Yo9aJo 

Next SPaMCAST 

In the Software Process and Measurement Cast 768, Phil Alves, CEO of DevSquad discusses how he structures teams to perform in dynamic environments. Software development of any stripe is a team sport, you either get it right or suffer the consequences.