Software Process and Measurement Cast

SPaMCAST 530 features our interview with Justin McPherson.  Justin and I talked about the role of the enterprise architect in agile. Organizations struggle with the role of the architect as they embrace agile methods.  However it is not all about agile, the multiple layers of architecture such as solution, application and enterprise add to the confusion and the perception that people need to jump through too many hoops.  Justin’s experience provides direction.

SPaMCAST 529 features our essay titled Habit and Commitment.  We are still early enough in the year to be pursuing the New Year resolutions you made a few weeks ago.  Commitment and habits can be positively interrelated. Commitment is being dedicated to a cause or activity. Habits reflect a more or less fixed routine. We also have a visit from the Software Sensei, Kim Pries.  Kim discusses nonlinear and analog thinking. Kim’s essay is a perfect counterpoint to Habit and Commitment

SPaMCAST 528  features our interview with Allan Kelly.  Allan makes his third appearance on the cast to talk about his book Continuous Digital (buy a copy!) and the state of agile.  A great way to start the year!

SPaMCAST 527, is our last podcast of 2018.  We say goodbye to 2018 by talking about user story maps.  User story maps are both versatile and an underused tool. Perhaps something that we can address in 2019? We also have a visit from Susan Parente.  Susan brings her Not a Scrumdamentalist column to the cast to discuss agile risk management.  Risk management is a requirement for any form of work. Why do some in the agile community feel it is not needed?  

SPaMCAST 526 features an interview with Freddie Clark.  Mr. Clark is a tester and Scrum Master by day and video game entrepreneur in the evening.  We had an in-depth conversation about using Scrum and other agile techniques in a lean startup environment.  It is not the same as the standard corporate environment.

SPaMCAST 525 continues our conversation about story points.  Many teams find that story points are only a partially useful tool to facilitate the flow of work within a team. Today we will highlight a behavioral fix and talk RATS. We will also have a visit from Jeremy Berriault with a discussion from the QA Corner.  Jeremey and I talked about how the concept of a minimum viable product (MVP) impacts testing.  Check out Mr. Berriault’s blog at https://qacorner.blog/

SPaMCAST 524 features the return of Matt Heusser.   Matt and I talk about the nuts and bolts of being a tester in today’s software environment including agile testing.  Matt and I had covered difficult areas that anyone that is interested in quality and risk needs to think about.

SPaMCAST 523 features our essay on story points.  Story points were a tool designed to give teams a rough understanding of their flow of work. It was a great idea at the time, but that time has passed. Unfortunately, story points now are being used improperly creating more problems than they solve. In addition, Jon M Quigley brings his Alpha and Omega of Product Development to the cast. In this installment, Jon discusses the risks of Centers of Excellence.  

The Software Process and Measurement Cast 522 features the return of Jeff Anderson.  Jeff returns to discuss scaling agile and getting to a minimum viable product. Many teams and organizations struggle with the concepts of scaling and getting to an MVP, Jeff provides advice for not going crazy!

SPaMCAST 521 features our essay on user stories and legacy code.  A common question is how user stories can be developed for legacy code or for problems that crop up in production.  The implication is that creating user stories is too hard when dealing with legacy code changes or too slow when dealing with production problems.   This week we also have a visit from the Software Sensei, Kim Pries!  Kim talks about training in a column titled, “Software Catechism.”

SPaMCAST 520 features our interview with Doc Norton. We talked about his new book Escape Velocity, measurement, and why velocity isn’t generally a good measure for teams. By the time teams get to a point where story point velocity is consistent and predictable, they will have better tools that have fewer negative side effects.

SPaMCAST 519 features our essay on a code of ethics for agile coaches. A code of ethics is a compilation of ethical principles brought together into a framework. I think it is time to discuss a code of ethics for agile coaches. We also have a visit from Susan Parente, with her Not A Scrumdamentalist column.  Susan discusses how to become an agilist. It is not as easy as learning any individual set of methods and techniques.

SPaMCAST 518 features our interview with Rebecca Staton-Reinstein.  We discussed leadership, the difference between leadership and management, coaching versus mentoring and who should own your improvement program.  Rebecca and I have known each other for years and I have always enjoyed her wisdom and pragmatic advice. Rebecca delivers the goods.

SPaMCAST 517 is very different from my original plan.  This week I spoke at ISMA 16 in Sao Paulo, Brazil. The translators were two hours late. The Portuguese speaking speakers were moved earlier so that the conference could get started.  During my wait, I discovered that I could record sessions on my iPhone, therefore, the SPaMCAST 517 is a recording of my talk, titled Product Owners In Agile – The Really Hard Role! Email for a copy of the slides SPaMCASTinfo@gmail.com .  

SPaMCAST 516 features our interview with Nishi Grover Garg.  Nishi and I started by discussing the major differences in agile and non-agile testing and ended with a discussion of agile pods. This is a wonderfully idea-rich interview.