Software Process and Measurement Cast

Software Process and Measurement Cast 783 tackles a classic work intake problem, “Do you have the authority to ask for this work?” Work input processes need to vet more than just requirements. We also have a visit from Jon M Quigley. Jon and I discussed taking control of your personal growth. It is not your organization's responsibility. Re-Read Saturday News Chapter 10 of is titled, The Red-Blue Operating System. Marquet starts this chapter with the cautionary tale of the Ford Pinto. The chapter highlights the outcome of the industrial approach to leadership going wrong. My wife had a Pinto when we first started dating. It was our only car and we both remember waiting for it to be recalled, even as we drove to work every morning. We discussed the potential of the fuel tank exploding. What we were oblivious to was the reason for the problem. The failure of leadership and the failure of the decision-making model literally sentenced people to death to achieve a goal. Previous installments of our re-read of (buy a copy)! Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: - Week 7: - Week 8: - Week 9: - Week 10: - Week 11: - Learn to Solve IT's Dirtiest Secret! Work input, which includes prioritization and sequencing, is how work gets to an organization or team. If you get it wrong you are throwing time and money away. Simply put, poor work intake means no agile for you. Jeremy Willets and I have written tackling the topic that JRoss Publishing will publish in January 2024. In support of the book, we are building a live, workshop-based course for anyone involved in deciding on what work gets completed! This includes Agile Coaches, Scrum Masters, Product Owners, Project Managers, Program Managers, and Portfolio Managers - lots of people are involved which is part of the problem! The workshop will cover why work intake is the biggest challenge to teams and organizations today. Attendees will also learn what to do to solve this challenge. This cohort-based course will combine very short lectures, discussions, and exercises. It will provide space to learn and share with peers. We’re using a survey to build a waitlist for the first cohort – link below. We will use the list to alert you when the workshop is available. Next SPaMCAST Software Process and Measurement Cast 784 will feature our interview with Michaele Gardner and Brian Hackerson. We talked about Agile Best Self and being in control of our agile.

The Software Process and Measurement Cast 782 features our conversation with Govind Balu on the importance of data and the concept of data transformations. Data represents the gold rush of the 21st Century! Govind Balu is a visionary entrepreneur and experienced executive with a strong background in leveraging data and AI to drive business growth across different industries. As the Founder and CEO of QuaXigma, he spearheads the company’s vision to transform organizations into data-driven enterprises. Govind observed that small and medium businesses struggle to effectively extract value from data and are unable to compete in a landscape where larger organizations more effectively leverage AI. Motivated to make data and AI easily accessible to SMBs, Govind founded QuaXigma with a clear mission to develop and deliver solutions that deliver business value by focusing on innovation, customer satisfaction, and strategic consulting. Govind’s LinkedIn Profile: Email: Company Website: Re-Read Saturday News In Chapter 9 of , Marquet provides several examples of using the new plays. As a reminder, the plays in the new playbook are: Control The Clock Collaborate Commit Complete Improve Connect Each play is powerful; however, the combination of the plays is where the real power is. For example, controlling the clock — calling a pause — allows a person or team time to think. During that pause, if they surface issues that are addressed the post-industrial plays of collaboration and improving are in evidence. Leveraging short iterations so that work can be demonstrated and inspected combines the control the clock, complete, and connect plays. Iterative planning, a hallmark of agile, combines control the clock and commit plays. Use the links below to explore more of the re-read. Previous installments of our re-read of (buy a copy)! Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: - Week 7: - Week 8: - Week 9: - Week 10: - Learn to Solve IT's Dirtiest Secret! Work input, which includes prioritization and sequencing, is how work gets to an organization or team. If you get it wrong you are throwing time and money away. Simply put, poor work intake means no agile for you. Jeremy Willets and I have written tackling the topic that JRoss Publishing will publish in January 2024. In support of the book, we are building a live, workshop-based course for anyone involved in deciding on what work gets completed! This includes Agile Coaches, Scrum Masters, Product Owners, Project Managers, Program Managers, and Portfolio Managers - lots of people are involved which is part of the problem! The workshop will cover why work intake is the biggest challenge to teams and organizations today. Attendees will also learn what to do to solve this challenge. This cohort-based course will combine very short lectures, discussions, and exercises. It will provide space to learn and share with peers. We’re using a survey to build a waitlist for the first cohort – link below. We will use the list to alert you when the workshop is available. Next SPaMCAST Software Process and Measurement Cast 783 will tackle a classic work intake problem, “Did I forget to tell you, the requirements changed?” What happens when you don’t have a clear line to the business to get feedback as you are doing work? Often you get to do things over and over and maybe over again. We will also have a visit from Jeremy Berriault bringing his Evolutionary Agilist Coumn to the cast!

The Software Process and Measurement Cast 781 begins with a discussion of prioritization and sequencing. These two ideas often get conflated. Work might be important but if it has predecessors and successors it will require sequencing. You can’t deploy a new piece of hardware unless you have it. The acquisition of the equipment comes before deployment. Not letting teams control or have input into sequencing has consequences. Let us discuss avoiding those negative outcomes. We also have a visit from Keis Kostaqi who returns with her You Are Not Alone column. Keis and I discuss the new Scrum Master that gets thrown to the wolves. Get a coach or risk being eaten? Re-Read Saturday News Chapter 8 is titled, The Enabling Play: Connect. This Chapter begins with the story of the Deepwater Horizon disaster. The disaster may have been avoided if a single button had been pushed. The button went unpushed until it was too late because the person did not have permission. Marquet states “How is it that a person could be more afraid of pushing a button without permission, than dying in a fiery explosion?” Hierarchy above all is a power play from the Industrial Age, a play that remains entrenched in corporate life. Fear supported by steep hierarchies, distorts common sense in environments with a strong culture of control and compliance. Previous installments of our re-read of (buy a copy)! Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: - Week 7: - Week 8: - Week 9: - Learn to Solve IT's Dirtiest Secret! Work input, which includes prioritization and sequencing, is how work gets to an organization or team. If you get it wrong you are throwing time and money away. Simply put, poor work intake means no agile for you. Jeremy Willets and I have written tackling the topic that JRoss Publishing will publish in January 2024. In support of the book, we are building a live, workshop-based course for anyone involved in deciding on what work gets completed! This includes Agile Coaches, Scrum Masters, Product Owners, Project Managers, Program Managers, and Portfolio Managers - there are a lot of people involved and that is part of the problem! The workshop will cover why work intake is the biggest challenge to teams and organizations today. Attendees will also learn what to do to solve this challenge. This cohort-based course will combine very short lectures, discussions, and exercises. It will provide space to learn and share with peers. We’re using a survey to build a waitlist for the first cohort – link below. We will use the list to alert you when the workshop is available. Link to Survey! Next SPaMCAST Software Process and Measurement Cast 782 will feature our interview with Govind Balu. We will discuss the importance of data and how organizations are tackling data transformations.

The Software Process and Measurement Cast 780 features our interview with Billie Johnson. Our discussion focuses on the role of delivering outcomes and values using agile teams. We also discussed her book, which she co-authored with Kelley Burns. Re-Read Saturday News The improve play is one of the most powerful aspects of Marquet’s suggested framework. Improve is chapter 7 of . Improve is a time for stepping back from the pressure of getting stuff done to consider whether you are doing the right thing, right. We have spoken about the need to pause, reflect, and replan periodically – this is the heart of the Improve play. Previous installments of our re-read of (buy a copy)! Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: - Week 7: - Week 8: - Learn to Solve IT's Dirtiest Secret! Work input is how work gets to an organization or team. If you get it wrong you are throwing time and money away. SImply put, poor work intake means no agile for you. Jeremy Willets and I have written a book tackling the topic that will be published by JRoss Publishing in January 2024. In support of the book we are building a live, cohort-based course for Agile Coaches, Scrum Masters, Product Owners, Project Managers, Program Managers, and Portfolio Managers on taming work intake. The cohort will cover why work intake is the biggest challenge to teams and organizations today. Attendees will also learn what to do to solve this challenge. We’ve held workshops on this topic at conferences. We even have a book coming out in January on this topic. This cohort-based course will combine very short lectures, discussions, and exercises. It will provide space to learn and share with peers. We’re using this survey to build a waitlist for the first cohort: Next SPaMCAST Software Process and Measurement Cast 781 wrestles with whether overprioritization’s impact extends beyond poor leadership to bad products. Just because you have a prioritized backlog does not ensure delivering value. We will also have a visit from Keis Kostaqi who returns with her You Are Not Alone column.

Software Process and Measurement Cast 779 wrestles with the question, When prioritization involves overly detailed or excessive control over how someone accomplishes their tasks or when it impedes an employee's ability to make their own decisions it becomes micromanagement. Let's explore and look for a path to healing. We will also have a visit from Susan Parente and her Not A Scrumdamentalist column. Susan talks about her impending sabbatical and why taking a pause can be powerful. Re-Read Saturday News Complete is the next chapter in . This concept suggests breaking goals into smaller chunks with pauses to think and replan between each. Another solution to over-prioritization and micromanagement. Previous installments of our re-read of (buy a copy)! Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: - Week 7: - A Call to Action! Jeremy Willets and I are building a live, cohort-based course for Agile Coaches, Scrum Masters, Product Owners, Project Managers, Program Managers, and Portfolio Managers on taming work intake. I wanted to see if you’d be up for sharing it with folks who would find it valuable. The cohort will cover why work intake is the biggest challenge to teams and organizations today. Attendees will also learn what to do to solve this challenge. We’ve held workshops on this topic at conferences. We even have a book coming out in January on this topic. This cohort-based course will combine very short lectures, discussions, and exercises. It will provide space to learn and share with peers. We’re using this survey to build a waitlist for the first cohort: Next SPaMCAST The Software Process and Measurement Cast 780 will feature our interview with Billie Johnson. We will discuss her book, which she co-authored with Kelley Burns. We also talked about using business analysis to power agile teams.

The Software Process and Measurement Cast 778 marks our return from Iceland. WICKED trip, great country, great people! We return with our interview with Bill Fox. Bill and I discussed his new book, , transformation, dialog, listening, and leadership. The many conversations Bill and I have had over the years leave me in a better place. Bill states, “I believe that the great leaders and companies in the 21st century will go on a Forward Thinking journey and be built from the inside out.’ The world has shifted, and new rules apply. It used to be that you would win by managing change, following best practices, working harder, or even smarter. It was the age of Industrial Thinking and people as profit-producing units. Bill’s LinkedIn Profile Websites (Company) (Personal) (Blog) Email bill@billfox.co Re-Read Saturday News This week in our re-read of L. David Marquet’s, , Leaving Bluework Behind: Commit. Whether you classify thinking as System Two thinking or bluework, at some point you have to cross the barrier from contemplation to doing. Chapter Five focuses on reducing the barrier between thinking and action. The process that bridges that barrier is commitment. The author begins the chapter by making the distinction between commitment and coercion. Previous installments of our re-read of (buy a copy)! Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: - Next SPaMCAST The Software Process and Measurement Cast 779 will wrestle with the question, when is prioritization micro-management? The answer is not straightforward but often can be yes. We will also have a visit from Susan Parente and her Not A Scrumdamentalist column.

This week we are on our annual holiday. We are toiling away editing audio and doing voice exercises to bring you new and exciting content and will be back next week! In the SPaMCAST 777 we re-release SPaMCAST 486 - Daniel S Vacanti, Actionable Agile Metrics. The idea of flow metrics has fundamentally changed my perspective on how to use metrics. I have to thank Mr. Vacanti for starting me on the path. Enjoy the interview. The original inroducion - SPaMCAST 486 features our interview with Daniel S. Vacanti. Mr. Vacanti is the author of . We discussed the concepts in the book, answered a question from Steven Adams, and talked about his new book. It was great to talk about a book with the author after the re-read.

We are on our annual holiday and will return with new programs on October 22nd. This week in the SPaMCAST 776 from our archives we feature SPaMCAST 641 - The Agile Coaching Code of Ethics, A Conversation With Shane Hastie and Craig Smith. The show was originally aired on March 7, 2021. I still think the ethics initiative is one of the most important things I have been involved with professionally. Enjoy the discussion. Read more (you really should) at The original inroducion - In the podcast this week, we discuss the Agile Coaching Code of Ethics and the process of building an ethical foundation. Shane Hastie and Craig Smith have been leading the effort to craft a useful Agile Coaching Code of Ethics for the past year. These two thought leaders have helped to pull together a diverse group of coaches, and then guide that herd of cats to create a new force to guide agile coaches of all stripes.

We are on our annual holiday and will return with new programs on October 22nd. The Software Process and Measurement Cast 775 is a re-release of SPaMCAST 635 - Practical Ways to Manage, A Conversation with Johanna Rothman. The show was originally released on January 24, 2021. It was one of the SPaMCAST’s many anniversary editions. Enjoy our conversation The original introduction - Cue the music . . . Happy Birthday, Software Process and Measurement Cast! Today we begin year 15 with a visit from Johanna Rothman. We talked about her THREE new books: Practical Ways to Manage Yourself: Modern Management Made Easy, Book 1 Practical Ways to Lead & Serve (Manage) Others: Modern Management Made Easy, Book 2 - Practical Ways to Lead an Innovative Organization: Modern Management Made Easy, Book 3 - We of course covered more ground. For example about 2/3rds of the way through we talked about why the word experiment is a dirty word in most organizations. This is a longer interview, but when I grow up I want to be just like Johanna (I am serious). See all her books, blogs, and other resources at jrothman.com and createadaptablelife.com.

The Software Process and Measurement Cast 774 is a re-release of SPaMCAST 436. We are on our annual holiday and will be back with new programs on October 22nd. For the next four weeks, we will feature shows from our archives. Today SPaMCAST 436 - Incrementalism, UAT and Agile, and Systems Thinking was released originally on April 3, 2017. I hope you will enjoy today’s show! The original introduction - The Software Process and Measurement Cast 436 features our essay titled, , in which we answer the question of whether the state and culture of the organization or team, can have a large impact on whether a Big Bang approach or an incremental approach makes sense to change. Our second column is from Jeremy Berriault. Jeremy discusses user acceptance testing and Agile. There are lots of different ways to accomplish user acceptance testing in an Agile environment. The only wrong way is not to do UAT in Agile. Jeremy can be found at https://www.berriaultandassociates.com/ Jon M Quigley brings his column, The Alpha and Omega of Product Development, to the Cast. This week Jon puts all the pieces together and discusses systems thinking. One of the places you can find Jon is at .

The Software Process and Measurement Cast 773 will feature our essay on why as professionals we should strive to grow a little every day. I overheard a team lead complaining that their team did not need to do a retrospective, they were “darn near perfect.” The inference was that their time would be better spent doing rather than reflecting and thinking. Fixed mindsets (Review our re-read of Mindsets by Carol Dweck) are foreign to the philosophy of agile and quality. The comment hurt my heart. We will also have a visit from Jon M. Quigley who brings his Alpha and Omega of Product Development column to the podcast! Jon and I use the learning to play a new bass as a metaphor for learning technology. Re-Read Saturday News This week begin a new book on Re-read Saturday, this week! Ten years ago we started our Re-read Saturday journey. The first installment featured . We have read and re-read a lot of books. The book we begin our next ten years is L. David Marquet’s, . This is not Mr. Marquet’s first time in our re-read queue. In 2018 we re-read Turn the Ship Around! I think that book is universally seen as a game changer. Here is the kicker, I think Leadership is Language is more important and useful on a day-to-day basis. I can’t tell how many times I have used ideas from the book in the short time I have owned it. Buy a copy of and begin reading along. Week 1: Logistics, Foreword, Introduction - Next SPaMCAST The Software Process and Measurement Cast 774 will feature a re-release of SPaMCAST 436. We are on our annual holiday and will be back with new programs on October 22nd. For the next four weeks, we will feature shows from our archives. Today SPaMCAST 436 - Incrementalism, UAT and Agile, Systems Thinking from April 3, 2017. I hope you will enjoy the show!

The Software Process and Measurement Cast 772 features our interview with Ahmed Wasfy. We discuss the role of the engineering manager and how people learn to be engineering managers. Coming to grips with the new role requires learning new skills not just rehashed technical skills. Ahmed, advises new leaders to take control of their careers and not to be a victim. Ahmed is an experienced engineering leader, having led teams at Microsoft, Amazon, and Google. In addition to his day job, Ahmed also helps engineering managers become effective leaders through his coaching. Links Instagram: LinkedIn: Website: Re-Read Saturday News After the conclusion of , there are three brief sections with practical tips for making ideas memorable. The dust cover states, “With Added Material (now even stickier)”. The added material provides more food for thought for using Made to Stick. Buy a copy of the book and then catch up on the logistics of this re-read: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Week 8: - Week 9: - Week 10: - Week 11: - Next SPaMCAST The Software Process and Measurement Cast 773 will feature our essay on why as professionals we should strive to grow a little every day. We will also have a visit from Jon M. Quigley who brings his Alpha and Omega of Product Development column to the podcast!

To paraphrase Ghostbusters, critical thinking is the indispensable defense science of the next decade. Over the summer we have investigated the concept so we are better positioned to take part in a boisterous world. As decision-makers, the onus is on us to use critical thinking. Also, Jeremy Berriault joins bringing his QA Corner to the podcast. In this installment, Jeremy discusses the difference between maturity and evolution. Do agile organizations mature or evolve? Re-Read Saturday News We have spent the majority of the summer re-reading . While I didn't take the book to the beach, I did take it to the porch! As with other re-reads, the content of the book has found its way into my writing and consulting practice. In the case of Made to Stick, several ideas and examples have made their way into my essays on critical thinking. The two themes work well together. As you consider sticky ideas you need a framework to test their veracity. Buy a copy of the book and then catch up on the logistics of this re-read: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Week 8: - Week 9: - Week 10: - Next SPaMCAST The Software Process and Measurement Cast 772 features our interview with Ahmed Wasfy. We will discuss the role of the engineering manager and how people learn the role. Being a good engineering manager requires more than a magic wand.

This week the Software Process and Measurement Cast 770 features my interview with Jess Brock. Jess and I talked about her new book, (the book is excellent but doesn’t really fit in your pocket), learning, and career pivots. Jess’s talk at Agile 2023 helped me reframe how I conceived of dojos as an intense learning environment, not a transformation technique. Jess’s Bio Jess is a dynamic coach, technologist, and author who has been involved in developing tech products since the mid-2000s. Jess attributes her diverse career experience as one of her greatest strengths because it enables her to coach with sincere empathy and experience. Former agile skeptic, Jess was eventually convinced by a colleague to give agile a try more than a decade ago. Her personal transformation was so impactful that Jess continues to contribute to the broader Agile community to this very day. Most recently Jess has poured her energy into immersive learning dojos as a preferred means of developing long standing skills. She is the proud author of . Website: http://jessbrock.com/ Re-Read Saturday News The epilogue was the end of the original version of ; later additions had extra material added. I am reading from the 26th printing. We will cover the extra material titled, Sticky Advice, next week. Today we'll discuss the Epilogue, without wrapping the book up. It feels wrong :) I read this chapter more deeply knowing that there was more to come. It felt like less of a recap and more of how to use the book. Three items caught my attention during this read. Buy a copy of the book and then catch up on the logistics of this re-read: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Week 8: - Week 9: - Next SPaMCAST In the Software Process and Measurement Cast 771 we will complete our summer theme on critical thinking. Critical thinking might sound esoteric or academic, however, I think that categorization is both wrong and misses the point. Critical thinking is a survival tool. We will also have a visit from Jeremy Berriault and his Agile Corner.

The Software Process and Measurement Cast 768 features our interview with Phil Alves, CEO of DevSquad. Phil and I covered a wide range of topics starting with how he structures teams to perform in dynamic environments and culminating in a discussion of SaaS and entrepreneurship. Software development of any stripe is a team sport; either get it right or suffer the consequences. Phil describes himself as a SaaS Aficionado! He builds products for bootstrapped founders, fast-growing startups, and big enterprises at DevSquad. His SaaS company, DevStats, helps product and engineering leaders measure what matters. Phil also is a podcaster! The SaaS Origin Stories Podcast uncovers those pivotal moments and decisions that turned SaaS companies into major successes. Contact Information DevSquad: DevStats: Podcast: Re-Read Saturday News In Chapter 5 of we find that an analytical approach reduces people’s ability to be emotionally connected to an idea or concept. Without an emotional connection, they are far less apt to act. Calls to action that are emotionally engaging will generate action. Buy a copy of the book and then catch up on the logistics of this re-read: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Next SPaMCAST In the Software Process and Measurement Cast 769, we return to our summer theme of Critical Thinking. My daughter (Meghan also is the editor for the blog and podcast and sounding board on a wide range of topics) pointed out a model for levels of research. The model provides an interesting filter to help understand the types of research we use and the “power” each delivers. We will also have a visit from Keis Kostaqi. Keis brings her wit, empathy, and wisdom as a Scrum Master in complex environments to help you improve.

In the Software Process and Measurement Cast 767, we continue our summer dive into critical thinking. In this installment, we consider research and evidence. The discussion of research and evidence ties into this week's installment of Re-Read Saturday (Chapter 4 of which is about credibility). Research and evidence provide credibility and that is not always a good thing. Tony Timbol brings his To Tell A Story column to the podcast. In this installment, Mr. Timbol continues to unravel the mystery of the agile requirements and user stories. Re-Read Saturday News Credibility is the fourth requirement for maximum stickiness (short of Gorilla Glue) discussed in . Credibility is defined as the quality or power of inspiring belief or trust. Without credibility, the attributes of simplicity, unexpectedness, and concreteness crumble. Buy a copy of the book and then catch up on the logistics of this re-read: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Next SPaMCAST In the Software Process and Measurement Cast 768, Phil Alves, CEO of DevSquad discusses how he structures teams to perform in dynamic environments. Software development of any stripe is a team sport, you either get it right or suffer the consequences.

This week the Software Process and Measurement Cast 766 features our interview with Ben Johnson, Founder of Particle41. Ben and I discuss the importance of teams, communication, and dependability. Ben Johnson, founder of Particle41, is a serial Entrepreneur with a track record of success and is an active investor. He is a results-driven leader, skilled in managing high-functioning teams for exceptional outcomes. Ben cultivates collaboration, motivation, and effective communication. As a leader, he aligns team efforts with organizational goals and drives innovation. Ben delivers complex projects with visibility, velocity, and vision and is committed to sharing expertise for the growth of others. Particle41: LinkedIn: https://www.linkedin.com/in/benjaminrjohnson/ Re-Read Saturday News The third attribute of stickiness is concreteness. I spent most of the past week at Agile 2023 in Orlando, Florida. It was a metaphorical banquet of agile knowledge. I had more hallway conversations than I can count ruminating over presentation topics. The third chapter of reminded me that language is abstract but real life is not. Most readers of the Software Process and Measurement Cast blog have been to conferences, so reflect on how many ideas and concepts you implemented when you returned to the office. I suspect the answer is very few because few were tangible enough to be sticky. Buy a copy of the book and then catch up on the logistics of this re-read: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Next SPaMCAST In the Software Process and Measurement Cast 767, we will continue our deep dive into critical thinking. We will touch on the need to understand what valid research looks like and perhaps why authority bias makes it hard to recognize. We will also have a conversation with Tony Timbol who brings his To Tell A Story column to the podcast.

In the Software Process and Measurement Cast 765, we will continue with our summer theme on critical thinking by discussing authority. When deciding what to believe, the authority we place on the source has a significant impact. Authority bias is the name for this cognitive bias. We will also have a visit from the one and only Susan Parente, who brings her Not A Scrumdamentalist column to the podcast. In this installment, we discuss why meetings seem to be the only mechanism for making decisions. Re-Read Saturday News And now for something completely different…is both the title of the 1971 movie by Monty Python and the Fly Circus and a hint at Chapter 2’s of title. The title is Unexpected (if you are reading along it won’t be a surprise), and is the second condition for something to be sticky. Buy a copy of the book and then catch up on the logistics of this re-read: Week 1: - Week 2: - Week 3: - Week 4: - Next SPaMCAST In the Software Process and Measurement Cast 766 will feature our interview with Ben Johnson, Founder of Particle41 we discuss how important teams are to delivering value.

In Software Process and Measurement Cast 764 we feature my conversation with Johanna Rothman. We discussed her new book Successful Independent Consulting. Well, we started there and then hit topics like personal value and the impact of success. This might be the eleventy-first conversation I have had with Johanna, and each time I look forward to our time together with anticipation. They are always like attending a master class. Buy a copy of Successful Independent Consulting. Available everywhere including: Leanpub: Amazon: Johanna’s Bio: Johanna Rothman, known as the “Pragmatic Manager,” offers frank advice for your thorny problems. She helps leaders and teams learn to see simple and reasonable options that might work. Those practical alternatives can help them be more effective with others at work. With those choices, they can choose what—and how—to adapt their product development. With her trademark practicality and humor, Johanna is the author of 19 books, hundreds of articles, and blog posts about many aspects of product development. Her most recent books include Successful Independent Consulting, Free Your Inner Nonfiction Writer, and Modern Management Made Easy series. Find her monthly newsletter and blogs at & . Editor's note: If you are not subscribed to Johanna’s newsletter…you should be. Re-Read Saturday News Simple is the first principle of making something sticky. It is also the title of chapter 1 of . There are three areas in this chapter I would like to spend more time with. The formula core + compactness = simple Curse of knowledge Metaphors and analogies As you read the chapter you will see that all three are intertwined; however, each of the three is useful to consider in isolation. Buy a copy of the book and then catch up on the logistics of this re-read: Week 1: - Week 2: - Week 3: - Next SPaMCAST In the Software Process and Measurement Cast 765, we will continue with our summer theme on critical thinking by exploring how experts, experience, and evidence apply to critical thinking. We will also have a visit from the one and only Susan Parente, who brings her Not A Scrumdamentalist column to the podcast.

We open the Software Process and Measurement Cast 763 with an application of critical thinking. Can you see the Great Wall of China from space? Urban legends say yes, Chip and Dan Heath (check out our re-read of ) say no. Let's think about this. We also have a visit from Jon M Quigley. Jon and I discuss the implication of the saying “time is money.” In the information economy using that old saw can lead to more problems than it solves. Re-Read Saturday News This week we begin our re-read of by Chip and Dan Heath in earnest. The Introduction lays out the framework for the book and a lot more. This is not one of those introductions you can skip. I can tell that this reading of is going to be different than the first. Heraclitus stated, “No man ever steps in the same river twice, for it’s not the same river and he’s not the same man.” This re-read may well be an examination of the dangers of accepting sticky ideas and those that generate sticky ideas. Buy a copy of the book and then catch up on the logistics of this re-read: Week 1: - Week 2: - Next SPaMCAST In the Software Process and Measurement Cast 764 will feature my conversation with Johanna Rothman. We discussed her new book Successful Independent Consulting. Well we started there and then hit topics like personal value and the impact of success. Talking with Johanna is the same as attending a master class.

In the Software Process and Measurement Cast 762, we host a panel discussion on the impact of AI on project management prospects. The panel of Paul Clapis, Susan Parente, Michael Milutis, and Mark Tolbert state categorically that project administration will be overtaken, but the high-value human side of project management will not be displaced. I am not sure what that means for most people working in the project management space. Listen to the discussion and then look carefully at the work you are doing. Will AI be a boon or a bane for project management? Let the conversation begin. About Paul J. Clapis, Ph.D.: Dr. Clapis has over 30 years of experience managing AI, Machine Learning, and RPA projects for NASA, aerospace, and financial services industries. He also directed the Hughes Advanced Computing Lab at Yale Science Park, where he conducted applied research in AI, Expert Systems, Machine Learning, and Neural Networks. About Susan Parente: Susan is an Engineer/Consultant, speaker, and author with experience managing both software and hardware development. She is proficient in managing complex system implementation for companies seeking to use enterprise business software to improve business process efficiency. Susan is a regular contributor to the Software Process and Measurement podcast. About Michael Milutis: Michael Milutis is an international keynote speaker, instructor, and 25-year veteran of the IT industry who has dedicated his career to helping individuals learn, develop, and compete within a shifting technology landscape. About Mark Tolbert: Mark has over 30 years of experience in I.T., including 27 years at Hewlett-Packard. He successfully managed support programs and projects within HP Services. He is a full-time instructor for PMP Prep classes since November 2007. He is very passionate about project management and believes adopting the best project management practices and skills is crucial to the success of enterprises today. Re-Read Saturday News The votes are in and we have a near tie for the top spot. I decided to re-read by Chip and Dan Heath first. Part of the rationale is that I have two copies of this book and have not read by L. David Marquet – yet. Once we have completed Made to Stick, we will launch ourselves into Leadership Is Language. By then I will have read the book. Buy a copy of the book and then catch up on the logistics of this re-read: Week 1: - https://bit.ly/46tn5Bz Next SPaMCAST In the Software Process and Measurement Cast 763, we will continue with our summer theme on critical thinking by exploring whether sources should matter when considering a topic. We will also have a visit from Jon M Quigley and his Alpha and Omega of Product Development.

In the Software Process and Measurement Cast 761 we continue our exploration of critical thinking. In this installment, we examine logical fallacies. The logic in logical fallacies is incorrect whether by design or misinterpretation. You need to be prepared. This week, Jeremy Berriault brings a discussion of QA Audit in agile to the QA Corner. Are QA Audits a logical fallacy? Re-Read Saturday News The Re-read Saturday has been a feature of the Software Process and Measurement blog since 2013 (7 Habits of Highly Effective People was the first book). This week we are still in the process of choosing the next book or books (we chose three last time), therefore we have a bit of an interlude today. I need your input to make the final cut! Please provide your input using the poll below. https://poll.fm/12416734 In the interim catch up on the re-read of . Buy a copy because you can’t borrow mine! All of the Team Topologies re-read installments: Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: – Week 7: – Week 8: Choose – Week 9: - Week 10: - Week 11: - Next SPaMCAST In the Software Process and Measurement Cast 762, we will share a panel discussing the impact of AI on the future of project management. A boon or a bane? Let the conversation begin.

SPaMCAST 760 will feature an interview with Jonathan Hensley, Founder & CEO at EMERGE. Jonathan and I talked about digital transformations and engagement. The core boils down to people and alignment. This was an extremely refreshing interview! Let me know what you think. Jonathon Hensley is co-founder and CEO of Emerge, a digital product consulting firm that works with companies to improve operational agility and customer experience. For more than two decades, Jonathon has helped startups, Fortune 100 brands, technology leaders, large regional health networks, non-profit organizations and more, transform their businesses by turning strategy, user needs and new technologies into valuable digital products and services. Jonathon writes and speaks about his experiences and insights from his career, and regularly hosts in-depth interviews with business leaders and industry insiders. He lives in the Pacific Northwest with his wife and two boys. (Company) (Company) (Mobile First Podcast) Re-Read Saturday News First things second! Help me pick the next batch of books to be re-read. Pick two books from the poll below or email me at if you have a different suggestion. https://poll.fm/12416734 Back to first things! We completed our re-read of this week. If you have (or ever will have) any input into how teams are formed and maintained you need to read this book at least once. PS - buy a copy because you can’t borrow mine! All of the Team Topologies re-read installments: Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: – Week 7: – Week 8: Choose – Week 9: - Week 10: - Week 11: - Next SPaMCAST In the Software Process and Measurement Cast 761, we will continue our exploration of critical thinking. In this installment, we will examine several of the attributes of critical thinking. We will also have a visit from the QA Corner. Mr. Berriault brings his wisdom to the podcast.

The SPaMCAST 759 continues our exploration of critical thinking. This week we search for a consumable definition. If you can’t hold a definition in your mind it is hard to contemplate the impact and necessity of rigorous thinking. Keis Kostaqi, brings the first installment of her Scrum Master, Facilitation and Transformation column to the podcast. In this installment, Keis discusses the impact of hierarchy on the role and behavior of Scrum Masters. Re-Read Saturday News We are nearly at the conclusion of . Over the next few days, we will post a poll to get the selection process moving for our next re-read book. Chapter 8 is titled “Evolve Team Structures With Organization Sensing.” I was struck by two important (and related) concepts during this read. They both are encompassed in the quote “the most important thing is not the shape of the organization itself but the rules and heuristics used to adapt and change the organizations as new challenges arise.” Previous Installments: Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: – Week 7: – Week 8: Choose – Week 9: - Week 10: - Next SPaMCAST SPaMCAST 760 will feature an interview with Jonathan Hensley, Founder & CEO at EMERGE. Jonathan and I talked about digital transformations and engagement. The core boils down to alignment.

Jeffrey Miller and I have been trying to coordinate a time for an interview on the topics of tribal knowledge and team playbooks since August 2022. We finally solved that problem. Teams generate knowledge, understanding how to hold on to that knowledge and to push boundaries forward is why teams are powerful. Jeffrey Miller Technologist, Speaker, Author Jeffrey Miller is a Senior Consultant at Manifest Solutions in Columbus, Ohio. Jeffrey has over two decades of experience helping organizations bring value to their mission through software. He has presented a variety of topics at local user groups, regional tech conferences, and national healthcare meetings. Jeffrey and his wife, Brandy, are adoptive parents and have written a fun children’s book called "Skeeters" with proceeds supporting adoption. Learn more about the project at . Contact Information Blog: Company Website: LinkedIn: Twitter: Re-Read Saturday News Part 3 of , integrates team interactions with the team topologies. In Chapter 7, Team Interaction Modes, the authors define three basic interaction patterns. Buy a copy of and read along! Previous Installments: Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: – Week 7: – Week 8: Choose – Week 9: - Next SPaMCAST SPaMCAST 759 will feature an essay building on our essay in SPaMCAST 757 which challenged the common agile belief that constant collaboration is a silver bullet. We will use this belief to explore critical thinking. We will also have a visit from Keis Kostaqi who brings her perspective of being a Scrum Master in a complicated environment.

A funny thing happened on the way to SPaMCAST 757. I was considering critical thinking when I ran into data that challenged a common agile belief - enter critical thinking. The idea is that constant collaboration, the goal of team rooms, and always-on communication software, is to create good ideas and decisions; good but not great. This week we also have a visit from Susan Parente who talks about her approach to personal kanban, something she calls kanban for one. Susan also takes us under the hood for a view into her busy, innovative world and how she keeps it under control. Re-Rread Saturday News This week we are back with Chapter 6 of by Matthew Skelton and Manuel Pais. The boundaries of teams are shaped by numerous pressures ranging from corporate politics and specialism to architectural structure. Inspecting the majority of teams it would seem that boundaries are the outcome of a random walk because they reflect all of these pressures over time. For more of a dive into the topic, check out the book and the whole re-read! Previous Installments: Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Week 8: - Next SPaMCAST SPaMCAST 758 will feature our discussion with Jeffrey Miller. We will discuss the idea of tribal knowledge and playbooks. Teams generate a lot of information and knowledge - capturing that knowledge is not as easy as wishful thinking or waving a magic wand.

SPaMCAST 756 welcomes back Paul Gibbons. In this visit, we discuss his new book which he co-authored with Tricia Kennedy. I have described Paul’s new book as a Trojan horse. While it dispels myths it more importantly provides the tools for critical thinking which will allow you to tackle new myths as they appear. Pau’s bio: Paul Gibbons is an author, academic, speaker, and business consultant He has authored numerous books, including and The Science of Successful Organizational Change, He lives in the Denver area with his two sons and enjoys playing poker, chess, and other mind sports. Paul’s Website: Email: Paul@paulgibbons.net Facebook – Twitter – YouTube – Philosophyfirst LinkedIn – Paul G Gibbons The interview with Paul was huge, so no Re-read Saturday News this week. We will be back next week. In the interim, buy a copy and catch up. Use the link to buy a copy of by Matthew Skelton and Manuel Pais. Previous Installments: Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Next SPaMCAST SPaMCAST 757 will begin an arc on critical thinking. The interview in this week’s podcast has caused me to begin to explore critical thinking and why the idea is important for agile coaches. We will also have a visit from Susan Parente who brings her Not A Scrumdamentalist column to the podcast.

SPaMCAST 755 features an essay on the relationship between engagement, hierarchy, and fatalism based on a discussion of the topic between the SPaMCAST Columnists. The ideas of hierarchy, engagement, and fatalism struck a nerve within the SPaMCAST family. To a person, the prevailing attitude is that hierarchy has value, but only to a point. Jon M Quigley joins the cast in the second slot this week with a discussion about making mistakes. Learning from mistakes is important but making the same mistake over and over is not a sign that you are learning. Re-read Saturday News! This week we finish the re-read Chapter 5 of by Matthew Skelton and Manuel Pais. As noted last week, Chapter 5 is a powerhouse. This week, let's examine some of the behaviors that the four fundamental team topologies exhibit. Understanding how teams structured in this manner should behave will also be useful for understanding which team type delivers the most value to the organization in a specific context. Buy a copy and read along! - Previous Installments: Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Next SPaMCAST SPaMCAST 756 will welcome back Paul Gibbons. In this visit we discuss his new book which he co-authored with Tricia Kennedy. The book gives you the tools to sort the sense from the nonsense -- and there is a lot of nonsense in the change management field.

Today I would like to introduce you to the Software Process and Measurement Cast’s newest columnist, Keis Kostaqi. Keis is a scrum master and coach. She will bring a Scrumban flavor to the podcast. Keis has experience with teams with complicated work input patterns. Today we get to know Keis - and get some interesting ideas along the way. Keis Kostaqi is a passionate Agile Coach with years of experience in healthcare, information services, and technology. Currently serving as a Program Manager for the Agile Transformation Team at Northwestern Medicine, she enables individuals and teams to be successful through continual learning and growth and facilitates self-managed continuous improvement. Keis serves at the Greater Illinois Chapter of HIMSS Board of Directors as an Educational Programs Director, where she plans and implements the chapter's programs and educational activities. She is also a Woman in Agile member focused on building mentor-mentee relationships that help the Women in Agile community unlock their full potential. She holds an MBA and is also a Certified Scrum Master and Product Owner. Other interests include traveling, food lover, writing novels, volunteering, and binge-watching TV shows. Contact Information: Re-read Saturday News! This week we re-read Chapter 5 of by Matthew Skelton and Manuel Pais. Chapter 5 is a powerhouse. This chapter lays out the four fundamental team topologies with examples. I read this chapter twice during my first read of the book and I read it twice this week. We will approach thinking through the re-read over two weeks. This week we start with a little practice identifying the four basic team topologies. Buy a copy and read along! - Previous Installments: Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Next SPaMCAST SPaMCAST 755 will feature an essay on the relationship between team design, flow, and behavior. Organizations passionately espouse the need for increasing productivity and process improvement but rarely tackle the problem of team design. Let's look that scary idea straight in the eye. We will also have a visit from Jon M Quigley who will regale us with wisdom in his Alpha and Omega of product development column.

SPaMCAST 753 features our essay on the impact of hierarchies on engagement and fatalism. Like most things in life, the relationship is not straightforward. Hierarchies giveth and taketh away. If you don’t get the balance right you can say goodbye to engagement, innovation, and fun at work. We also have a visit from Tony Timbol who brings his insights on the life cycle of user stories to the podcast in his To Tell A Story column. In this installment, we talk about the “Wall of Confusion.” When stories are created and then tossed over the wall to another team even high-performing teams slip into the slow lane. Re-read Saturday News! This week we re-read Chapter 4 of by Matthew Skelton and Manuel Pais. The title of Chapter 4 is Static Team Topologies. One of the underlying messages in the chapter is that team topologies should not be static. However, not being static isn’t the same as playing musical chairs. Buy a copy and read along! - Previous Installments: Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Next SPaMCAST SPaMCAST 754 introduces Keis Kostaqi. Keis is a scrum master and coach. She will bring a Scrumban flavor to the podcast with a column on agile teams with complicated work input patterns. Keis begins her column with a bit of an introduction and a bucket load of experienced-based advice.

SPaMCAST 752 features our interview with Laura Bell Main. We discuss the confluence of fast-growing companies and security. Maybe I should say collision instead of confluence. Note: Laura provides an incredible amount of wisdom in the interview; however, due to a user error (mine) I lost the first minute of the interview. The abrupt start of the interview means we hit the ground running with very little preamble. Laura Bell Main specializes in securing some of Australia and New Zealand’s fastest-growing organizations. She has over twenty years of experience in software development and information security. It's her mission and passion to bring security into organizations of every shape and size. Laura is the founder and CEO of SafeStack Academy, an online education platform offering flexible, high-quality, and people-focused, secure development training for fast-moving companies, with a focus on building security skills, practices, and culture across the entire engineering team. SafeStack is a value’s driven company on a mission to make cybersecurity accessible for everyone and any organization. “To protect each one of us, we must protect all of us” Connect With Laura Bell Main: mobile.twitter.com/lady_nerd l Re-read Saturday News! Chapter 3 of by Matthew Skelton and Manuel Pais is titled Team First Thinking. Using teams to get work done in all walks of life is undeniable. Whether the idea of “team” emerged a century ago or last week is less important. What is important is the knowledge that very little work happens without teams. Team-first thinking makes simple sense. Buy a copy and read along! - Previous Installments: Week 1: – Week 2: – Week 3: - Week 4: - Next SPaMCAST In SPaMCAST 753 we will return to our discussion of fatalism to examine the relationship between hierarchy, fatalism, and engagement. We will also have a visit from Tony Timbol who will bring his To Tell A Story column to the podcast.

I have been considering the relationship between privilege and fatalism. Boiling down the impact of privilege to a single word, we find power. Whether it is the ability to make decisions about the work you will do, the power to direct others to do work, or even just to be heard, privilege is power. That power can generate fatalism in those without the power privilege delivers. In SPaMCAST 751 we discuss! Jeremy Berriault brings his QA Corner to the podcast. Mr. Berriault and I discuss why continuous improvement is important. Our discussion ties neatly into the essay on privilege and fatalism. We all have to commit to getting better every day or risk becoming irrelevant. Re-read Saturday News! Chapter 2 of by Matthew Skelton and Manuel Pais is a deep dive into Conway’s Law both forward and backward (the Reverse Conway Manuver). Conway’s Law states simply: the way people are organized influences software architecture. Buy a copy and upgrade your coaching skills - Previous Installments: Week 1: – Week 2: – Week 3 - Next SPaMCAST SPaMCAST 752 features our interview with Laura Bell Main. We will discuss the confluence of fast-growing companies and security. Maybe I should say collision instead of confluence.

SPaMCAST 750 marks the return of Evan Leybourn to the podcast. Evan and I discuss the different domains of business agility, the relationship between behavior and culture, and whether Taylorism still has a place in the world. Evan is the co-founder of the Business Agility Institute; an international membership body to both champion and support the next generation of organizations. Companies that are agile, innovative, and dynamic - perfectly designed to thrive in today’s unpredictable markets. Evan is also the author of Directing the Agile Organisation (2012) and #noprojects; a culture of continuous value (2018). Website: Re-read Saturday News! This week we tackle Chapter 1 of by Matthew Skelton and Manuel Pais. The authors open Chapter 1 with a quote from Naomi Stafford, Guide to Organizational Design. “Organizations should be viewed as complex and adaptive organizations rather than mechanistic and linear systems” The quotes set the tone for . Chapter 1 is titled The Problem With Org Charts. In this chapter, the authors point out problems in how organizations describe and organize themselves. Buy a copy and upgrade your coaching skills - Previous Installments: Week 1: - Week 2: - Next SPaMCAST SPaMCAST 751 will feature an essay on the collision of fatalism and privilege. Let's just say…it isn’t pretty. Jeremy Berriault will bring his QA Corner to the podcast. Mr. Berriault and I will discuss testing, Quality, and evolving behavior.

In SPaMCAST 749, we discuss the attributes of good work input/entry. There is no perfect approach to bringing work into an organization or team. Arguably since people are involved, perfect may not be something that can exist in the real world but instead, there are good approaches. There are nine key concepts for good work entry. Good work entry requires that these nine have to be present in some form regardless of whether you are using Scrum, Kanban waterfall, or some mix of frameworks. We want to be crystal clear, deciding to forego any of these characteristics other than for the briefest moment will set you on the path to the ninth circle of work entry hell. We also have a visit from Susan Parente who brings her Not A Scrumdamentalist column to the podcast. Susan and I diagnose why some organizations think that a product owner can also be a scrum master. Re-read Saturday News! Today we begin the re-read of by Matthew Skelton and Manuel Pais. The book contains front matter, including a foreword and preface (22 pages), 8 chapters, a conclusion (190 pages), and end matter (glossary, recommended reading, references, notes, index, acknowledgments, and about the authors). Today we tackle the approach to the re-read and the front matter. Buy a copy and upgrade your coaching skills - Previous Installments: Week 1: - Next SPaMCAST SPaMCAST 750 will mark the return of Evan Leybourn to the podcast. Evan and I discuss the different domains of business agility and whether Taylorism still has a place in the world.

SPaMCAST 748 features our interview with Bob Galen. Bob and I discuss Extraordinary . With the interview, we wrap up the re-read and then moved on to talk about improving coaching and the agile industrial complex. Bob Galen is an Agile Practitioner, Trainer & Coach based in Cary, NC. In this role, he helps guide companies and teams in their pragmatic adoption and organizational shift towards agile methods of working. Bob has been doing that since the late 1990s, so he’s deeply experienced. He is the Director of Agile Practice at Zenergy Technologies, a leading business agility transformation company. Bob is also President and Head Coach at RGCG a boutique agile coaching firm. Bob regularly speaks at international conferences and professional groups on topics related to agile software development, testing, scaling, and organizational leadership. He is a Certified Enterprise Coach (CEC), Scrum Alliance CAL trainer, and an active member of the Agile & Scrum Alliances. He’s published four agile-centric books: The Three Pillars of Agile Quality and Testing in 2015, Scrum Product Ownership, 3’rd Edition in 2019, Agile Reflections in 2012, and Extraordinarily Badass Agile Coaching in 2022. He’s also a prolific writer & blogger (at - www.rgalen.com and www.agile-moose.com) and podcaster (at www.meta-cast.com ) Bob may be reached directly at: bob@rgalen.com or networking via: http://www.linkedin.com/in/bobgalen Re-read Saturday News! This week we conclude our re-read of Extraordinary . Extraordinary Badass Agile Coaching is my new go-to coaching reference. It will be the book I recommend to anyone playing a coaching role in an agile environment. As we know a wide variety of organizational roles such as team leads, Scrum Masters, managers, and of course agile coaches coach. Coaching is dynamic and complex. What would you expect? There are people involved. Bob and his co-authors provide the tools to help a coach go from meh to badass. Buy a copy and upgrade your coaching skills - Previous Installments: Week 20: - Week 19: - Week 18: - Week 17: - Week 16: - Week 15: - Next SPaMCAST In SPaMCAST 749 we will discuss the attributes of good work input/entry. We have discussed patterns and anti-patterns. We explore what makes good work entry, good. We will also have a visit from Susan Parente who brings her Not A Scrumdamentalist column to the podcast.

This week we continue our exploration of fatalism’s impact on change in organizations (listen to Part 1 in ). Fatalism does not have to be permanent. How that transition away from fatalism can be made varies depending on context. In this installment of the series, we will look at a few approaches to tackling this problem. We also have a visit from Jon M Quigley. Jon and I discussed succession planning and why planning needs to be more diverse to support organizational health. Re-read Saturday News! This week we re-read Chapter 20 of Extraordinary . Bob notes that Stephen Covey’s seventh habit in his classic, Seven Habits of Highly Effective People, is sharpening the saw. This is a reminder that who and where we are today can’t be who or where we are tomorrow. This habit is a prescription for balanced self-renewal. This is the last chapter of Extraordinary Badass; next week we will discuss the afterword and final thoughts. Buy a copy and upgrade your coaching skills - Previous Installments: Week 19: - Week 18: - Week 17: - Week 16: - Week 15: - Next SPaMCAST SPaMCAST 748 features our interview with Bob Galen. Bob and I will discuss Extraordinary and wrap up the re-read.

This week we discuss the Manifesto for Organizational Agility with Jeff Bubolz and Chad Beier. Jeff and Chad developed the manifesto to help organizations get agile and stay agile. Many organizations rush into agile finding early success that turns sour a few months or years down the road. This pattern is indisputable. The Manifesto seeks to highlight the core issues that lead to this pattern (you will also want to listen to the interview with Bob Galen on SPaMCAST 748 due to be posted on 26 March). You can read the Manifesto for Organizational Agility at http://bit.ly/3mOnBaU Chad and Jeff’s Bios: Chad is an organizational agility advisor and external change agent with Wisconsin Agility and Professional Scrum Trainer (PST) with Scrum.org. He promotes organizational agility and positive pressure for change through speaking, advising, coaching, and training. Jeff is a Professional Scrum Trainer (PST) with Scrum.org, organizational agility advisor, podcast host, and speaker. Jeff brings storytelling, a broad array of experience, along with a collaborative approach to teaching and speaking. Contact information and More: Wisconsin Agility: Agile Wire Podcast (one of my favorites): Chad Beier: Chad Beier’s Agile Songs: https://www.youtube.com/channel/UCrE4EJKhiUtc3j5aAnRlskg Jeff Bubolz: Re-read Saturday News! Chapter 19 of Extraordinary is titled “ Setting Up a Badass Agile Coaching Community of Practice.” I have strong opinions about Communities of Practice (CoP). They can be a very valuable tool, when done well, for supporting movements within an organization. As Mr. Galen points out, a CoP, is a place for learning and feedback. Done poorly they are invasive and harmful. CoPs will get like-minded people together to learn, support each other, interact, and become a community. Buy a copy and upgrade your coaching skills - Previous Installments: Week 18: - Week 17: - Week 16: - Week 15: - Next SPaMCAST We will continue our exploration of fatalism’s impact on change in organizations (listen to the essay in SPaMCAST 745). Fatalism does not have to be permanent. How that transition away from fatalism can be made varies depending on context. In the next installment in this series, we will look at a few approaches to tackling this problem. We will also have a visit from Jon M Quigley who will bring his Alpha and Omega of Product Development to the podcast.

Fatalism stops process improvement and agile transformations in their tracks. One of the definitions of fatalism is the belief that all events are predetermined and therefore inevitable. Just accepting the status quo because it is the status quo isn’t pragmatism it is stagnation. We also have a visit from Tony Timbol who brings his To Tell A Story column to the podcast. Sign up for his free newsletter () and get a copy of the ebook on agile requirements we discussed. Re-read Saturday News! Chapter 18 of Extraordinary is titled “Dojo Practice for the Badass Agile Coach.” The coaching dojo in Chapter 18 has a much smaller footprint than other dojos I have participated in and is easily implementable. I ran two this week and have plans for several more. Buy a copy and upgrade your coaching skills - Week 17: - Week 16: - Week 15: - Next SPaMCAST The next Software Process and Measurement Cast will feature a conversation with Jeff Bubolz and Chad Beier. We discussed their Manifesto for Organizational Agility ( Agility.) - a new manifesto for the dynamic world of work.

This week Nikhil Nandagopal and I talked about building teams. Teams are the heart and soul of software development in all of its many aspects. Nikhil provides pragmatic advice for organizing people into teams. We also discussed the democratization of coding that low-code platforms deliver. Nikhil Nandagopal, a co-founder of Appsmith, leads the development of the company’s product – the first open-source low-code platform for developers. He is a software engineer and entrepreneur with 10 years of experience building apps. Nikhil’s Website: Nikhil’s Profile: Twitter Re-read Saturday News! Chapter 17 of Extraordinary is titled “The Badass Agile Coach’s Guide to Starting Your Day” which provides a structure or ritual for beginning each coaching day. I almost see this as a macro planning arc that Bob has recommended for all coaching sessions. Thinking about Christmas presents for your coaching friends? (302 days from today!) Buy a copy and beat the rush - Week 16: - Week 15: - A quick advertisement: Controlling work entry requires preparation, knowledge, and building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST In the next Software Process and Measurement Cast, I want to talk about one of the great enemies of change - fatalism. Phrases like “that's not our culture” or “that won’t work here” are discussion killers. We will also have a visit from Tony Timbol who brings his To Tell A Story column to the podcast.

This week, we take a detour thanks to Extraordinary Badass Agile Coaching. Over the past two chapters, the book has drilled us on recognizing and adapting to situational nuances as a crucial skill for effective coaching. I will admit that my first few years of coaching were formulaic. I did not spend the needed time to understand and address nuances of context or differences in individuals' journeys through life. I do not remember when I learned that roles and situations change the trajectory of coaching, as does the starting point of the person or persons you are coaching. At some point, I got the point. In this chapter, diversity is an omnibus term used to describe inclusiveness across a range of different social and ethnic backgrounds and of different genders, sexual orientations, life experiences, and more. Galen-Personick focuses on four specific areas. Rather than recounting the four, what struck me during this read was the impact privilege has on both delivering and being coached. That’s what I discuss in today’s podcast. Jeremy Berriault brings his QA Corner to the podcast. This week we communicated on the topic of communication. Re-read Saturday News! Chapter 16 of Extraordinary is titled Situational Awareness as a Badass Agile Coach. This chapter is written by Rhiannon Galen-Personick and focuses on diversity awareness. The author uses four areas of diversity to help coaches think through their biases, the biases of the people they are coaching, and the biases of the teams around them. This is in an effort to teach all of us to be better coaches and, dare I say, people. Week 15: - A quick advertisement: Controlling work entry requires preparation, knowledge, and building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST In the next Software Process and Measurement Cast, Nikhil Nandagopal and I talked about building teams. Teams are the heart and soul of software development in all of its many aspects.

This week, Jorgen Hesselberg discusses the efficacy of assessments in helping to guide an agile journey. Assessments are a tool to help coaches coach and to answer the question of where are we in our journey toward being more agile. Jorgen last appeared in SPaMCAST 557 in 2019 (). Jorgen Hesselberg is the author of Unlocking Agility and co-founder of Comparative Agility, a leading agile assessment, and continuous improvement platform. A proven thought leader of numerous successful enterprise transformation efforts since 2009, Jorgen provides strategic guidance, executive counsel, and coaching to some of the world’s most respected companies, both as an internal change agent and an external consultant. He has trained thousands of people on agile and Scrum, disruptive innovation, and enterprise transformation strategy. Contact Information Email: jorgen@comparativeagility.com LinkedIn: Comparative Agility: Re-read Saturday News! Chapters 14 and 15 of are titled Badass Role-Based Coaching and Context-Based Coaching. Written by Jennifer Fields, the chapters explore role-based and context-based coaching dynamics. The two chapters are intertwined; I view roles as a specialized type of context. Jennifer presents several scenarios in both chapters on how she would approach coaching events for different roles and contexts. Week 1: - A quick advertisement: Controlling work entry requires preparation, knowledge, and building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST In the next Software Process and Measurement Cast, we continue our journey into the use of flow metrics to plan work. Next week we will tackle something more complex. We will also return to the QA corner with the regular version of Mr. Barriault’s column.

Planning is an important component of getting work done. Planning is not, however, creating and delivering work. Minimizing the amount of time spent planning but not under planning is almost mind-numbingly difficult. Flow metrics are tools to maximize the value of planning while minimizing the time spent on planning. Over the next few entries in the Software Process and Measurement Blog, we will explore several examples of using flow metrics in planning. We also have a visit from Susan Parente who brings her Not A Scrumdamentalist column to the podcast. Susan provides guidance on navigating environments that are not pristinely agile in a pragmatic fashion. Re-read Saturday News! Chapter 13 of is titled Badass Pair-Coaching. Over the years I have had many opportunities to participate in pair coaching, although fewer over the past few years. I miss pair coaching; it pushes me to expand my horizons and up my game. What about you? Week 13: - A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Jorgen Hesselberg returns to the podcast to discuss the efficacy of assessments in helping to guide an agile journey. Assessments are a tool to help coaches coach and to answer the question of where are we in our journey toward being more agile. Jorgen appeared in SPaMCAST 557 in 2019 ()

Today we begin year 17 of the Software Process and Measurement Cast with a presentation that Jeremy Berriault did at IdeaFest 2020. The presentation covered using supply chain concepts in an agile environment. When I originally recorded the session, I felt the idea was interesting but not very useful. But I am a bit of a packrat; I don’t throw anything away. Last week I listened to the presentation again. This time I could see that the idea of using supply chain concepts is a great approach to implementing value chains and mirrors why flow metrics are such a valuable concept. Jeremy was just a bit ahead of the rest of the world. Note, the recording is not perfect. There is some external noise from unmuted microphones in the feed. I think the bit of interference does not diminish the message. The content is great; stay with it and you will have a lot to think about. The slides: (see www.spamcast.net Jeremy’s website: https://berriaultandassociates.com/ Re-read Saturday News! This week Chapter 12 of focuses on language. Language is both essential and a deterrent for creating understanding. This is a provocative statement, but the truth of the statement is not open for debate. Week 12: - A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Using flow metrics to plan in Kanban and Scrum environments. Flow metrics are incredibly useful metrics for value streams and value chains. They are equally useful at the team level — and in some cases even more powerful. We will also have a visit from Susan Parente who brings her Not A Scrumdamentalist column to the podcast.

Today we revisit the topic of empathy as we mark the last show in year 16. As coaches and leaders, we are taught that being empathetic is critical. However, the blanket statement that we need to walk a mile in someone else's shoes is not all rainbows and kittens. We will also have a visit from Jon M Quigley who brings his Alpha and Omega of Product Development column to the podcast. Jon and I continue our conversation on flow and its importance for teams and leaders. Re-read Saturday News! This week Chapter 11 of looks up. Even if you focus your agile coaching practice on teams you will need to coach up the managerial and executive hierarchy of the team. Week 11 - - http://bit.ly/3ZWo6z1 A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Using flow metrics to plan in Kanban and Scrum environments. Flow metrics are thought of as incredible metrics for value streams and value chains. They are equally useful at the team level — and in some cases even more powerful. We will also have a visit from Jeremy Berriault who brings his QA Corner column to the podcast.

Luis Gonçalves returns to the Software Process and Measurement Cast to discuss his new book, Product First. We also talked about organizational mastery and change. Become a beta reader of Product First at Luis last joined us on , we discussed OKRs. Luis’s Bio Luis Gonçalves is an Entrepreneur, Best Seller Author, and International Keynote Speaker. When consulting he works exclusively with Entrepreneurs, Founders, and Senior Leaders on the implementation of his game-changing "ADAPT Methodology". By following the "ADAPT Methodology" Executive Leaders will be able to transform their traditional project-oriented companies into modern digital product companies. OKR Guide: Website: Website: Podcast: https://adaptmethodology.com/podcast/ LinkedIn: Re-read Saturday News! This week Chapter 10 of enumerates the four meta-skills in the Coaching Growth Wheel. They are: Leadership, Change Artistry, Inspiration, and Role Modeling. These four skills underpin the model and I strongly recommend a close reading of the chapter. A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Using flow metrics to plan in Kanban and Scrum environments. Flow metrics are thought of as incredible metrics for value streams and value chains. They are equally useful at the team level — and in some cases even more powerful. We will also have a visit from Jon M Quigley who brings his Alpha and Omega of Product Development column to the podcast.

A funny thing happened on the way to this week’s Software Process and Measurement Cast, I was asked about managing risk in Agile. In preparation for answering the question, I reviewed and updated some of my work on the topic. So instead of flow metrics, we have an essay on risk. That is just the chance you take when you ask me a question. Note -- I have a great question on risk to ask Susan Parente, @techriskmanager, the next time we record. We also have a visit from Tony Timbol. Tony discusses agile requirements in an installment of his To Tell A Story column. Check out Tony at http://tonytimbol.com/ Re-read Saturday News! This week we tackle Chapters 8 and 9. These chapters of are titled An Agile Coaching Story, Parts 1 and 2. They are written by Mark Summers of Beliminal and provide great advice on how to prepare and execute coaching events. Week 9 - - A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Luis Gonçalves is back to discuss his new book! Luis and I had a great time talking about shifting from projects to product thinking, organizational mastery, and more!

Today we share our year-end panel discussion with the SPaMcast contributors and occasionally our dogs (once one gets going everyone needs to get in on the action). The topic this year is engagement. Is being on two calls at once, engagement? Does just being present tick the engagement box? Patterns and antipatterns abound, but Is engagement really that important? The panelists for this installment are: Jeremy Berriault Jeremy Willets Susan Parente A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Using flow metrics to plan in Kanban and Scrum environments. Flow metrics are thought of as incredible metrics for value streams and value chains. They are equally useful at the team level -- and in some cases even more powerful. We will also have a visit from Tony Timbol who brings his “To Tell A Story” column to the podcast.

Over the years we have explored a wide range of books on Saturdays. Sometimes our re-reads reflect the real world outside software development. For example, in 2018 we re-read by John Carreyrou, the story of Theranos and Elizabeth Anne Holmes. This year Ms. Holmes went to prison. While I don’t expect prison sentences for the subjects in the books we read in 2022, I expect the knowledge in the books we tackled to have a broader impact on the world. In the past year, we have re-read 3.4 books – 40% is the progress on the current book according to Kindle. Links to all of the read entries can be found in the show notes. I am looking forward to reading and learning with all of you in 2023. This week we also have a visit from Susan Parente and her Not A Scrumdamentalist column. Susan and I discussed how a newly minted Scrum Master can get up to speed quickly. A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Every year I host a panel discussion with the columnists and other SPaMcast contributors. We will cap 2022 with a spirited discussion on the importance of engagement. Is it all that its cracked up to be or not?

While preparing for this week’s podcast I ran across a recording of a presentation I did at IDEAfest 2020. The topic was the seven macro trends driving software development behavior. The presentation was crafted just at the beginning of the Covid19 pandemic but the topics are still relevant, perhaps even more relevant than they were in March 2020. So to make a long story short, I re-edited the recording and decided to share the talk with those that weren’t at IDEAfest 2020 or have blanked the last two years from their memory. I will also post the presentation in the feed for your pleasure and to spark conversation. Re-read Saturday News This week we re-read Chapter 6 of (Amazon Associate Link - buy a copy or two and give them to friends). Chapter 6 of is titled, Badass Agile Coaching Operating System. There are several important concepts to explore in this chapter all wrapped into the metaphor of a computer operating system. Previous Entries in Our Re-read: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST The SPaMCAST 735 feature an essay on using flow metrics to plan either an epic or a sprint. Simply put the process generates a ton of knowledge and is dead simple . . . why aren’t you using it now? We will also have a visit from Susan Parente and her Not A Scrumdamentalist column

The SPaMCAST 733 features a reflection on a reflection. As I was reading Chapter 5 of (check out the re-read at ) and retrospecting on my own behavior, I replayed some past coaching experiences. The point today is less the linkage to our current re-read than the confluence of continued learning and reflection. We also have a visit from Mr. Jeremy Berriault. Jeremy and I talk about coaches who let their own biases run away with them. Re-read Saturday News This week we re-read Chapter 5 of (Amazon Associate Link - buy a copy or two and give them to friends). Chapter 5 is titled Badass Agile Coaching Arcs. Coaching and conversations are highly intertwined activities. I am at a loss as to how I would coach without actively interacting with people. I think the idea of a conversation arc is something I naturally understood or perhaps the concept percolated in my mind from sales training (haven’t I strongly suggested sales training?). The idea of an arc to a coaching conversation makes perfect sense. Previous Entries in Our Re-read: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST The SPaMCAST 734 will feature a lightly edited version of the SPaMCASTs annual holiday panel. We are going to talk about engagement and whether being engaged is as important to organizations as it is to all of us in the agile and lean consulting industry.

The SPaMCAST 732 features our interview with Robert Cooke. Robert and I discussed the role of software development in delivering value in non-software product organizations. Robert Cooke is the Founder and Principal Architect at 3Forge, a New York-based provider of data virtualization and visualization technology. 3Forge has achieved significant growth over the years as a result of increasing demand for its award-winning, web-based browser AMI platform. Today, AMI is deployed at three of the five largest global banks, and nearly 20 percent of global equities flow through the platform. 3Forge also has provided its services to hedge funds, broker-dealers, and other financial services firms. The company is the leading provider of “performance at scale” data management systems. Robert’s accomplishments have spanned electronic trading, middle and back office, regulatory reporting, compliance, and risk management. Website: LinkedIn: Re-read Saturday News This week we re-read Chapter 4 of (Amazon Associate Link). Chapter 4, Badass Agile Coaching Agreements, focuses on the need for and structure of…coaching agreements (hence the name of the chapter :)). I use coaching agreements on a regular basis. They are an excellent idea. Galen states, “My point being: never, ever coach without establishing an agreement.” Previous Entries in Our Re-read: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST The SPaMCAST 733 continues our answer to the question: if one product owner is good, aren’t two, three, or four better? We will also have a visit from Jeremy Berriault who brings his wide-ranging QA corner to the podcast.

The annual Thanksgiving holiday in the US was a few days ago providing space to reflect and give thanks to everyone involved in the 16-plus years history of the Software Process and Measurement Cast blog and podcast. There is a lot to be thankful and grateful for, this week we put the spotlight on everyone that makes the SPaMCAST possible. Also, Jon M Quigley brings his Alpha and Omega of Product Development to the podcast. Jon and I discuss the idea of flow. Re-read Saturday News This week we are taking a break from our re-read of (Amazon Associate Link). Previous Entries in Our Re-read: Week 1: - Week 2: - Week 3: - Week 4: - A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST The SPaMCAST 732 features our interview with Robert Cooke. Robert and I discuss the role of software development in delivering value.

The SPaMCAST 730 features our conversation with Ramzi Marjaba. Ramzi and I discussed the role of a sales engineer. The role solves customers' problems and is a bridge between customers and technical teams. With all that going for it, why is it a forgotten job path for people with deep technical acumen? Ramzi is an established Sales Engineer and the Founder of We The Sales Engineers and found his calling in helping people change their lives for the better, either by breaking into the difficult world of Sales Engineering or upskilling their current skill levels to get that pay raise and promotion. Contact Information Website Ramzi’s LinkedIn Profile Email Podcast Twitter Re-read Saturday News This week we re-read Chapter 3 of (Amazon Associate Link). In Chapter 3, Agile Coaching Framework, the authors create a line in the sand stating “professional badass agile coaching needs to support and model a multivariate framework that supports all aspects (stances) of our craft.” Week 4: - Previous Weeks: Week 1: - Week 2: - Week 3: - A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST The SPaMCAST 731 continues our answer to the question: if one product owner is good, aren’t two, three, or four better? We will also have a visit from Jon M Quigley who brings his Alpha and Omega of Product Development column to the podcast.

This week we go back to basics and answer a listener’s question (name and a bit of the context changed to protect the involved parties). In the essay this week we discuss why it is a rotten idea to have a functional product owner and a technical product owner. When it comes to product owners the old adage, “the more the merrier," does not hold. Also, we have an installment of Tony Timbol’s “To Tell A Story” column. In this installment, Tony discusses how to synchronize team-level agile with a waterfall requirements process. This is one of those scenarios that when you run into it you will need to find a way to deal with it until more of the organization embraces agile. Re-read Saturday News This week we re-read Chapter 2 of (Amazon Associate Link). Chapter 2, The Mindset of the Badass Agile Coach, focuses on the most important part of a coach's arsenal of superpowers: their mindset. This Week: Week 3: - Previous Weeks: Week 1: - Week 2: - A quick advertisement: Controlling work entry requires preparation and knowledge, building to establishing a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST The SPaMCAST 730 features our interview with Ramzi Marjaba. Ramzi and I discussed the role of a sales engineer and why this is a forgotten job path for people with deep technical acumen.

SPaMCAST 728 features a discussion with Anjali Leon and Nadezhda Belousova. We discussed their new model, Product Leadership Stances. One of my takeaways was how powerful the model was in helping to develop an understanding of product leadership and then highlighting gaps in how the role is practiced in organizations. Anjali and Nadezhda’s Bios! Anjali Leon is an Agility, Product, and Professional Coach, Collaboration Facilitator, and Trusted Strategic Advisor. Through her boutique coaching and consulting practice, PPL Coach, She brings her years of experience in technology, leadership, and Agile to help her clients adapt, innovate, and thrive in the new-normal business environment - where the meaning of ‘winning’ is quickly being redefined as integrating better business outcomes and our collective well-being. You can experience Anjali’s authentic head, hearts and hands approach to product, people, and personal leadership through one of her unique value-driven and values-based coaching programs, workshops, and training. Anjali is an accredited trainer through ICAgile and ProKanban, is a trained co-active coach and is a committed lifelong learner. She is recognized as an inspiring speaker, conference organizer, and community leader. She is co-creator of Product Leadership Stances™, co-founder of HitRefresh – a resilience-building practice, founder of Empowering South Florida Women in Agile, and member of the advisory board for . Anjali’s Profile Website (Company) Twitter Nadezhda Belousova is an Integral Master Coach™ and an independent Enterprise Business Agility Strategist who deeply cares about high-performing scalable businesses with human-centric approach and sustainability at heart. She brings a combination of psychology, multiple professional coaching approaches (ORSC, Solution-Focused coaching, Clean Language, etc.), years of extensive hands-on consulting experience in various industries, and a can-do-all mindset. Nadezhda sees organizations holistically as living systems and enables them to unleash their potential – to evolve, to re-invent themselves, to thrive. She runs a boutique organizational coaching and management consulting practice serving her clients worldwide from Berlin, Germany. Nadezhda is a mentor, speaker and a passionate contributor to a number of professional communities (European Organizational Design Forum, Agile Alliance, Business Agility Institute, etc.). LinkedIn https://www.linkedin.com/in/nadezhdabelousova Product Leadership Website: Re-read Saturday News This week we re-read Chapter 1 of (Amazon Associate Link). Chapter 1, , is an overview of the book including thoughts on how to read it and a whole lot more. This Week: Week 2: - Previous Weeks: Week 1: - A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST In the SPaMCAST 729 let's go back to basics and discuss why it is a rotten idea to have a functional product owner and a technical product owner. Tony Timbol will also bring his “To Tell A Story” column to the podcast.

In SPaMCAST 727 we discuss the assumptions behind Little’s Law and Neglected WIP. Some of the assumptions you can cheat to generate useful conversations but there are limits and you need to be upfront about what you are doing. We also have a visit from Susan Parente who brings her Not A Scrumdamentalist column to the cast. In this installment, Susan answers a listener's question about the complications of a team with 2 developers and 5 managers. Re-read Saturday News This week we begin our re-read of (Amazon Associate Link – buy your copy soon and start reading). This week we begin with a few notes on the logistics of the read and then review the two Forewords. Week 1: - A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Please email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST In SPaMCAST 728 we will feature our discussion of product leadership stances with Anjali Leon and Nadezhda Belousova. Developing an understanding of product leadership stances will highlight product leadership gaps and strengthen your product focus. .

In SPaMCAST 726 Mr. Allan Kelly returns! We discussed the fact that backlogs often become dumping grounds. Allan suggested an energetic solution. We also discussed OKRs and whether they are related to backlogs. Are OKRs the chicken or the egg? Allan Kelly advises and mentors managers and teams in using agile approaches and OKRs to accelerate delivery, meet deadlines and execute against strategy. He believes these approaches benefit businesses and create more fulfilling work environments. Allan is a keynote conference speaker and author of several books including "Succeeding with OKRs in Agile", "The Art of Agile Product Ownership" and "Business Patterns for Software Developers". He blogs at and can be contacted there or on Linkedin, Re-read Saturday News We complete our re-read of the classic this week with a few final thoughts. I view as a tale of two themes. The first is a book of philosophy and the second is a how-to book full of techniques. The full value of this book requires two readings. The first time I read the book, I took the how-to path. This time the philosophies of agile coaching were more important to me than any individual technique. Next week we start our re-read of (Amazon Associate Link – buy your copy soon and start reading). This will be less of a re-read than it will be me trying to stay one or two chapters ahead because I am reading the book for the first time. We will begin with a few notes on the logistics of the read and then we will review the front matter. Previous Installments Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Week 8: r - Week 9: - Week 10: - Week 11: - Week 12: Week 13: - Week 14: - A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. Interested? Email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST In SPaMCAST 727 we will discuss the assumptions behind Little’s Law and Neglected WIP. Some of the assumptions you can cheat on and still get valuable information. We will also have a visit from Susan Parente who brings her Not A Scrumdamentalist column to the cast.

One of the most common problems teams face is starting more work than they complete. Neglected WIP is the gap between all the work you say you are working on and the stuff you are doing. The natural vagaries of office life can cause an item to get stuck due to someone being out sick or because your co-worker hit the lottery - stuff happens. A little might be ok, but more is bad. When neglected WIP passes that hurdle, real flow time will increase and velocity will slow. The combination of getting less work done and taking longer at it is a prescription for your stakeholders to start looking for torches and pitchforks. We also have a visit from Jeremy Berriault who brings his QA Corner to the podcast. In this installment, we discussed the QA Lead’s role in agile teams. So just what does a QA Lead do in an agile team . . . Jeremy has some ideas. Re-read Saturday News I am going to combine the conversation of Chapters 12 and 13 of this week because there is a common core in these two chapters. Chapter 12, When Will I Get There?, discusses when will you know that you have become an Agile Coach, and Chapter 13, It’s Your Journey, discusses the journey several coaches have taken to get there. Chapter 12 plots the journey and Chapter 13 provides several travelogues. Remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line ) and read along! Logistics Note: Next week we will wrap up Coaching Agile Teams and then on to (Amazon Associate Link – buy your copy soon and start reading). Buy a copy now and start reading. Previous Installments Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Week 8: r - Week 9: - Week 10: - Week 11: - Week 12: Week 13: - A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. We recently delivered the workshop at the 2022 Path to Agility in Columbus, OH to rave reviews. Interested? Email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST In SPaMCAST 726 we will chat with Mr. Allan Kelly. I missed talking to Allan so we covered a wide range of topics including OKRs, Product Backlogs, and remote working. Allan brings incredible insight to the podcast.

This week we feature an interview with Indus Khaitan, Founder & CEO at Quolum. A few of the topics covered include: Why do organizations need help in consuming SaaS at scale efficiently? How can looking carefully at how you are using Saas save organizations tons of money? How can organizations refocus on delivering value rather than on overhead? What does it take to take a vision and make it a going concern, more than once? Indus Khaitan is the founder of Quolum. Quolum helps companies manage their SaaS spend. He started Bitzer Mobile, a mobile security startup that Oracle acquired. Earlier, he led growth at Chargebee. He lives in the San Francisco Bay Area. Indus’ Profile: Websites: (AngelList Profile) (Company) Email: khaitan@gmail.com Twitter: Podcast: Re-read Saturday News This week we reread Chapter 11 of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate link ). Chapter 11, Agile Coach Failure, Recovery, and Success Modes, begins Part 3 of Coaching Agile Teams. Part 3 titled “ Getting More for Yourself.” Chapter 11 hits the topic of failure head-on, sharing both failure and success modes. Anyone that has been in the business of agile coach (coach, Scrum Master, manager, or others) for more than a few years and has pushed the boundaries of culture will have failures on their CV. Coaching is hard, training and continuous learning are important but not enough. A coach without experience is a trainee. A wide range of experience, which opens the door to successes and failures, is a learning opportunity that classes and webinars can’t deliver. Remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line ) and read along! Logistics Note: We will combine the discussion of the last two chapters in this book and then follow that with a recap before starting. (Amazon Associate Link – buy your copy soon and start reading). Buy a copy now and start reading. Previous Installments Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Week 8: r - Week 9: - Week 10: - Week 11: - Week 12 A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. We recently delivered the workshop at the 2022 Path to Agility in Columbus, OH to rave reviews. Interested? Email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST In SPaMCAST 725 we delve deeper into the concept of neglected WIP highlighting the calculation and a quick case study’ette so you can see the concept in action. We will also have a visit from

SPaMCAST 723 features our essay on neglected WIP. Work that has been started and is now just sitting around is neglected. Running a team or organization above their natural level WIP for any length of time causes flow velocity (throughput) to slow and flow time (cycle time) to increase. When there is too much work, people try all sorts of techniques to get work done. Multitasking is the grandfather of them all and we all know how that turns out (need a hint – badly). In the end, all approaches to trying to do too many ends up with some things being juggled and ignored. That is neglected WIP. We also have a visit from Jon M Quigley and his Alpha and Omega of Product Development Column. In this column Jon and I discuss time. Speaking of time, this is a lost episode…we started the episode discussing snow, last year's snow. We talked last week and were discussing when the first snow will be this year. Sometimes time flys and sometimes it doesn’t. Re-read Saturday News This week we reread Chapter 10 of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate link ). The chapter is titled Coach as Coordination Conductor. The two most important items for me during this read of chapter 10 are found in the first part of this chapter. Reflecting back on my previous cover-to-cover read, I think that the number of great facilitation techniques in this chapter caused me to overlook two very important concepts. The first is an approach for differentiating collaboration and coordination. The approach is simple but very powerful. Why would any coach care about observing the difference? Because the two concepts are different and are useful in different scenarios. Logistics Note: We have three more chapters in this book which we will follow with a recap before starting. (Amazon Associate Link – buy your copy soon and start reading). Buy a copy now and start reading. Remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line ) and read along! Previous Installments Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Week 8: r - Week 9: - Week 10: - A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. We recently delivered the workshop at the 2022 Path to Agility in Columbus, OH to rave reviews. Interested? Email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Next week we will feature an interview with Indus Khaitan, Founder & CEO at Quolum. Indus and I talked about SaaS, controlling SaaS spending, and serial entrepreneurship.

We are back with new content this week! The bears did not eat us as we trekked in three national parks. We did see bears but kept a respectable distance from them. Today the SPaMCAST 722 features an interview with Scott Showalter, Agile Career Accelerator. We discussed the definition of an agile coach. Building on that definition we wrestled with how to scale the business of agile coaching. Note - I mispronounced Scott’s name at the beginning of the interview, rather than re-record the faux pax, it triggered a great story so I left it in. Scott is an active enterprise agile coach working in the trenches with execs and leaders at a Fortune 10 organization, and what he has learned throughout the journey of his career is that what feels impossible only becomes achievable once we shift our perspective. Scott has a passion for helping people design, grow and automate their products and their lives so that they can focus on what's truly important and have a greater impact on this planet. He coaches IT professionals and entrepreneurs on income growth and career advancement, and on the weekends he has been known to perform laugh-out-loud stand-up comedy. Scott’s LinkedIn Profile Website (Personal) Twitter Re-read Saturday News During the last few weeks, I have read and reread Chapter 9 of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate link ). The chapter titled Coach as Conflict Navigator talks about the value and danger of conflict. What stuck with me was the model of levels of conflict and how at a certain point there can be no constructive outcome. Teams aside, scary thoughts for the world we live in. Remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line ) and read along! Previous Installments Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Week 8: r - Week 9: - Week 10: - A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. We recently delivered the workshop at the 2022 Path to Agility in Columbus, OH to rave reviews. Interested? Email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Next week SPaMCAST 723 will feature an essay on neglected WIP. Work that has been started and is now just sitting around is neglected. We will also have a visit from Jon M Quigley and his Alpha and Omega of Product Development Column.

The SPaMCAST is on a three-week hiatus. We will be back with new programming on September 25. In the interim, I asked the SPaMCAST columnists (Jeremy, Jon, Susan, and Tony) for a couple of favorite columns they delivered. Today we have: Jeremy Berriault from SPaMCAST 571 Jiu-Jitsu and Teams, Want to listen to the full podcast? Susan Parente from SPaMCAST 556 Agile In Name Only, Want to listen to the full podcast? Tony TImbol from SPaMCAST 692 Agile Requirements, Want to listen to the full podcast? Enjoy! Do you have questions that you would like Susan, Jon, Jeremy, Tony, or myself to answer? Leave a voice message at 01.440.668.5717 or an email at . Re-read Saturday News I am packaging this show well ahead of time therefore all I can say for sure about the re-read is to remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate link ) and read along! A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. We recently delivered the workshop at the 2022 Path to Agility in Columbus, OH to rave reviews. Interested? Email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Next week we are back…unless bears have eaten me (I've been hiking in the Rockies). SPaMCAST 722 will feature an interview with Scott Showalter, Agile Career Accelerator. We discussed the definition of an agile coach. Building on that definition we wrestled with how to scale the business of agile coaching.

The SPaMCAST is on a three-week hiatus. We will be back with new programming on September 25. In the interim, I asked the SPaMCAST columnists (Jeremy, Jon, Susan, and Tony) for a couple of favorite columns they delivered. Today we have: Jon M Quigley - SPaMCAST 397 – Project Strategy - Want to listen to the full podcast? (Note: this was Jon’s debut column and he doesn’t know I am slipping this in.) Susan Parente and Jon M Quigley- SPaMCAST 585 - Most Agile Transformations Ignore Technical Skills - Want to listen to the full podcast? Enjoy! Do you have questions that you would like Susan, Jon, Jeremy, Tony, or myself to answer? Leave a voice message at 01.440.668.5717 or an email at . Re-read Saturday News I am packaging this show well ahead of time therefore all I can say for sure about the re-read is to remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line ) and read along! A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. We recently delivered the workshop at the 2022 Path to Agility in Columbus, OH to rave reviews. Interested? Email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Next week we feature more of Jeremy Berriault, Susan Parente, and Tony Timbol.

The SPaMCAST is on a three-week hiatus. We will be back with new programming on September 25. In the interim, I asked the SPaMCAST columnists (Jeremy, Jon, Susan, and Tony) for a couple of favorite columns they delivered. Today we have: Jeremy Berriault - Your Scrum Master Is Not Yout Team Admin from SPaMCAST 705 Want to listen to the full podcast? Tony Timbol - Agile Requirement Lifecycle from SPaMCAST 709 - Want to listen to the full podcast? Susan Parente - Virtual Agile from SPaMCAST 589 - Want to listen to the full podcast? Enjoy! Do you have questions that you would like Susan, Jon, Jeremy, Tony, or myself to answer? Leave a voice message at 01.440.668.5717 or an email at . Re-read Saturday News I am packaging this show well ahead of time therefore all I can say for sure about the re-read is to remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line ) and read along! A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. We recently delivered the workshop at the 2022 Path to Agility in Columbus, OH to rave reviews. Interested? Email us at tcagley@tomcagley.com or willetsjm@gmail.com Next SPaMCAST Next week we feature Jon M Quigley and Jon and Susan Parente together (a Jon and Susan-polza?)

Earlier this year I attended Agile 2022; It was a fantastic conference. One of the undercurrent themes was the use of OKRs (objectives and key results for the uninitiated) to enable agility, align organizations, and cure Covid. There is no such thing as a silver bullet, especially with the wide range of interpretations of what an OKR is and how to apply them. Luis Gonçalves retunes to the podcast to set us straight. Luis’s Bio Luis Gonçalves is an Entrepreneur, Best Seller Author, and International Keynote Speaker. When consulting he works exclusively with Entrepreneurs, Founders, and Senior Leaders on the implementation of his game-changing "ADAPT Methodology". By following the "ADAPT Methodology" Executive Leaders will be able to transform their traditional project-oriented companies into modern digital product companies. OKR Guide: Website: Website: Podcast: https://adaptmethodology.com/podcast/ LinkedIn: Re-read Saturday News This week, Chapter 7 of by Lyssa Adkins. While observing and facilitating might be the most prolific coach activities, at times teaching takes front and center. Teaching encompasses a wide range of behaviors, but the goal is always the same - to elevate the person or team you are teaching. Teachers are there to help PEOPLE to become better at something. Remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line ) and read along! Previous Installments Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Week 8: r - A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available), which is why Jeremy Willets and I have developed a work entry workshop. We recently delivered the workshop at the 2022 Path to Agility in Columbus, OH to rave reviews. Interested? Email us at tcagley@tomcagley.com or willetsjm@gmail.com Do you have questions that you would like Susan, Jon, Jeremy, Tony, or myself to answer? Leave a voice message at 01.440.668.5717 or an email at . Next SPaMCAST The SPaMCAST will be on a three-week hiatus. We will be back with new programming on September 25. In the interim, I asked the SPaMCAST columnists (Jeremy, Jon, Susan, and Tony) for a couple of favorite columns they delivered. For the next three weeks, we will serve you the best of the best.

Flow Load has a special place in flow metrics, it is a leading indicator of value delivery as exhibited in flow velocity (throughput) and flow time. We review one experiment and propose another. In the end, you either control work entry or it controls you. A quick advertisement: Controlling work entry requires preparation and knowledge building to establish a path to control work entry (magic wands are normally not available) which is why Jeremy Willets and I have developed a work entry workshop. We recently delivered the workshop at the 2022 Path to Agility in Columbus, OH to rave reviews. Interested email us at tcagley@tomcagley.com or willetsjm@gmail.com Also this week we are joined by Tony TImbol and his To Tell A Story column. In this installment, Tony focuses on the impact of delayed requirements on agile teams. Do you have questions that you would like Susan, Jon, Jeremy, Tony, or myself to answer? Leave a voice message at 01.440.668.5717 or an email at . Re-read Saturday News Chapter 6 of is titled Coach as Facilitator. As a coach, I suspect I spend more time facilitating and observing than playing any other sub-role. Chapter 6 provides a number of gems that piqued my interest more during this read than in the first. Remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line ) and read along! Previous Installments Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Week 7: - Next SPaMCAST SPaMCAST 718 features our most recent discussion with Luis Gonçalves. Luis and I talked about OKRs. We will cover the gamut; the good, the bad, and the OMG they’ve turned into annual reviews all in one session! Luis last appeared on the cast in .

This week Jeff Perry and I discussed learning how to consciously guide your technology career. We are all problem solvers, and Jeff provides a ton of hard-won advice. We also wrestled with the difference between a series of jobs and a career. Jeff’s Bio: Jeff Perry is the founder of More Than Engineering and serves as a leadership and career coach for engineers and technology professionals. His innovative programs and coaching help people take a mindful, intentional, and purposeful approach to career transitions, leadership, and personal development goals. Listeners of the SPaMCAST can find some free resources including the Career Clarity Checklist at . They can also find and follow Jeff on LinkedIn at . Do you have questions that you would like Susan, Jon, Jeremy, Tony, or myself to answer? Leave a voice message at 01.440.668.5717 or an email at . Re-read Saturday News Chapter 5 begins Part 2 of and is titled Coach as Coach-Mentor. During my initial reading of this book, I found Part 2 the most immediately useful. During this re-read, I reflect less on techniques to engage people and teams and more on engagements that I have had and where my remit and my behavior took me off track. Remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line ) and read along! Previous Installments Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Next SPaMCAST SPaMCAST 717 we will focus on why Work in Process, flow load, is the leading indicator of flow metrics. We will also be joined by Tony TImbol who brings his To Tell A Story column to the podcast.

A funny thing happened on the way to the essay this week. I was distracted by feedback from a colleague on a workshop Jeremy Willets and I developed and delivered this week. We discuss why the phrase work entry describes how work gets to teams and organizations, and why “work intake” masks problems in the real world. We also have a visit from Susan Parente and her Not A Scrumdamentalist column. This month Susan answers a listener's question about whether it makes sense for a Scrum Master to also play other roles on a team. Do you have questions that you would like Susan, Jon, Jeremy, Tony, or myself to answer? Leave a voice message at 01.440.668.5717 or an email at . Re-read Saturday News Chapter 4 of , discusses the idea that a team, individual, or organization follows a path from a learner to mastery to a teacher using the Shu Ha Ri metaphor. The concept of Shu Ha Ri represents a continuum of learning. In martial arts or any demonstrable activity, practitioners must learn and practice before they can take the next step forward. Carol Dweck, in her book Mindset, postulated that even the most gifted athletes need an open mindset to succeed in the long run. To progress across the continuum of learning everyone needs to put in the work. I suspect that for many, the Shu state is the hardest to accept because we all want to believe we are special and we are all impatient to meet the prize of mastery. Remember to buy a copy of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line ) and read along! Previous Installments Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Next SPaMCAST The SPaMCAST 716 features our interview with Jeff Perry. Jeff and I talked about consciously guiding a career in technology. We also wrestled with the difference between a series of jobs and a career. Jeff delivers a ton of hard-won advice.

Today Jonathon Wright will shift us…right? After decades of listening to the mantra shift left, you probably think you are entering the twilight zone. Maybe, but not on our account! Jonathan and I talked about putting customers first, testing AI, quality, and leadership. is the Chief Technology Evangelist and heads up Solution Engineering (R&D) for Eggplant a company. He is a strategic thought leader and distinguished technology evangelist. He specializes in emerging technologies, innovation, and automation, and has more than 25 years of international commercial experience within global organizations. Jonathon combines his extensive practical experience and leadership with insights into real-world adoption of Cognitive Engineering (Enterprise A.I. and AIOps). Thus, he is frequently in demand as a speaker at international conferences such as TEDx, Gartner, Oracle, AI Summit, ITWeb, EuroSTAR, STAREast, STARWest, UKSTAR, Guild Conferences, Swiss Testing Days, Unicom, DevOps Summit, TestExpo, and Vivit Community. Jonathon also hosts the QA lead (based in Canada) and is the author of several award-winning books (2010 – 2022) the latest with Rex Black on ‘AI for Software Testing. Podcast: LinkedIn: Twitter: @Jonathon_Wright Webpage: Upcoming Events Jeremy Willets and I have been accepted as speakers for this year’s Path to Agility! Our workshop is titled “Managing Work Entry: How the Mushy Middle is Killing Your Agility.” I’m very excited to be part of this wonderful conference and hope to reconnect with long-time colleagues at a fabulous venue — The Ohio Union at The Ohio State University. See you soon Columbus! August 1 - 2 in Columbus, Ohio Register Today: Re-read Saturday News I am still recovering from a Covid infection I picked up at or getting to Agile 2022. All in all I have been lucky (and prepared) and have weathered a mild brush with this disease. My chest still feels like I was mugged, but every day I am getting better. The lack of self-awareness that I was getting sick until things were full-blown is fairly startling. It was more startling when I was re-reading Chapter 3 of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line - buy a copy) again this week in preparation to write this essay. Previous Installments Week 1: - Week 2: - Week 3: - Week 4: - Next SPaMCAST We will map the attributes of flow explored in SPaMCAST 708 to a basic palette of flow metrics. This will complete the circle defining flow, establishing basic attributes, and then identifying how to measure flow through its attributes. We will also have a visit from Susan Parente who will bring her Not A Scrumdamentalist column to the cast!

Today’s cast is a very short podcast. Over the past week, I spent an amazing week at Agile 2022. My goal was to be re-radicalized. I reconnected with friends, made new friends, learned a new set of personal pronouns (while not for me, they really work well), picked up a bunch of swag, learned a ton, got re-energized and re-radicalized, and got Covid19. I could have done without the latter. I will get better, but right now it is moving up on my personal least fun thing to do list. I told Jeremy Berriault (you will hear from him later) that Covid is somewhere between the sixth and seventh least fun thing I've ever been involved with. It was a solid #7 yesterday. With luck, things will be back to normal soon. All that aside, the money shot presentation (for me) was given by Bethany Andres-Beck, titled “A Radical Culture of Culture Building.” Zie rocked it. The combination of small group influencing techniques combined with anarchist meeting design, community activism from the civil rights era, and the women’s movent was simply brilliant. Better yet, none of it was pie in the sky theory but the relating of an experience report. I need to talk hir into appearing on the podcast. This presentation was worth the price of admission for me. I will share more in the near future. This week we return to the QA Corner with Jeremy Berriault to discuss who is responsible for quality. In many organizations quality is on QA’s shoulders, should it be? Upcoming Event Jeremy Willets and I have been accepted as speakers for this year’s Path to Agility! Our workshop is titled “Managing Work Entry: How the Mushy Middle is Killing Your Agility.” I’m very excited to be part of this wonderful conference and hope to reconnect with long-time colleagues at a fabulous venue — The Ohio Union at The Ohio State University. See you soon Columbus! August 1 - 2 in Columbus, Ohio Register Today: Re-read Saturday News We WILL be back next week barring any catastrophes. Remember to buy a copy of and read along. Previous Installments Week 1: - Week 2: - Week 3: - Next SPaMCAST Next week we will feature our interview with Jonathan Wright. Jonathan and I will discuss shifting right. If, after decades of listening to the mantra shift left, you just experienced whiplash, I understand.

Jim Benson has a new book titled, The Collaboration Equation. Jim states that collaboration “is the base of the human condition, we need other people in order to live, but always seem to be at odds with each other.” Jim also states that unless you are striving for improvement, you are unprofessional. I really like talking to Jim; Jim is a force of nature. Jim’s career path has taken him through government agencies, Fortune 10 corporations, and start-ups. Through them all, his passion has remained consistent – applying new technologies to workgroups. In each case asking how they can be leveraged to collaborate and cooperate more effectively. Jim loves ideas, creation, and building opportunities. He loves working with teams who are passionate about the future, pushing boundaries, and inclusion. His goal with all technologies is to increase beneficial contact between people and reduce the bureaucratic noise which so often tends to increase costs and destroy creativity. Jim is the author of the Shingo Research Award-winning book (use the link to buy a copy and support the podcast). He is a noted expert in business process, personal work management, and the application of Lean to personal work and life. Jim believes that the best process is the least process necessary to achieve goals. He has zero tolerance for process waste. All said, Jim enjoys helping people and teams work out sticky problems, an advocate of people actually seeing their work, and inventing new ways to work at the intersection of Lean thinking, brain science, and leadership. Contact Jim Twitter: LinkedIn: Personal Kanban: Modus Cooperandi: Re-read Saturday News We are talking the week off on our re-read Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line - buy a copy). I was traveling to Nashville for Agile 2022 (let me know if you are here). Next week we will be back on track but in the interim remember to buy a copy of and read along. Previous Installments Week 1: - Week 2: - Week 3: - Next SPaMCAST We will map our basic flow metrics palttet a simple organizational hierarchy. Some metrics tell us where we were and some tell us where we are going. This essay reflects work that Jeremy WIllets and I are exploring. We will also have a visit from Jeremy Berriault who brings his QA Corner to the Software Process and Measurement Cast.

This week we make a quick side trip. Earlier this week I was asked why I “did” the Re-read Saturday column. Today, I offer a short explanation and highlight the experiments I am running as part of our re-read of . We also have a visit from Jon M. Quigley. In this installment of his Alpha and Omega of Product Development, Jon and I discuss the role of the team lead in agile teams that have coaches, scrum masters, and just might be self-organizing. There is a role but it is not the classic version that is in common use. Why Do I “Do” Re-read Saturday. Re-read Saturday is a long-running column featured on my blog (tcagley.wordpress.com) and at tomcagley.com. The books selected for the column are nominated and then voted on by readers. Because most books are selected by the acclaim from readers of the blog, the re-read is sometimes actually the first read for me. During the re-read we read, discuss, and highlight concepts chapter by chapter. There are three major reasons for the column. One, the column draws eyes. A blog without readers is a diary. Over the years, many of the top 10 annual posts have been from the re-read feature. A second reason, and perhaps the original reason was that I had not read some of these books before and really needed to read them. For some of the other books we have re-read, the re-read drove home the point that memory erodes over time. For example, I am embarrassed to say I had forgotten the story of Herby (check out the re-read of The Goal). Reason two is that the re-read is a forcing function to guide behavior. The books we read and re-read help shape how we behave. The third reason is that the column generates a lot of interaction. I have heard from readers and authors with ideas and opinions. The interactions have certainly improved my understanding of how work is done and how to improve. The level of interaction suggests that the readers get similar benefits. Recently, I decided to run weekly experiments based on the chapter I am reading. The weekly experiment is another forcing function. Doing the activity drives home a point so it is harder to forget. For example from the re-read of Chapter 2 of Coaching Agile Teams by Lyssa Adkins titled Expect High Performance I am focusing on using metaphors to guide behaviors. As an experiment, I am establishing a metaphor for myself. The goal is to see whether having a metaphor changes my behavior. The concept of the weekly experiment might end up being the best reason for me to “do” Re-read Saturday and perhaps the best reason for you, the reader, to participate. PS -- I am not convinced that the person that asked was really looking for this much information. I actually think they we asking why read books at all when you watch videos which lead us to a different discussion which I will share another day. Finally, have you downloaded the book referenced in last week's interview? Check out Seeing Money Clearly at Re-read Saturday News This week, Chapter 2 of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line - buy a copy). The chapter’s title is Expect High Performance. As a coach, you need to have high expectations of yourself and those you are coaching. Remember to buy a copy of and read along. Previous Installments Week 1: - Week 2: - Week 3: - Next SPaMCAST Jim Benson has a new book titled, The Collaboration Equation. The first sentence in the description of the book is: “It is the base of the human condition, we need other people in order to live, but always seem to be at odds with each other.” We went from there,

Daniel Doiron's new book Seeing Money Clearly challenges Agile Centers of Excellence to view decision-making through the lens of Throughput Accounting. Throughput Accounting is a lot of things: An accounting system, A financial application, A process of ongoing improvement (POOGI), and First and foremost, the decision-making arm of the Theory of Constraints. Daniel’s Bio “I am the only CPA in the world - negative assurance provided - to give a one-day Throughput Accounting class to a CPA chapter (Québec) within the scope of their mandatory Professional Development Program. A few CPA chapters in the world give diluted Throughput Accounting classes in a recorded format and ignore the Five Focusing Steps, thereby disqualifying them from the spirit of Throughput Accounting”, states Doiron. “For Agile CoEs (Center of Excellence), I wrote the only Throughput Accounting book dealing exclusively with Knowledge Work. It has received rave reviews from the top minds in Throughput Accounting as I have brought numerous novelties never thought of before.” In short, Seeing Money Clearly: Teaches CPAs how to make more money now and in the future. Teaches Agile CoEs how to mint money. Download Seeing Money Clearly at and reach out at daniel_doiron@hotmail.com and on Twitter @AgileAgonist Re-read Saturday News This week, Chapter 1 of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line - buy a copy). The chapter tackles more than just the question embedded in the title exploring why a coach is needed, the path to becoming a coach, and both the mindsets and skills a coach needs. Read all of Week 1’s entry and next week we will cover Part 1, Chapter 1: Will I Be A Good Coach. Remember to buy a copy of and read along. Previous Installments Week 1: - Week 2: - Next SPaMCAST We will map the attributes of flow explored in SPaMCAST 708 to a basic palette of flow metrics. This will complete the circle defining flow, establishing basic attributes, and then identifying how to measure flow through its attributes. We will also have a visit from Jon M. Quigley who brings his Alpha and Omega of Product Development to the cast!

Definitions provide several benefits. The first is that once a definition for an object or concept is agreed upon, it is far easier to have a discussion without getting confused. A second and equally important benefit is that definitions provide a platform for establishing attributes that can be used to describe the object or idea. Attributes are critical because even with a definition we need to communicate and measure nuances. Just think if you only had one word to describe rain or hot; a lot would be lost. Today we identify four basic attributes of flow. We will also have a visit from Tony Timbol who brings his “To Tell A Story” column to the podcast. In this installment, Tony and I talk about agile requirements. They really exist…really! Re-read Saturday News This week we began our re-read of Coaching Agile Teams by Lyssa Adkins (SPaMCAST Amazon affiliate line buy a copy). I am re-reading my Kindle version of the book. The front matter includes Forwards by Mike Cohn, Jim Highsmith, Acknowledgments, Introduction, and a section titled, About the Author. The main body of the book is in three parts comprised of 13 chapters. It is indexed -- useful for reference books! I estimate 16 or 17 weeks to complete the re-read depending on my travel. Note: The Kindle edition of the book has not been updated and will not run on the Paperwhite Version 10 models, so we will re-read it on the iPhone and Laptop -- I did not have a happy chat with Kindle support on this issue. Wake up, Addison Wesley! Read all of Week 1’s Entry and next week we will cover Part 1, Chapter 1: Will I Be A Good Coach. Remember to buy a copy of and read along. If you are still catching up on the re-read of are are all of the links”: Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: s - Week 8: - Week 9: - Week 10: - Week 11: - Week 12: - Next SPaMCAST Daniel Dorion returns to the podcast next week to talk about his new book, Throughput Accounting - Seeing Money Clearly. Daniel begins the Prologue of his new book with the statement “My aim is to have you think differently and lose your reflexes and cognitive biases that are the fabric of society.” You will have a lot to think about after you listen!

107 podcasts ago (just a little over two years ago) on I interviewed Brian Weaver of Torch.AI about leadership. Lots of things have happened since then, a pandemic, Europe in flames again and Torch.AI thriving. It was great to touch base with Brian to talk about how his perspective as a leader has changed. While not needed for this interview, I highly recommend listening to either before or after. Brian serves as CEO of Torch.AI and has more than 20 years of experience leading mission-driven, high-growth, technology-focused companies. Torch.AI helps leading organizations leverage artificial intelligence in a unique way via a proprietary enterprise data management software solution. Today, Torch.AI supports clients like H&R Block with fraud detection and mitigation and the U.S. Department of Defense with machine learning-enabled background investigations for all federal employees, supporting the determination of an individual’s trustworthiness and security credentialing. LinkedIn: Torch.AI – Re-read Saturday News Completing a re-read is always bittersweet. Today we say goodbye to a friend, . The final chapter is the Epilogue and interwoven are our final notes. Next week we lay out the logistics for our re-read of Coaching Agile Teams by Lyssa Arkins . Remember to buy a copy and read along. Amazon Affiliate LInk: Previous Entries Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: s - Week 8: - Week 9: - Week 10: - Week 11: - Week 12: - Next SPaMCAST Everyone has a set of attributes they use to describe and measure flow. Let's narrow the field to the most important few and start from there. We will also have a visit from Tony TImbol and his To Tell A Story Column.

In SPaMCAST 707 Susan Parente and I discuss the difference between leadership and management in her Not A Scrumdamentalist column. These two concepts are related but not the same. The votes are in! The next three books for Re-read Saturday are: Coaching Agile Teams by Lyssa Arkins Extraordinarily Badass Agile Coaching by Bob Galen Team Topologies by Matthew Skelton, Manuel Pais, and Ruth Malan Re-read Saturday News This week, we are revisiting (and re-editing) the conclusion of the first re-read to tide you over to the completion of Why Limit WIP. I have been backpacking, glamping, and visiting my father for the past eight days. That in its own right would not have precluded completing our re-read, but I also forgot the power cord for my laptop. Next week we will conclude our re-read of . Remember to buy a copy and read along. Amazon Affiliate LInk: Previous Entries Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: s - Week 8: - Week 9: - Week 10: - Week 11: - Next SPaMCAST Brian Weaver returns to the Software Process and Measurement Cast to discuss the impact of AI on business, leadership, and development.

SPaMCAST 706 features a conversation with Tom Henricksen. Tom makes a strong case that ignoring soft skills will limit your ability to deliver real value. Tom says, "Humans Are Hard, Code Is Easy." Tom’s Bio: Tom Henricksen is a problem-solving technology professional. He has worked in various roles in technology for over twenty years. Tom has learned how to solve challenging issues in technology and lead technical teams. He can help you develop those skills too! URL: LinkedIn: Twitter: @tomhenricksen Re-read Saturday News The bottom line to Chapter 10 of is simple (assuming you have been re-reading along): too much WIP interferes with learning. Without the time or inclination to experiment, the best scenario is learning by accident. In Chapter 10, the author discusses how knowledge workers learn. Remember to buy a copy and read along. Amazon Affiliate LInk: Previous Entries Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: s - Week 8: - Week 9: - Week 10: - Week 11: - Next SPaMCAST In SPaMCAST 707 it is back to flow basics with a discussion of the attributes of flow. Scott Ambler described two attributes of flow as smoothness and scent. We will discuss. We will also have a visit from Susan Parente who will bring her Not A Scrumdamentalist column to the podcast.

In the SPaMCAST 705 we stay with the basics and define the term flow. I recently listened to a conversation where the term flow was used 30ish times in 30 minutes. Each use of the term meant something different. Today we draw a line in the sand to improve communication. We also have a visit from Jeremy Berriault from the QA Corner. Jeremy and I discussed the mistaken belief that Scrum Master and Coach can be translated to administrative assistant. Re-read Saturday News In Chapter 9 of , the author extols the virtues of transparency. The Kanban board provides a platform for everyone (I am not being hyperbolic) to understand how much work is in process. Remember to buy a copy and read along. Amazon Affiliate LInk: Previous Entries Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: s - Week 8: - Week 9: - Week 10: - Next SPaMCAST In SPaMCAST 706 we have a visit from Tom Henricksen. We walked about programmers and soft skills… like communication. As Tom says, "Humans Are Hard, Code Is Easy."

In the Software Process and Measurement Cast 704, we talk leadership with Stuart Leo Founder & CEO of Waymaker.io. One of the reasons I enjoy interviews is that I often stumble across great stories. Stuart’s entrepreneurial origin story includes golf balls, icy Tasmanian lakes, and scuba divers -- I will remember this story until I die. Stuart is a global thinker in strategy, systems, and leadership development. As the founder of Waymaker.io he has led the creation of Waymaker’s Leadership Curve - a revolutionary way of building clarity, alignment, and remarkable results for any organization. LinkedIn Company Website Blog Twitter @stuartleo Re-read Saturday News This week’s chapter of opens with a quote from The Dalai Lama linking effective self-discipline with awareness of consequences. The chapter, titled Awareness, speaks to me of redemption. Awareness is a precursor to shedding helplessness and ignites the desire to act. I have spent a large part of my career participating, influencing, and/or leading change. Struggle is a common thread in nearly all of these efforts when entrenched leaders push back against ideas that bubble up from teams or other levels of the organization. Whether from fear or myriad other reasons, there are consequences for everyone involved. Learned helplessness, as noted in Chapter 7, or a dawning awareness that there are other possibilities creates an impetus for change. Whether change creates better processes, products, relationships, or changes in the workforce (that means people leaving) boils down to agency. Remember to buy a copy and read along. Amazon Affiliate LInk: Previous Entries Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: s - Week 8: - Next SPaMCAST In the SPaMCAST 705 we define the term flow. I listened to a conversation last week. The term flow was used 30ish times in 30 minutes. Each use of the term meant something different. Let's draw a line in the sand to improve communication. We will also have a visit from Susan Parente who brings another fabulous installment of Not A Scrumdamentalist to the podcast.

In the Software Process and Measurement Cast 703, we wrestle with one of the basics of agile. What is the power of making a commitment? Making and keeping commitments are core components of professional behavior. It is a promise to perform. Whether Agile or Waterfall, commitments are used to manage software projects. They are used to drive the behavior of teams. We also have a visit from Jon M Quigley who brings his Alpha and Omega of Product Development column to the podcast. Re-read Saturday News Chapter 7 is one of my favorites in . One of the chronic problems I help teams deal with is the perceived need to start everything that comes to them, generating huge amounts of WIP. Many of the items sit in an on-hold status until something else happens. The iron-willed self-discipline of starting is great at creating on-hold items and crap at getting work done. There is a gap in understanding the impact of the consequences. Remember to buy a copy and read along. Amazon Affiliate LInk: Previous Entries Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: s - Week 8: - Next SPaMCAST In the SPaMCAST 704, we talk leadership with Stuart Leo Founder & CEO at Waymaker.io. Leadership is incredibly important and requires constant attention.

In SPaMCAST 702, Matthew Stibbe and I talk about the impact of leadership when building a technology-driven business. Mathew shared stories about learning to type, how he has reinvented himself numerous times, and why he blogs at . Note: I have not edited out the parts of the interview just before I welcome Matthew to the podcast. Mr. Stibbe told a couple of very endearing stories that help set the tone for the entire interview. He agreed to allow me to share them. MATTHEW STIBBE is a serial entrepreneur, marketing maven, writer, pilot, and wine enthusiast. But not necessarily in that order. He created marketing strategies, content, and campaigns for clients including Microsoft, Google, LinkedIn, and HP and contributed to Wired, Forbes, and Popular Science. Currently, he is CEO at Articulate Marketing, a UK marketing agency specializing in the technology sector. Also, his geek credentials are strong. Previously, he was founder and CEO at Intelligent Games, a 70-person computer games company where he designed games for LEGO and produced two games based on Dune. Matthew also has his commercial pilots license and an advanced wine diploma. (Have you seen the film Somm? Like that!) At some point in the previous millennium, he studied history at Oxford University. These days, he blogs about modern management at www.geekboss. com, about marketing at www. articulatemarketing.com and wine at www.vincarta.com Re-read Saturday News This week, we talk about Healthy Constraints in . Many years (think decades) ago a friend of mine, Danny Bailus, had a cool mini-bike. He rode it around our neighborhood in Howland, Ohio all summer. It was the third coolest (text me the first two) thing that held my attention that summer. That was until Danny decided that it did not go fast enough and removed the governor from the small engine. He removed the constraint from the system and the engine burned out. His father was not very happy, Danny was not very happy, and I was very happy I was not riding it when it happened. In this chapter, Mr. Benson discusses the difference between healthy and unhealthy constraints. Remember to buy a copy and read along. Amazon Affiliate LInk: Previous Entries Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Week 7: s - Next SPaMCAST We continue on the basics with an essay on Teams and team design. We will also have a visit from Jon M Quigley who will regale us with tales of the Alpha and Omega of Product Development.

With SPaMCAST 701 we go back to basics. Whether you call that quick meeting to coordinate the day the Daily Scrum, Stand-up, or a huddle is not material. Daily coordination is phenomenally powerful and useful unless it isn’t. Just making teams meet without benefit is a really bad idea. What else can be done? We also have a visit from Tony Timbol with another installment from his Tell A Story Column. In this installment, Tony discusses agile requirements. Getting work done in agile is not just user stories and a cloud of dust. Re-read Saturday News The chapter of this week is titled, Creating An Economy. In the past decade, certain words have become toxic. Words like process, waterfall, and output have become taboo in certain corners of software-related industries. Add the word productivity to the mix and many people would grab torches and pitchforks. The vilification of these words (or any words – it is sort of like burning books in my mind) makes it difficult to talk about systemic improvement. As a Kanban practitioner, I focus on flow. But not just flow, I advise my clients that they should keep their eye on continuously improving the flow. Continuous improvement yields better outcomes. Organizations, teams, and individuals that overextend and exceed their WIP limit are not improving their delivery of outcomes but rather in Jim Benson’s words “disrespecting your ability to create amazing things.” More bluntly they are neither effective nor efficient. Remember to buy a copy and read along. Amazon Affiliate LInk: Previous Entries Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Week 6: - Next SPaMCAST Next week, Matthew Stibbe and I talk about the impact of leadership when building a technology-driven business.

SPaMCAST 700 features our interview with Slater Victoroff. Slater suggests that what we think of as AI today will be overtaken by human-machine partnerships. He uses the metaphor of a bionic arm. AI is the future and that future is not very far away. Slater Victoroff is the Founder and CTO of indico data solutions, an Enterprise AI solution for unstructured content with an emphasis on text and NLP. He has been building machine learning solutions for startups, governments, and Fortune 100 companies for the past 5 years and is a frequent speaker at AI conferences. Twitter: Website: Re-read Saturday News The chapters of this week and last are interrelated. Last week we focused on multitasking. For those with a short memory, human multitasking is in the same category as unicorns and shiny vampires: a fun concept but dangerous to believe in. This week we deal with context switching. Because humans don’t have multiple cores and processors instead of multitasking we bounce between things. Each bounce requires shifting context – this takes time and effort. Remember that the author established earlier that things that are not done are sitting in the back of your mind sucking up capacity and an occasional conscious thought (another contest switch). Remember to buy a copy and read along. Amazon Affiliate LInk: Previous Entries Week 1: – Week 2: – Week 3: - Week 4: - Week 5: - Next SPaMCAST Back to basics, whether you call that quick meeting to coordinate the day the Daily Scrum, Stand-up or a huddle is not material. Daily coordination is phenomenally powerful and useful unless it isn’t. Just making teams meet without benefit is a really bad idea. What else can be done? We will also have a visit from Tony Timbol with another installment from his Tell A Story Column.

This week we feature our interview with Eric Daimler, PhD. Eric and I discussed how AI can unlock the potential of humanity. Dr. Eric Daimler is an authority in Artificial Intelligence with over 20 years of experience in the field as an entrepreneur, executive, investor, technologist, and policy advisor. Daimler has co-founded six technology companies that have done pioneering work in fields ranging from software systems to statistical arbitrage. Daimler is the author of the forthcoming book "The Coming Composability: The roadmap for using technology to solve society’s biggest problems." A frequent speaker, lecturer, and commentator, he works to empower communities and citizens to leverage AI for a more sustainable, secure, and prosperous future. As a Presidential Innovation Fellow during the Obama Administration, Daimler helped drive the agenda for U.S. leadership in research, commercialization, and public adoption of AI. He has also served as Assistant Dean and Assistant Professor of Software Engineering in Carnegie Mellon’s School of Computer Science. His academic research focuses on the intersection of Machine Learning, Computational Linguistics, and Network Science (Graph Theory). He has a specialization in public policy and economics, helped launch Carnegie Mellon’s Silicon Valley Campus, and founded its Entrepreneurial Management program. A frequent keynote speaker, he has presented at venues including the engineering schools of MIT, Stanford, and Harvard. Daimler studied at Stanford University, the University of Washington-Seattle, and Carnegie Mellon University, where he earned his PhD in its School of Computer Science. Contact Information Twitter: @ead LinkedIn: Website: Re-read Saturday News Multitasking is the first or second greatest LIE in the modern business world. The best description of multitasking would include thrash, waste, and hubris. The problem is that EVERYONE thinks they are special and can multitask their way to the effective delivery of value. Chapter 3 of blasts away at multitasking (another take on the topic from 2015: Multitasking Yourself Away From Efficiency | Software Process and Measurement ). Multitasking is bad, don’t do it. Remember to buy a copy and read along. Amazon Affiliate LInk: Previous Entries Week 1: – Week 2: – Week 3: - Week 4: - Upcoming Events: Final Call! Free Webinar When Prioritization Goes Bad April 19, 2022 11 AM EDT to 1230 EDT Next SPaMCAST Next week for SPaMCAST 700 we will feature our interview with Slater Victoroff. Slater presents an alternate definition for AI. Compare and contrast to Dr. Daimler’s definition?

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 or on LinkedIn at Re-read Saturday News Week 3 of our re-read of 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: Previous Entries Week 1: – Week 2: – Week 3: - https://bit.ly/3usMiLm Upcoming Events: Free Webinar When Prioritization Goes Bad 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 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 . 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, “l” 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 LinkedIn: Upcoming Events: Free Webinar When Prioritization Goes Bad 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 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 (buy a copy using our Amazon Affiliate link get reading) along with us. The written version: 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: Twitter: j LinkedIn: 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 (buy a copy using our Amazon Affiliate link get reading) as we run a poll to select the next of books for the series. 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, 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 . 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 while we run a poll to select the next books. Week 1: - Week 2: - Week 3: - Week 4: - Week 5 - Week 6 - Week 7 - Week 8 – Week 9 - Week 10 - 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 to learn more about him. Plutoshift: 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 completed (thanks to Laurie and Todd for use of their condo). We will be back next week. Week 1: - Week 2: - Week 3: - Week 4: - Week 5 - Week 6 - Week 7 - Week 8 – Week 9 - 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! Re-Read Saturday News Week 9 of our re-read of 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 Week 1: - Week 2: - Week 3: - Week 4: - Week 5 - Week 6 - Week 7 - Week 8 – Week 9 - 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 Website: Re-Read Saturday News Week 8 of our re-read of 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). Week 1: - Week 2: - Week 3: - Week 4: - Week 5 - Week 6 - Week 7 - Week 8 - 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 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. Week 1: - Week 2: - Week 3: - Week 4: - Week 5 - Week 6 - Week 7 - 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: Twitter: Company Website: https://www.pyze.com/ Re-Read Saturday News Week 6 of our re-read of 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. Week 1: - Week 2: - Week 3: - Week 4: - Week 5 - Week 6 - 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.

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. 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 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. Week 1: - Week 2: - Week 3: - Week 4: - Week 5 - 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. 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 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. Week 1: - Week 2: - Week 3: - Week 4: - Week 5 - 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: 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: TeamForm: Email: LinkedIn: 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 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. Week 1: - Week 2: - Week 3: - Week 4: - 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 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.

Today we feature our interview with Vincent Hendersen. We talked about scaling agility up -- not the same as scaling agile. Mr. Hendersen and I discussed thinking about agile as a service to align team and portfolio. This is a most thought-provoking interview. The idea of thinking about agile teams as a subscription model shifts the whole agile paradigm. Vincent’s bio: Vincent Henderson is an operations and product executive in B2B organizations that use knowledge and technology to create value. He has transformed information supply chains and content-driven businesses across 10 countries, 5 industries, and 3 decades. Vincent is a business technologist. He enjoys building rational and purposeful teams that focus on concrete, meaningful outcomes. He had his first Agile workshop about 10 years ago with Tom Cagley and Anthony Mersino. Since that watershed moment of insight, he has implemented and run Agile product development in the 4 different organizations that he has led since. As a business leader who rolls out Agile as part of his leadership practice, he has developed unique insights around how Agile fits within the broader context of business management. Contact information: Re-Read Saturday News This week we re-read Chapter 5 of Project to Product (Amazon Affiliate Link). As the previous chapters have highlighted, we can measure the flow items that enter and exit a value stream. There are a number of suitcase words (words that have many ideas packed in them) in that statement, such as value streams and flow items. connects flow items and metrics to business results. The integrated view is where the real power of the model is found (but only if you bite the bullet and understand the value streams in the organization). Catch up on previous installments: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Week 6: - Next SPaMCAST Next week, another interview takes center stage. 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.

This week we continue the priority theme with an essay titled, “What is a Priority?” I wish it was a simple question. Since the whole idea of priority is premised on a group of people having a shared perspective and definition this is a question that needs to be asked and answered. We also have a visit from Susan Parente with her I’m Not A Scrumdamentalist column. In this installment, we tackle bad leadership (I wish tackle was not used metaphorically). Upcoming Events Out of Control Work Entry Means "No Agile For You" November 4, 2021 11:00 AM - 12:30 PM EST In this webinar, we will use five common patterns of work entry to highlight team dysfunctions of poor work entry practices. We will also explore a path forward for each work entry pattern to help improve the delivery of business value. Register Now: Re-Read Saturday News I was busy preparing for my webinar, Out of Control Work Entry Means "No Agile For You" and did not complete Chapter 5’s re-read of Project to Product. (Amazon Affiliate Link). We will be back next week. Catch up on previous installments: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Next SPaMCAST Next week we will feature our interview with Vincent Hendersen. We talked about scaling agility up -- not the same as scaling agile. Mr. Hendersen and I discussed thinking about agile as a service to align team and portfolio.

In the essay today, prioritization requires a steady hand and consistency. The process for prioritization should have more in common with a well-oiled basketball or futbol team than five-year-olds playing soccer in the schoolyard. How the moving parts work together is a process, but in some circles, “process” is a dirty word. On the conversation side, Jeremy Berriault brings his QA Corner to the cast. We discuss test automation plans and strategies in agile. Upcoming Events The Agile Online Summit! This Week!! Tom Henricksen delivers one of the most innovative online conferences. This year he has upped the bar again! While you can attend the Summit for free, there are a number of innovative options to learn even more from the Summit. Please join the premier Agile Online Conference from October 25th to 27th, 2021. Register at Re-Read Saturday News This week, we dive into Chapter 4 of Project to Product titled Capturing Flow Metrics. (Amazon Affiliate Link). Why capture flow metrics? The four components of the flow distribution reflect the investment pattern within the value stream. That pattern is a direct reflection of the value delivered by an organization. Catch up on previous installments: Week 1: - Week 2: - Week 3: - Week 4: - Week 5: - Next SPaMCAST Next week another essay, perhaps even the promised Why Pragmatic Has Become Code For Half-assed. We will also have a visit from Susan Parente with her I Am Not A Scrumdamentalist column.

Today, we feature an essay titled, So I Asked What Is Agile. A simple question that yields interesting answers. One interesting outcome was that answers fit into three categories. We explore the process and people-oriented groups this week. I will come back to the rant category later this month. In addition to the essay, Tony Timbol brings his To Tell A Story column to the cast! In this installment, the product owner’s role is under the microscope. Check out Tony’s website at https://bit.ly/2Z1IrIg Upcoming Events The Agile Online Summit! The clock is ticking - loudly! Tom Henricksen delivers one of the most innovative online conferences. This year he has upped the bar again! While you can attend the Summit for free, there are a number of innovative options to learn even more from the Summit. Please join the premier Agile Online Conference from October 25th to 27th, 2021. Register at Re-Read Saturday News This week, we are taking a break from Project to Product. Remember to buy a copy today (Amazon Affiliate Link) and we will be back next week. Previous Week’s Installment: Week 1: - Week 2: - Week 3: - Week 4: - https://bit.ly/3lqJTwd Next SPaMCAST Kyle Siemens returns to the podcast to talk about certifications and running a testing business. Kyle does not shy away from hard topics in a world that is certification crazy.