Software Process and Measurement Cast

Continuous improvement through inspecting and adapting is a core tenant of an agile mindset, which dovetails well with every executive's need to deliver the most value possible. Measurement is an important tool to help teams and organizations ask the right questions at the right time. Flow metrics, not burndowns and velocity, need to be a big part of any IT organization's approach to measurement. We also have a visit from Jon M Quigley who brings his Alpha and Omega of Product Development column to the podcast. Jon discusses the complicated relationship between time, work entry, and promises. Have you checked out The Open Transformation Playbooks Martin Foster discussed last week? If not, you are missing something important. https://transformationplaybooks.org/ The Open Transformation Playbooks is an initiative to build an open, remixable, body of knowledge for agile organizational transformation. Re-Read Saturday News Week 5 of our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick tackles Chapter 4: The Fear Conversation. Fear has a significant impact on what we think and how we behave. The changes that fear drives don't stop at the individual, the behavior changes ripple through organizations. My experiment of the week: Update on last week's experiment. I was able to use some of the ideas from the trust conversation this week. I actually used the statement, "the story I am telling myself is . . ." in a real conversation twice. The first time it felt contrived; it is much easier to state something as fact than to admit it might not be true. For both conversations, I had created a conversation analysis sheet to record the conversation. I need conversation analysis practice. Also, both conversations would have gone better with a copy of the trust ladder close at hand. This week's experiment. I would like to try to generate a fear chart and have a fear conversation. I am still considering what type of job aids will be most useful. 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 Next SPaMCAST Next week Prabhjot Singh and I talk about AI. If you are a developer or entrepreneur, AI (however you define it) is in your future. You need to be ready! Mr. 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. Continuous improvement through inspecting and adapting is a core tenant of an agile mindset, which dovetails well with every executive's need to deliver the most value possible. Measurement is an important tool to help teams and organizations ask the right questions at the right time. Flow metrics, not burndowns and velocity, need to be a big part of any IT organization's approach to measurement. We also have a visit from Jon M Quigley who brings his Alpha and Omega of Product Development column to the podcast. Jon discusses the complicated relationship between time, work entry, and promises. Have you checked out The Open Transformation Playbooks Martin Foster discussed last week? If not, you are missing something important. https://transformationplaybooks.org/ The Open Transformation Playbooks is an initiative to build an open, remixable, body of knowledge for agile organizational transformation. Re-Read Saturday News Week 5 of our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick tackles Chapter 4: The Fear Conversation. Fear has a significant impact on what we think and how we behave. The changes that fear drives don't stop at the individual, the behavior changes ripple through organizations. My experiment of the week: Update on last week's experiment. I was able to use some of the ideas from the trust conversation this week. I actually used the statement, "the story I am telling myself is . . ." in a real conversation twice. The first time it felt contrived; it is much easier to state something as fact than to admit it might not be true. For both conversations, I had created a conversation analysis sheet to record the conversation. I need conversation analysis practice. Also, both conversations would have gone better with a copy of the trust ladder close at hand. This week's experiment. I would like to try to generate a fear chart and have a fear conversation. I am still considering what type of job aids will be most useful. 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 Next SPaMCAST Next week Prabhjot Singh and I talk about AI. If you are a developer or entrepreneur, AI (however you define it) is in your future. You need to be ready! Mr. 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.

Today we begin Year 16 with an interview, discussion, conversation -- call it what you like -- with Martin Foster. We covered a ton of ground, including whether the goal of any organization should be to be more agile and the 2021 Business Agility Report. During one segment we discussed the statement, "the impediments are the path." A wonderful and thought-provoking start to Year 16! ANNOUNCING: The Open Transformation Playbooks: https://transformationplaybooks.org/ A (very new) initiative to build an open, remixable, body of knowledge for agile organizational transformation. To accompany this episode Martin and TeamForm have launched the first tranche of content. Martin's Contact Information: 2021 Business Agility Report: https://bit.ly/3GXfzBJ TeamForm: https://www.teamform.co/ Email: martin@orchestrated.io LinkedIn: linkedin.com/in/martinfoster Martin's Bio Martin is a senior consultant at TeamForm. His passion is working with organizations that are transforming themselves to cross-functional team structures, with all the nuances, benefits, and challenges that this brings. With his past experience as a product owner and engineer, he enjoys bringing data into the people conversation. Re-Read Saturday News Week 4 of our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick tackles Chapter 3: The Trust Conversation. Trust is a requirement for people to work together toward a common goal. Misters Squirrel and Fredrick define trust as aligned stories. My experiment of the week: First an update on my experiment from last week. I found that I need to create a job aid for conversational analysis in order to practice the R's from Chapter 2. I must admit that not preparing for conversational analysis creates a scenario where I am looking back and trying to remember conversations, which makes them more susceptible to bias. This week I am going to create a job aid for trust conversations, then find two or three scenarios to practice. Practice will include the R's from Chapter 2. 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 Next SPaMCAST Next week our first essay of Year 16 with thoughts on flow metrics and why focusing on flow is powerful, important, and causes people to run around like their hair is on fire. Hopefully, we can dampen the blaze down a bit.

Today marks the end of year 15 on the Software Process and Measurement Cast, and we are closing the year with pitchfork and torches. We discussed the world of knowledge work in 2022. Leadership, principles, value, and values take center stage. Panels like this make me want to do panels every week! The panelists (other than myself) are: Jeremy Berriault https://www.linkedin.com/in/jeremy-berriault-mba/ Web: https://berriaultandassociates.com/ Jon M Quigley linkedin.com/in/jonmquigley Web: https://www.valuetransform.com/product-development-tools/ Kevin Rush linkedin.com/in/kezrush Twitter: @Kezrush Chris Hurney linkedin.com/in/chrishurney Web: https://www.inspiradoconsulting.com/ Twitter: chris_hurney Participating in spirit (they were on part one last week) Susan Parente Susan Parente linkedin.com/in/susanparente Twitter: @TechRiskManager Jeremy Willets linkedin.com/in/jeremywillets Blog: https://www.jeremywillets.com/ Re-Read Saturday News Week 3 of our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick tackles Chapter 2, Improving Your Conversations. Chapter 2 begins the heavy lifting of improving conversations. This is a chapter I strongly suggest reading at least twice while you are putting the ideas into practice. The authors spend the first part of the chapter building a case for why conversations are so powerful. The authors state that through conversation "we are able to create and believe in shared fictions." There is a ton to think about and practice! My experiment of the week: First an update on my conversation experiment from last week. Last week I wanted to review my conversations to determine if I was correctly assessing scenarios using the Cynefin Framework. There was at least one conversation where I misjudged the complexity. Whereas the participants viewed the scenario being discussed to be complicated (the solution being a framework or best practices), I viewed the scenario as complex or possibly chaotic. The differences in mental models made the conversation tense and ungratifying. In my mind, my failure was not recognizing the issue until I was reviewing the conversation after the fact (one of the Four Rs in Chapter 2). I think a better approach, for me, will be to assess the complexity of the scenario before the conversion in the future. Perhaps a form of conversational premortem. This week I am going to use the conversational analysis process on two or three different types of hard conversations – my weeks are always interesting. One of the areas I am interested in contemplating is whether different kinds of conversations have different question ratios. 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 Next SPaMCAST Next week we have an interview with Martin Foster. Mr. Foster and I wrestle with the question, "Why don't most agile transformations deliver tangible business value?" A valuable start to year 16 and 2022!

One of the fun parts of programming the Software Process and Measurement Cast is getting diverse groups of people together to chat. In this edition of the podcast, Jon M Quigley, Jeremy Willets, Jeremy Berriault, Kevin Rush, Susan Parente, and myself convened to discuss what we learned about work in 2021. The last few years have been extraordinary -- both good and bad. When you live in times like these it is incumbent on all of us to learn from them. The panelists (other than myself) are: Jeremy Berriault https://www.linkedin.com/in/jeremy-berriault-mba/ Web: https://berriaultandassociates.com/ Susan Parente linkedin.com/in/susanparente Web: http://www.s3-tec.com/ Jon M Quigley linkedin.com/in/jonmquigley Web: https://www.valuetransform.com/product-development-tools/ Kevin Rush linkedin.com/in/kezrush Twitter: @Kezrush Jeremy Willets linkedin.com/in/jeremywillets Blog: https://www.jeremywillets.com/ Re-Read Saturday News Week 2 of our re-read of Agile Conversations by Douglas Squirrel and Jeffrey Fredrick tackles Chapter 1, Escaping the Software Factory. The idea that software development and maintenance fit a factory model in which people are fungible and that processes are deterministic is a thing in 2021 (as it was when this book was written). I have always been hard-pressed to buy the factory/manufacturing model. I have worked on an assembly line. One of the jobs I had was building tires for Firestone Tire and Rubber Company at their plant in Memphis. That job was one of the reasons I made sure I went to university. Whether the assembly line model was truly appropriate even for tire manufacturing would be interesting to debate (the plant is gone, no amount of scientific management could save it). At the very least, software development and maintenance are better served by team-based collaborative approaches. Words like team-based and collaboration require communication (something that did not happen on the assembly line, except when we had union meetings) so that rigid processes and micromanagement can be minimized. My experiment of the week: I originally planned to begin experimenting with the ideas from Agile Conversations with Chapter 2; however, Chapter 1 reminded me of the need to take a mindset-centered approach to change and to incorporate the ideas from Cynefin. I will review my decisions this week to assess whether I am getting lazy and assuming that situations are more deterministic than complex, and therefore not putting myself in the right place to collaborate. https://amzn.to/3vEjr55 (Affiliate Link) Week 1: Logistics and Introduction - https://bit.ly/3EZspxT Week 2: Escaping The Software Factory - https://bit.ly/3HIlivg Next SPaMCAST Next week features a second panel discussion with some of the same people (and a new mixer) with a focus on hopes and aspirations for 2022 and beyond. Next week will spike the ball on year 15 of the Software Process and Measurement Cast.

SPaMCAST 684 posts on January 2nd, 2022. The new year evokes both retrospection and expectations for the future. 2021 was quite the year; SPaMCAST 635 marked the beginning of our 15th year of publishing with a conversation with Johanna Rothman (SPaMCAST 635 - Practical Ways to Manage, A Conversation with Johanna Rothman). That was our most downloaded cast of 2021. In late August I lost a podcast . . . (a summer rerun), SPaMCAST 668 has attained the status of the Lost Show. Somehow while I was backpacking on Isle Royale the preprogrammed show failed to post. I have a backup but it is more fun to have a lost cast. I will rectify the situation at some point when I stop being amused. The year ended with my 12-year-old mixer going to the electronics recycler. The new mixer should be delivered soon. Even with all of the hassle, I have been able to do three great interviews and two related panel discussions that will round out year 15 and kick-off year 16. That's the long way to say that even though I am struggling through a website issue and a switchover of hardware, I am currently planning years 16 and 17. Happy New Year, and now back to our regularly scheduled programming with Tony Timbol and his To Tell A Story column. This installment tackles product owners and work entry. Re-Read Saturday News Starting a re-read is a great way to start the new year. Today we start into Agile Conversations by Douglas Squirrel and Jeffrey Fredrick by charting the predicted course of the re-read and touching on the introduction. The version of the book I am reading is the paperback version copyrighted 2020 by IT Revolution. The book consists of an introduction, seven numbered chapters, a conclusion, and 20 pages of end matter. All of this is over 223 pages. It is my intent to cover this book over 9 weeks using the chapters as pacing. This book has similarities with Monotasking by Staffan Nöteberg in that this book demands action. Therefore like that re-read, as we get to chapter 2 I will begin identifying how I will experiment with the knowledge each chapter delivers. As I have discovered over the years reading technical and self-improvement books, if you do not experiment with ideas they fade quickly regardless of their value. https://amzn.to/3vEjr55 Week 1: Logistics and Introduction - Next SPaMCAST Next week features part 1 of a 2 part panel discussion (both parts have slightly different participants), discussing the world of knowledge work circa 2021 and pontifications about the shape of work in 2022.

Ben Woznicki and I talk about the book and ideas inside the covers of Team Topologies. Ben provides a great deal of advice on creating teams that are fit for purpose. Ben and I have worked together, hosted a video podcast together, and more -- it is a great conversation. Ben is an Organizational Health Coach: Helping you deliver sooner, with higher confidence, and more consistency. Ben has 10 years of experience with all facets of technical and business agility and organizational transformation. He collaborates with, trains, mentors, and coaches at all levels to smooth the transition to Lean and Agile ways of delivering value. And aligns transformation efforts to organizational objectives so everyone is on the same page. Contact InformationLinkedIn: https://www.linkedin.com/in/benwoz/ Email: b@benwoz.com Re-Read Saturday News We have just completed our re-read of Project to Product ( https://amzn.to/2WzvPac - Amazon Affiliate link). Next week we begin our re-read of Agile Conversations: Transform Your Conversations, Transform Your Culture – https://amzn.to/3sfK55q (affiliate link). Catch up on previous installments: Week 1: Foreword and Introduction - https://bit.ly/39gIt0A Week 2: Age of Software - https://bit.ly/2XYvqyI Week 3: From Project to Product - https://bit.ly/3mhwJBb Week 4: Introducing The Flow Framework - https://bit.ly/3lqJTwd Week 5: Capturing Flow Metrics - https://bit.ly/3GjCffC Week 6: Connecting to Business Results - https://bit.ly/3BTROqQ Week 7: Tracking Disruptions -https://bit.ly/3neIs5h Week 8: The Ground Truth of Enterprise Tool Networks - https://bit.ly/3DHO5OU Week 9: Specialized Tools and the Value Stream - https://bit.ly/332OuhC Week 10:Value Stream Management - https://bit.ly/3ESfhv2 Week 11: The Conclusion - https://bit.ly/3e5d83c Next SPaMCAST Next week we begin 2022 with a reflection on the economic rationale for breaking work down into smaller pieces. We will also have a visit from Tony Timbol and his To Tell A Story Column.

At the end of the year, planning and prioritization take center stage. We can only really prioritize work, needs, and dreams that are within our span of control. That does not stop people from trying to prioritize work that is not theirs to prioritize. We also have a visit from Susan Parente who brings her I'm Not A Scrumdamentalist column to the cast. This month we talk about getting leadership right. It is possible! Re-Read Saturday News As 2021 comes to a close we bring our re-read of Project to Product to a close as well (buy a copy and dive into the book https://amzn.to/2WzvPac - Amazon Affiliate link). The conclusion of the book brings the discussion back as a reflection on the turning point of the Age of Software. Catch up on previous installments: Week 1: Foreword and Introduction - https://bit.ly/39gIt0A Week 2: Age of Software - https://bit.ly/2XYvqyI Week 3: From Project to Product - https://bit.ly/3mhwJBb Week 4: Introducing The Flow Framework - https://bit.ly/3lqJTwd Week 5: Capturing Flow Metrics - https://bit.ly/3GjCffC Week 6: Connecting to Business Results - https://bit.ly/3BTROqQ Week 7: Tracking Disruptions -https://bit.ly/3neIs5h Week 8: The Ground Truth of Enterprise Tool Networks - https://bit.ly/3DHO5OU Week 9: Specialized Tools and the Value Stream - https://bit.ly/332OuhC Week 10:Value Stream Management - https://bit.ly/3ESfhv2 Week 11: The Conclusion - https://bit.ly/3e5d83c Next SPaMCAST Next week, we will have a special show. Ben Wozniki and I talked about team topologies (the idea and the book). Ben and I have worked together, hosted a video podcast together, and more -- this was more of a conversation than an interview.

This week we touch on a topic that is near and dear to my heart, work entry, with an essay titled Prioritization Without Control of Work Entry. I am tempted to suggest that without control over what you can say yes to, the whole idea of prioritization is a farce. The answer is more complicated, but only a little. We also have a visit from Jeremy Berriault who brings his QA Corner to the cast. This week we discuss measuring testing -- it is more than just pass/fail. Re-Read Saturday News Chapter 9 of Project to Product (buy a copy and re-read the book with us https://amzn.to/2WzvPac Amazon Affiliate Link) ties the three layers of the author's model together and exposes the third epiphany from his visit to the BMW plant that has been the central plot element of the book. The chapter puts all the parts together. But instead of relating how he connects the infrastructure, I want to focus on how important it is to generate an end-to-end view of work for any software-intensive product. Catch up on previous installments: Week 1: Foreword and Introduction - https://bit.ly/39gIt0A Week 2: Age of Software - https://bit.ly/2XYvqyI Week 3: From Project to Product - https://bit.ly/3mhwJBb Week 4: Introducing The Flow Framework - https://bit.ly/3lqJTwd Week 5: Capturing Flow Metrics - https://bit.ly/3GjCffC Week 6: Connecting to Business Results - https://bit.ly/3BTROqQ Week 7: Tracking Disruptions -https://bit.ly/3neIs5h Week 8: The Ground Truth of Enterprise Tool Networks - https://bit.ly/3DHO5OU Week 9: Specialized Tools and the Value Stream - https://bit.ly/332OuhC Week 10:Value Stream Management - https://bit.ly/3ESfhv2 Next SPaMCAST Next week, more on work entry and prioritization (it is at the top of my priority list unless I don't have control over my work entry). We will also spend time with Susan Parente and her I Not A Scrumdamentalist column.

This week Mauricio Aguiar and Christine Green join me to discuss the state and future of Software Measurement. Mauricio, Christine, and I are all recent Past Presidents of the International Function Point Users Group (the largest international software measurement association). The conversation is both provocative and enlightening. Note, the audio of my voice is a little muffled but the important parts of the conversation come from Christine's and Mauricio's lips. I know what the issue was and have added a step to my interview checklist. Bios Mauricio Aguiar is the founder of TI Metricas, a leading software measurement company based in Brazil. He holds a bachelor's degree in Engineering from the Federal University of Rio de Janeiro. Mauricio was elected President of the International Function Point Users Group (IFPUG) for 2005-2007 and also for 2017-2019, after serving on the IFPUG Board since 2000. Mauricio was involved with the implementation of function point analysis and metrics programs in many Brazilian and multinational organizations. As a second career, he now does pro-bono work as a hypnotherapist. Christine is the founder of IP by Green, senior consultant, and past president of IFPUG. Re-Read Saturday News This week, Chapter 8 of Project to Product https://amzn.to/2WzvPac (Amazon Affiliate Link). The chapter is titled Specialized Tools and the Value Stream. I was presented with a scenario this week in which product, UX, development, testing, and security operated within their own boundaries with their own goals and tools — silos. Chapter 8 has something to say about the impact of silos. Catch up on previous installments: Week 1: Foreword and Introduction - https://bit.ly/39gIt0A Week 2: Age of Software - https://bit.ly/2XYvqyI Week 3: From Project to Product - https://bit.ly/3mhwJBb Week 4: Introducing The Flow Framework - https://bit.ly/3lqJTwd Week 5: Capturing Flow Metrics - https://bit.ly/3GjCffC Week 6: Connecting to Business Results - https://bit.ly/3BTROqQ Week 7: Tracking Disruptions -https://bit.ly/3neIs5h Week 8: The Ground Truth of Enterprise Tool Networks - https://bit.ly/3DHO5OU Week 9: Specialized Tools and the Value Stream - https://bit.ly/332OuhC Next SPaMCAST Next week we will continue our exploration of the team lead's role in agile frameworks. As with anything that involves humans and hierarchies the role is not straightforward. We will also return to the QA Corner to visit Jeremy Berriault

As we begin counting down to the end of the year, I would like to consider the team lead's role. It is a nearly ubiquitous role in organizations, but is almost never talked about in agile frameworks. We begin our journey into the role by establishing three examples to help understand how the role is practiced and why it can generate friction if not addressed when adopting frameworks. We also have a visit from Jon M Quigley who brings his Alpha and Omega of Product Development column to the cast. This week we talk about the idea of descoping and its role in work entry. Done early, descoping is a tool while done after you have made commitments it makes a tool out of you. Re-Read Saturday News Nearly 30 hours of driving, Thanksgiving, and far too few hours with a large part of my extended family kept me from completing the re-read of Chapter 8 of Project to Product https://amzn.to/2WzvPac (Amazon Affiliate Link). We will be back next week to talk about the problems caused by role and tool disconnection across the value chain (silos). Catch up on previous installments: Week 1: Foreword and Introduction - https://bit.ly/39gIt0A Week 2: Age of Software - https://bit.ly/2XYvqyI Week 3: From Project to Product - https://bit.ly/3mhwJBb Week 4: Introducing The Flow Framework - https://bit.ly/3lqJTwd Week 5: Capturing Flow Metrics - https://bit.ly/3GjCffC Week 6: Connecting to Business Results - https://bit.ly/3BTROqQ Week 7: Tracking Disruptions -https://bit.ly/3neIs5h Week 8: The Ground Truth of Enterprise Tool Networks - https://bit.ly/3DHO5OU Next SPaMCAST Next week Mauricio Aguliar and Christine Green join me to discuss the state and future of Software Measurement. Mauricio, Christine, and I are all recent Past Presidents of the International Function Point Users Group (the largest international software measurement association). The conversation will be provocative and enlightening.