Software Process and Measurement Cast

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 Web:   Jon M Quigley Web: https://www.valuetransform.com/product-development-tools/ Kevin Rush Twitter: @ Chris Hurney Web: Twitter: Participating in spirit (they were on part one last week) Susan Parente Susan Parente   Twitter: @TechRiskManager Jeremy Willets   Blog:     Re-Read Saturday News  Week 3 of our re-read of  tackles s. 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.      Week 1: -   Week 2: -   Week 3: -     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 Web:   Susan Parente Web: http://www.s3-tec.com/ Jon M Quigley Web: https://www.valuetransform.com/product-development-tools/ Kevin Rush Twitter: @ Jeremy Willets   Blog:      Re-Read Saturday News  Week 2 of our re-read of  tackles . 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 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. (Affiliate Link) Week 1: -   Week 2: -     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 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 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.        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 . 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:   Email:    Re-Read Saturday News  We have just completed our re-read of t ( - Amazon Affiliate link). Next week we begin our re-read of  – (affiliate link).  Catch up on previous installments: Week 1: -   Week 2: -   Week 3: -   Week 4: - Week 5: -   Week 6: -   Week 7: -  Week 8: -     Week 9: -   Week 10: -   Week 11: -      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 t to a close as well (buy a copy and dive into the book - 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: -   Week 2: -   Week 3: -   Week 4: - Week 5: -   Week 6: -   Week 7: -  Week 8: -     Week 9: -   Week 10: -   Week 11: -    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 t (buy a copy and re-read the book with us 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: -   Week 2: -   Week 3: -   Week 4: - Week 5: -   Week 6: -   Week 7: -  Week 8: -     Week 9: -   Week 10: -   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 t  (Amazon Affiliate Link). The chapter is titled . 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: -   Week 2: -   Week 3: -   Week 4: - Week 5: -   Week 6: -   Week 7: -  Week 8: -     Week 9: -   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  (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: -   Week 2: -   Week 3: -   Week 4: - Week 5: -   Week 6: -   Week 7: -  Week 8: -       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.

This week we are taking a quick journey into a discussion of prioritization outside of a team or an organization's span of control. It is easy to confuse influence and actually be able to exert control over an outcome.  Wishful thinking often can lead to frustration.  Tony TImbol also brings his “To Tell A Story” column to the cast building on the ideas that are central fro good user stores.  Check out Tony’s Product Owner training events at   This week to talk about the product owner’s role in writing and maintaining user stories.  Re-Read Saturday News  This week we re-read Chapter 7 of Project to Product  (Amazon Affiliate Link). This week we consider Mik’s first two epiphanies and introduce the topic of network value streams.   Catch up on previous installments: Week 1: -   Week 2: -   Week 3: -   Week 4: - Week 5: -   Week 6: -   Week 7: -  Week 8: -     Next SPaMCAST  Next week an essay on the role of the team lead in Scrum. As Mellisa Greller points out, the role of the TL is often overlooked. When a role is overlooked it causes friction. Unless you are starting a campfire, friction is not a great idea.   We will also have a visit from Jon M Quigley (i know I said that last week but this week we recorded the next few Alpha and Omega of Product Development columns).

Today we will speak to Kit Merker, COO of Nobl9 about Service Level Objectives (SLO). Kit provides down-to-earth advice for adopting and using SLOs to benefit teams AND organizations.  Kit’s bio: Kit Merker's 20+ year career spans product management, engineering, evangelism and community-building roles at Google, Microsoft, JFrog, and the governing board of the Cloud Native Computing Foundation (CNCF). He is currently Chief Operating Officer for Nobl9, driving community and growth for service reliability for enterprise development teams. Contact information: (LinkedIn) (Personal Website) (Company Website) @KitMerker (Twitter) Re-Read Saturday News  This week we re-read Chapter 6 of Project to Product  (Amazon Affiliate Link). In the chapter the author tells four stories of disruption -- they are interesting in their own right. Still, if we look for a common thread I would suggest the communication needed to manage the balance between flow items (features, defects, risks, and debts).  Catch up on previous installments: Week 1: -   Week 2: -   Week 3: -   Week 4: - Week 5: -   Week 6: -   Week 8: -    Next SPaMCAST  Next week an essay on the role of the team lead in Scrum. As Mellisa Greller points out, the role of the TL is often overlooked. When a role is overlooked it causes friction. Unless you are starting a campfire, friction is not a great idea.   We will also have a visit from Jon M Quigley.