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. 

 

Sep 17, 2017

SPaMCAST 460 features our interview with Peter Varhol.  Peter and I discussed machine learning and AI, and how it will impact software development and testing.  We also discussed how anyone can stay current and enhance their careers.

Peter’s Bio

Peter Varhol is a well-known writer and speaker on software...


Apr 17, 2017

The Software Process and Measurement Cast 438 features our essay on leveraging sizing in testing. Size can be a useful tool for budgeting and planning both at the portfolio level and the team level.

Gene Hughson brings his Form Follows Function Blog to the cast this week to discuss his recent blog entry titled,


Aug 7, 2016

The Software Process and Measurement Cast 406 features our interview with Erik van Veenendaal.  We discussed Agile testing, risk and testing, the Test Maturity Model Integrated (TMMi), and why in an Agile world quality and testing still matter.

Erik van Veenendaal (www.erikvanveenendaal.nl) is a leading international...


Jul 5, 2015

To paraphrase Ed Sullivan, “We have a big, big show this week,” so we will keep the up front chit chat to a minimum.  First up is our essay on Agile Testing. Even if you are not a tester, understanding how testing flows in Agile projects is important to maximize value.

Second, we have a new installment from...


Jun 22, 2014

SPaMCAST 295 features our essay on Test Driven Development (TDD). TDD is an approach to development in which you write a test that proves the piece of work you are working on, and then write the code required to pass the test. You then refactor that code to eliminate duplication and any overlap, then repeat until all...