Software Process and Measurement Cast

This week Susan Parente and I had an extraordinary conversation about team leads in agile and leadership. In some cases, the role of a team leader is treated as if it were superfluous to requirements in other cases it is a tool to delegate work to people in an effort to subvert self-organization and when organizations get it right the role is a vehicle to unlocking the capabilities of teams. Contact Susan at parente.s3@gmail.com or on LinkedIn at linkedin.com/in/susanparente Re-read Saturday News Week 3 of our re-read of Why Limit WIP: We Are Drowning In Work by Jim Benson talks about the thrill of getting things done. People with a lot of WIP look for more work, things they can grab and complete to feel good about themselves. I am as guilty as anyone else. Sometimes when items on my shortlist get stuck instead of breaking the items down into smaller chunks to progress the work I will grab a less valuable task and just do it so I can check something off. Susan Parente, who you just heard from in one of her great "Not A Scrumdamentalist" podcast columns described the same scenario. Remember to buy a copy and read along. Amazon Affiliate LInk: https://amzn.to/36Rq3p5 Previous Entries Week 1: Preface, Foreword, Introduction, and Logistics – https://bit.ly/3iDezbp Week 2: Processing and Memory – https://bit.ly/3qYR4yg Week 3: Completion - https://bit.ly/3usMiLm Upcoming Events: Free Webinar When Prioritization Goes Bad https://www.greatpro.org/Webinar-Live-Register?id=1954 April 19, 2022 11 AM EDT to 1230 EDT Special Call to Action If you are a team lead I need your help! I believe the TL role is the least understood and least talked about in agile. It is time to change that. I am working on testing a model of TL behaviors in agile. I need examples of REAL TL job descriptions to map into the model. The glittering generalities that you find on the web don't match what really happens in the real world. I do not need anything sensitive like salary or product details. I will happily share the first cut of the model with anyone that helps and sponsor a virtual meeting to discuss the model with all participants. If you have a TL job description you can share please email me at tcagley@tomcagley.com Next SPaMCAST Next week we will feature our interview with Matthew Stibbe. Matt and I discussed how leadership (or the lack thereof) contributes to projects in wide a range of environments (software and marketing).

This week we talked with Jardena London. We discussed her book Cultivating Transformations - A Leader's Guide to Connecting the Soulful and the Practical. Being soulful sounds fluffy, but isn't. It is critical for delivering lasting change. Jardena is a Business Transformation Consultant, Author, Keynote Speaker, and a Certified Facilitator of Dare to Lead; Brene Brown's groundbreaking training program for organizations based on creating courageous workplaces. Jardena is also the Founder of Souls@Work.org which is focusing on leading a movement to create workplaces that nourish our souls and exude positive energy. Her recent book, "Cultivating Transformations: A Leader's Guide to Connecting the Soulful and the Practical" has been described as "the book you buy and carry around with you everywhere." Her most recent successes have been transforming a large legacy organization into a modern workplace with breakout results. She also speaks at corporate events and on stages worldwide on the positive effects of organizational transformation. Jardena has also served as co-founder and CEO of Rosetta Technology Group since 1997. Websites and Contact Information Cultivatingtransformations.com rosettaagile.com LinkedIn: https://www.linkedin.com/in/jardena/ Upcoming Events: Free Webinar When Prioritization Goes Bad https://www.greatpro.org/Webinar-Live-Register?id=1954 April 19, 2022 11 AM EDT to 1230 EDT Special Call to Action If you are a team lead I need your help! I believe the TL role is the least understood and least talked about in agile. It is time to change that. I am working on testing a model of TL behaviors in agile. I need examples of REAL TL job descriptions to map into the model. The glittering generalities that you find on the web don't match what really happens in the real world. I do not need anything sensitive like salary or product details. I will happily share the first cut of the model with anyone that helps and sponsor a virtual meeting to discuss the model with all participants. If you have TL job description you can share please email me at tcagley@tomcagley.com Next SPaMCAST We are finally going to tackle the difference between prioritization and sequencing. Sequencing is the forgotten cousin of prioritization, HOWEVER, just because you know the priority isn't enough because if you don't get the order right value will be lost. We will also have a visit from Susan "Not A Scrumdamentalist" Parente.

We began the Re-Read Saturday feature in 2014 with a re-read of John Kotter's classic Leading Change. The list of books we have re-read is quite long -- I am going to have to create a list. All that said, last week a person that regularly comments on the podcast indicated they really did not know what Re-Read Saturday was all about. So today to commemorate spring in the northern hemisphere (and the fact that it snowed) and the kick-off of the latest re-read (Why Limit WIP by Jim Benson) I am going to share an audio version of this week's entry. As we always say, buy a copy of the book and read Jim Benson's Why Limit WiP (buy a copy using our Amazon Affiliate link https://amzn.to/3u6Feml get reading) along with us. The written version: https://bit.ly/3iDezbp This week we also have a visit from Jeremy Berriault, who brings his QA Corner to the podcast. Jeremy and I explored the difference between relative and absolute time. Upcoming Events: Free Webinar When Prioritization Goes Bad https://www.greatpro.org/Webinar-Live-Register?id=1954 April 19, 2022 11 AM EDT to 1230 EDT Next SPaMCAST Next week we will talk with Jardena London. We will discuss her book Cultivating Transformations - A Leader's Guide to Connecting the Soulful and the Practical. We will also explore why being soulful in the workplace is critical for facilitating change.

This week we talk to Julianna Lamb, co-founder and CTO at Stytch about agile in start-ups, hybrid working, how to keep a product backlog under control, grow a business in the early 2020's, and more. Julianna is the Co-Founder and CTO of Stytch, a platform for user infrastructure and passwordless authentication. She was previously a software engineer at Strava and Plaid and an early product hire at Very Good Security. Originally from Idaho, Julianna studied computer science and history at Stanford. A former professional figure skater, she started racing triathlons in college and is now an Ironman triathlete. Contact Data: Website: https://stytch.com/ Twitter: juliannaelamb LinkedIn: linkedin.com/in/juliannaelamb Re-Read Saturday News Today we complete our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick touching on the Conclusion, Further Resources, and our concluding notes. Next week we will begin re-reading Jim Benson's Why Limit WiP (buy a copy using our Amazon Affiliate link https://amzn.to/3u6Feml get reading) as we run a poll to select the next of books for the series. Agile Conversations: https://amzn.to/3vEjr55 Previous Installments: Week 1: Logistics and Introduction - https://bit.ly/3EZspxT Week 2: Escaping The Software Factory - https://bit.ly/3HIlivg Week 3: Improving Your Conversations - https://bit.ly/3ty0nYe Week 4: The Trust Conversation - https://bit.ly/3ApUrSk Week 5 The Fear Conversation (Part 1) - https://bit.ly/3gahSpt Week 6 The Fear Conversation (Part 2) - https://bit.ly/34lLON4 Week 7 The Why Conversation (Part 1) - https://bit.ly/3Jg6KE2 Week 8 The Why Conversation (Part 2) – https://bit.ly/34YAsPc Week 9 The Commitment Conversation - https://bit.ly/3pmaooj Week 10 The Accountability Conversation - https://bit.ly/3KCJXD1 Week 11 Conclusion and More - https://bit.ly/3wlGSn8 Next SPaMCAST Next week, are sequencing and prioritization different sides to the same coin or are they different coins entirely. Is a keystone topic when wrestling with work entry. We will also have a visit from Jeremy Berriault and the QA Corner.

Organizational design often collides with getting work done; generating friction that causes all manner of problems. No one goes out of their way to make things difficult, however poor operating metaphors and one size fits all solutions are never optimal. There is a way for agile and team leaders to coexist, but can you take that path? Also this week, Jon M Quigley and his Alpha and Omega of Product Development column make time for the cast. In this installment, we talk about time (including a few time-related puns). Re-Read Saturday News The accountability conversation is the fifth and last conversation addressed in our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick. In Chapter 7 the authors define accountability as "being obligated to render an account of what you have done and why." Next week we will cover the conclusions and some final thoughts. Then we will have a quick interlude re-reading Jim Benson's Why Limit WiP while we run a poll to select the next books. https://amzn.to/3vEjr55 Week 1: Logistics and Introduction - https://bit.ly/3EZspxT Week 2: Escaping The Software Factory - https://bit.ly/3HIlivg Week 3: Improving Your Conversations - https://bit.ly/3ty0nYe Week 4: The Trust Conversation - https://bit.ly/3ApUrSk Week 5 The Fear Conversation (Part 1) - https://bit.ly/3gahSpt Week 6 The Fear Conversation (Part 2) - https://bit.ly/34lLON4 Week 7 The Why Conversation (Part 1) - https://bit.ly/3Jg6KE2 Week 8 The Why Conversation (Part 2) – https://bit.ly/34YAsPc Week 9 The Commitment Conversation - https://bit.ly/3pmaooj Week 10 The Accountability Conversation - https://bit.ly/3KCJXD1 Next SPaMCAST Next week, Julianna Lamb, co-founder and CTO at STYTCH. We talked agile, start-ups, security, and more.

Today we speak with Prateek Joshi. Prateek and I talked about the definition of AI, machine learning, and an approach to using AI in the real world. AI is in your future and it won't be the Matrix or Skywarn (or will it). Prateek Joshi is the founder of Plutoshift and a published author of 13 books on AI. He has been featured in publications such as Forbes, CNBC, TechCrunch, and Bloomberg. You can visit www.prateekj.com to learn more about him. Plutoshift: https://plutoshift.com/ Re-Read Saturday News We had a bit of home repair this week and I did not get the Week 10 of our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick completed (thanks to Laurie and Todd for use of their condo). We will be back next week. Buy a copy now! https://amzn.to/3vEjr55 Week 1: Logistics and Introduction - https://bit.ly/3EZspxT Week 2: Escaping The Software Factory - https://bit.ly/3HIlivg Week 3: Improving Your Conversations - https://bit.ly/3ty0nYe Week 4: The Trust Conversation - https://bit.ly/3ApUrSk Week 5 The Fear Conversation (Part 1) - https://bit.ly/3gahSpt Week 6 The Fear Conversation (Part 2) - https://bit.ly/34lLON4 Week 7 The Why Conversation (Part 1) - https://bit.ly/3Jg6KE2 Week 8 The Why Conversation (Part 2) – https://bit.ly/34YAsPc Week 9 The Commitment Conversation - https://bit.ly/3pmaooj Next SPaMCAST Next week, we revisit the role of the team lead and the concept of self-organizing teams. Can they co-exist? We will also have a visit from Jon M Quigley who brings his Alpha and Omega of Product Development column to the podcast.

In SPaMCAST 692 we discuss Process Improvement as a phrase or perhaps even a mantra. Uttering the phrase evokes all sorts of baggage and cognitive biases that affect behaviors, not always for the better. What are the listeners of the Software Process and Measurement Cast to do? We also have a visit from Tony TImbol who brings his "To Tell A Story" column to the Podcast. We dive headlong into the tangled world of user stories and agile requirements. Tony also announces his new ebook on agile requirements. Get your own copy! https://bit.ly/3plyiAu Re-Read Saturday News Week 9 of our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick is about commitment. Over the years I have observed that there are some people who are very committed to adopting a new way of working, some people that pay lip service, and others who flat-out resist. This is obviously a continuum. Update on last week's experiment: I was not able to leverage the concepts of joint design directly. I did use coherence busting techniques again (we are back to situational context). I am going to try again this week and I am also going to experiment with calculating the ratio of defined important words to total important words in conversations that people are trying to generate commitment. Amazon Affiliate Link https://amzn.to/3vEjr55 Week 1: Logistics and Introduction - https://bit.ly/3EZspxT Week 2: Escaping The Software Factory - https://bit.ly/3HIlivg Week 3: Improving Your Conversations - https://bit.ly/3ty0nYe Week 4: The Trust Conversation - https://bit.ly/3ApUrSk Week 5 The Fear Conversation (Part 1) - https://bit.ly/3gahSpt Week 6 The Fear Conversation (Part 2) - https://bit.ly/34lLON4 Week 7 The Why Conversation (Part 1) - https://bit.ly/3Jg6KE2 Week 8 The Why Conversation (Part 2) – https://bit.ly/34YAsPc Week 9 The Commitment Conversation - https://bit.ly/3pmaooj Next SPaMCAST More AI with a conversation with Prateek Joshi. Mr. Joshi and I talked about the definition of AI, machine learning, and how to test AI (this was just the tip of the iceberg). AI is in your future and it won't be the Matrix or Skywarn (or will it).

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. LinkedIn linkedin.com/in/kevin-mckeel-2457235 Website: logapps.com 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). https://amzn.to/3vEjr55 Week 1: Logistics and Introduction - https://bit.ly/3EZspxT Week 2: Escaping The Software Factory - https://bit.ly/3HIlivg Week 3: Improving Your Conversations - https://bit.ly/3ty0nYe Week 4: The Trust Conversation - https://bit.ly/3ApUrSk Week 5 The Fear Conversation (Part 1) - https://bit.ly/3gahSpt Week 6 The Fear Conversation (Part 2) - https://bit.ly/34lLON4 Week 7 The Why Conversation (Part 1) - https://bit.ly/3Jg6KE2 Week 8 The Why Conversation (Part 2) - https://bit.ly/34YAsPc Next SPaMCAST 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.

This week we revisit the age-old statements, "I don't want to be measured" and its alter ego, "management will use metrics against me." While often stated as if they are questions, both are positions. We weave in two recent techniques from our Re-read of Agile Conversations to consider the interests behind the statements Also, Jeremy Berriault weighs in on the need for testing strategies in agile on this edition of this QA Corner. Re-Read Saturday News Week 7 of our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick begins Chapter 5 addressing the 'Why Conversation'. Like the 'Fear Conversation', we will approach this in two parts; focusing this week on two areas, positions and interests, and inquiry and advocacy. We will tackle joint design next week. My experiment of the week: I set out to create a fear matrix – that sounds like a movie title. I failed, BUT more importantly, I was able to use the fear matrix approach as a structure for a retrospective. It worked well. The idea of exposing and mitigating fears shifted perspectives nicely. Interestingly, what was hard was tying the fears and mitigations to an espoused norm. In conversations afterward, it became apparent that it is hard to admit that your behavior is or was at odds with the norms of the team and organization. It will be worth another conversation to make sure the link is clear. Next week, I am going to explore building a position-interest chart. https://amzn.to/3vEjr55 Week 1: Logistics and Introduction - https://bit.ly/3EZspxT Week 2: Escaping The Software Factory - https://bit.ly/3HIlivg Week 3: Improving Your Conversations - https://bit.ly/3ty0nYe Week 4: The Trust Conversation - https://bit.ly/3ApUrSk Week 5 The Fear Conversation (Part 1) - https://bit.ly/3gahSpt Week 6 The Fear Conversation (Part 2) - https://bit.ly/34lLON4 Week 7 The Why Conversation (Part 1) - https://bit.ly/3Jg6KE2 Next SPaMCAST Next week Kevin McKeel will visit the SPaMCAST to talk about AI and software estimation tools. Is this the end of the world for the software estimating profession or the beginning of a golden age?

Prabhjot Singh and I talk about AI using AI to improve the flow of work and the delivery of value. AI, however you define it, is in your future. You need to be ready! Mr. Singh's bio: Prabhjot Singh is a serial entrepreneur who has started multiple for-profit, social enterprise, and non-profit ventures. He serves as President and CEO of Pyze, the most recent company he founded to enable the world's largest enterprises to improve business operations through AI-driven Process Intelligence and Analytics. He has over 20 years of experience in sales, marketing, and product management. He previously co-founded Pixatel Systems, a social enterprise that utilizes mobile computing to deploy apps and e-Learning solutions to millions of users. LinkedIn: linkedin.com/in/psinghsf Twitter: https://twitter.com/psinghSF Company Website: https://www.pyze.com/ Re-Read Saturday News Week 6 of our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick continues on Chapter 4: The Fear Conversation. We discussed two of the three major concepts in Chapter 4 last week, but we did not consider the fear conversation and more specifically the fear chart. Many years ago I worked with a manager, Rich Hisrich at BancSystems/EDS. I was the QA manager at the site. It was through my interaction with RIch that I learned the value of whiteboards and visualization. The fear chart is a visualization tool I can see having great value. My experiment of the week: I am going to double down and commit to creating a fear chart. Whether an opportunity for a fear conversation presents itself, we shall see. https://amzn.to/3vEjr55 Week 1: Logistics and Introduction - https://bit.ly/3EZspxT Week 2: Escaping The Software Factory - https://bit.ly/3HIlivg Week 3: Improving Your Conversations - https://bit.ly/3ty0nYe Week 4: The Trust Conversation - https://bit.ly/3ApUrSk Week 5 The Fear Conversation (Part 1) - https://bit.ly/3gahSpt Week 6 The Fear Conversation (Part 2) - https://bit.ly/34lLON4 Next SPaMCAST Next week we continue an essay refining how we are using Flow Metrics in 2022 to … manage flow (surprise) rather than micromanaging tasks or kidding ourselves with relative sizing techniques. We will also have a visit from Jeremy Berriault and his QA Corner.