Nov 18, 2018
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. User stories are a core tenet for most agile approaches and have a lot of value.
This week we also have a visit from the Software Sensei, Kim Pries! Kim talks about training in a column titled, “Software Catechism.”
Can you help keep the podcast growing? Here are some ideas:
Whether you do one or all six, being here is a big deal to everyone that helps get the podcast and blog together. Thank you!
Re-Read Saturday News
The Software Process and Measurement Cast and Blog crew is on the road this weekend so we are going to take a day off from our re-read of Bad Blood, Secrets and Lies in a Silicon Valley Startup by John Carreyrou (published by Alfred A. Knopf, 2018 – Buy a copy and read along!) Today we re-visit an entry from 2013, In 2013 we ran a series titled “Motivational Sunday”. In this entry, we talked about the relationship between commitment and habits. I have tweaked the works a little but the sentiments are no different.
SPaMCAST 522 features the return of Jeff Anderson. Jeff returns to discuss getting to a minimum viable product. Many teams and organizations struggle with the concepts of an MVP, Jeff provides three ways to get to an MVP without going crazy!