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. 


Feb 20, 2022

In SPaMCAST 69, Kevin McKeel talks about using neurolinguistics to aid in software estimation tools. Is this the end of the world for the software estimating profession or the beginning of a golden age?  Probably both, listen and draw your own conclusions.

Kevin’s Bio

Mr. Kevin McKeel has over 25 years of experience in software cost estimation. He is a CCEA and SAFe Architect and received the prestigious 2021 Technical Achievement of the Year award from ICEAA related to the research of automated software sizing using AI and NLP. Mr. McKeel holds a Bachelor’s in Business Administration (Finance, ‘89) from James Madison University and a Master’s in Business Administration (Decision Systems, ’92) from The George Washington University.



Re-Read Saturday News 

Week 8 of our re-read of  Agile Conversations by Douglas Squirrel and Jeffrey Fredrick concludes our read of Chapter 5 addressing the ‘Why Conversation’. This week we spent time tackling the concepts of joint design and urging organizations to train team leads in decision making. They are not second class citizens

My experiment of the week:

Last week I proposed the experiment of creating a position-interest chart during the week. I actually used the technique to help frame an essay for the Software Process and Measurement Podcast within 12 hours of proposing the experiment. I also used the ideas in the approach to reframing several discussions (looking for the positions behind stated positions) during the week. 


This week I will try to find a scenario to apply the concepts of joint design (no eggs will be harmed). 


Week 1: Logistics and Introduction - 

Week 2: Escaping The Software Factory - 

Week 3: Improving Your Conversations - 

Week 4: The Trust Conversation - 

Week 5 The Fear Conversation (Part 1) - 

Week 6 The Fear Conversation (Part 2) - 

Week 7 The Why Conversation (Part 1) - 

Week 8 The Why Conversation (Part 2)  -


What would you call a person with little training, a lot of responsibility, and little to no real authority?  This is not a Dad Joke.  I suggest the answer is often a team lead. 


Also, Mr. Tony Timbol is back to talk about user stories in his To Tell A Story column.