Podcasts about product development flow

BONUS: Mastering the Art of Forecasting, Prioritization Paradigms and Flow Metrics with Troy Lightfoot Agile Planning Insights From The Gambler's Ruin Thought Experiment Troy, in this Agile Uprising podcast episode, delves into his intriguing journey in the realm of forecasting and estimation for software development. Inspired by that episode, we discuss the concept of Gambler's Ruin, a mathematical problem turned into a game. Troy shares the main insights from Gambler's Ruin and mentions Prateek Singh of ProKanban.org who has used this concept to demonstrate that even a slight skill advantage can lead to success when focusing product development on what Troy calls “Small Bets”  Small bets and impact on prioritization Small bets relate to the implications of spending money on a product idea. It's not just an expense; it's an investment with an anticipated return on investment (ROI). The crucial question arises: how do we strategically place these bets in product development? Here, Troy exposes the fallacy of assuming we can determine value upfront. We also discuss the concept of anti-fragility and highlight how many processes are inadvertently designed to be fragile. In this context, the size of the bet correlates with cycle time, and "time" itself becomes the bet's magnitude. As Annie Duke advocates in her book "Thinking in Bets," small bets bolster resilience, while large bets can lead to vulnerability. Essential flow metrics and their significance How do we know we are making small bets? Troy sheds light on the pivotal flow metrics that software development teams should diligently track. He explains the relationship between Work In Progress (WIP) and cycle time, referring to Little's law formula. And he introduces work item age as a metric that can help predict WIP and Cycle time, which gives teams a tangible representation of their current investment. This metric aids in decision-making and fosters a more effective approach to forecasting. Rethinking traditional prioritization techniques In the podcast, Troy advocates for a paradigm shift in prioritization practices. He highlights that the more time spent prioritizing work, the larger the bet size (planning time directly affects bet size). Drawing from the wisdom of Don Reinertsen and the principles outlined in the book "Principles of Product Development Flow," he stresses the intrinsic cost associated with all work undertaken. Aligning individuals and teams on priorities is essential, yet the priority itself may hold uncertainty. To aid teams in this endeavor, Troy discusses the Weighted Shortest Job First (WSJF) framework, and how it offers a pragmatic approach to prioritize tasks based on contributing factors. However, prioritization is directly affected by dependencies, which means that eliminating dependencies becomes a critical step towards making smaller, more manageable bets. For example, by segregating dependencies, teams can significantly reduce bet sizes and enhance predictability. In this episode, Troy elucidates how conventional prioritization techniques can inadvertently hinder forecasting and predictability. He provides insights into alternative approaches that foster adaptability and more accurate forecasts. Resource recommendation For those eager to dive deeper into the world of Agile metrics and predictability, Troy recommends Dan Vacanti's book, "Actionable Agile Metrics for Predictability," as an invaluable resource. About Troy Lightfoot Troy is a Lean Product Development Coach and trainer for ProKanban.Org. He coaches and trains Scrum, Kanban, and SAFe and other Agile Scaling approaches. Troy transitioned from computer science to full-time Agile coaching, specializing in Lean Portfolio and Program Management. He is also a co-founder of the Agile Uprising Podcast, and an active blogger. For further insights into Troy's work and methodologies, visit ProKanbanTraining.com and explore the Agile Uprising podcast. Additionally, you can delve deeper into Troy's teachings at ProKanban.org.

Ein Buch aus einer ganz anderen Welt – der Produktentwicklung – und doch mit einer Fülle von Anregungen für Steuerberater und Unternehmer aus allen Branchen. Mit Tobias Leisgang, Innovations- und Nachhaltigkeitsentwickler, bespreche ich die aus unserer Sicht wichtigsten der insgesamt 175 (!) Prinzipien. Angefangen von den wirklich aussagekräftigen Kennzahlen über Engpassmanagement bis Work in Progress Hindernissen.

Today, I'm talking to Gina Doyle.-Gina currently works as a Product Designer designing the testing and runner aspects of the CI/CD features at GitLab. Before GitLab, she once worked as a contract designer at Instacart and Hera Realty Group and worked in-house at Red Hat for multiple years. Also in October of 2021, Gina started a design consulting company, SVG consulting group, with her brother and mom, which I found super fascinating.-During our conversation, one pattern that I realized in Gina's career was that she was always designing in highly technical areas, primarily in developer and internal tooling. Thus, we delved into pretty technical stuff, and Gina shared valuable advice about working with developers, GitLab's product development flow, and tips for any designers about to enter a technical field. If you want to improve your collaboration skills with developer, this episode is filled with goodness for you. So, without further ado, here was my conversation with Gina Doyle.===Highlights⭐ GitLab's product development flow⭐ How Gina managed 3 jobs at the same time⭐ Tips for designers entering a highly technical field⭐ Best practices for designer x developer collaboration⭐ How Gina found contract design opportunities===Links

Jeffrey remarks that he's working with a software team whose code is "done", that is, the organisation wants to keep using it but doesn't want to invest more in changing it. He and Squirrel reflect on when this make sense and how "software doneness" affects processes and measurements. SHOW LINKS: - Control Chart: https://en.wikipedia.org/wiki/Control_chart - Principles of Product Development Flow: https://www.pdma.org/page/review_principles_pr --- Our book, Agile Conversations, is out now! See https://agileconversations.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. 
 Email us at info@agileconversations.com

Dominica Degrandis is an expert on flow and helping companies get the benefits of using flow metrics to make systemic improvements. What does she find as the biggest obstacle to success? A proper investment in change. In this conversation Jeffrey and Dominica talk about the importance of a daily change budget, time you'd expect people to be working in the new way, with some advice for both leaders and practitioners. Recorded live at DevOps Enterprise Summit 2022 in Las Vegas. SHOW LINKS: - LinkedIn: https://www.linkedin.com/in/dominicadeg/ - Dominica Degrandis: https://ddegrandis.com - Making Work Visible, 2nd Edition: https://itrevolution.com/making-work-visible-by-dominica-degrandis/ - Dominica Degranids past episode: https://podcasts.apple.com/us/podcast/troubleshooting-agile/id1327456890?i=1000458010204 - Donald Reinertsen Principles of Product Development Flow: http://reinertsenassociates.com/books/ --- Our book, Agile Conversations, is out now! See https://agileconversations.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. 
 Email us at info@agileconversations.com

Jean Pierre Lambert, Développeur à Scrum Master, Coach Agile, nous raconte son parcours et sa manière de voir son métier. En tant que facilitateur de projets IT, il nous partage la méthode pour arriver à des projets vraiment agiles. Intéressant, non ? Je vous explique de quoi nous avons parlé dans les grandes lignes : - La création de sa chaîne YouTube Scrum Life en 2017 jusqu'à maintenant : avec une communauté de 25 000 abonnés et une newsletter hebdomadaire ! Sa chaîne a pour objectif de partager et d'évangéliser, grâce à une nouvelle vidéo chaque semaine qui traite d'un sujet : on y trouve plein de conseils sur les choses à faire et les erreurs à éviter. - Un de ses premiers articles « c'est quoi Scrum Master » qu'il a écrit d'une traite. - La place du développeur dans la création d'une interface : pur exécutant ou cocréateur avec les équipes produits ? - Méthode Lean ou méthode Scrum ? Amies ou ennemies ? - Comment faire de l'agile efficacement ? - L'avenir du Scrum Guide. Jean Pierre évoque les méthodes agiles qui permettent d'intégrer plus de légèreté dans les process grâce à l'intégration d'une rigueur au sein des organisations. Contradictoire ? Non vous verrez en l'écoutant : l'agilité c'est l'extrême rigueur ! Nous finissons par la question que beaucoup se posent : pourquoi tant de projets IT se cassent la figure en cours de route ? Jean Pierre a son idée sur la question et nous la partage ici. Bonne écoute et à dans 15 jours ! ▬▬▬▬▬▬▬▬▬▬ Soutenez le podcast gratuitement - Abonnez-vous - Laissez un avis et 5 ⭐ - Merci beaucoup ! - Inscrivez-vous sur On part en prod pour ne louper aucun épisode Les informations mentionnées dans cet épisode - Méthode Agile, Manifeste Agile : https://agilemanifesto.org/iso/fr/manifesto.html - Constantin GUAY (Scrum Life) : https://www.linkedin.com/in/constantinguay/ - La méthode du canard en plastique : https://fr.wikipedia.org/wiki/Méthode_du_canard_en_plastique - Jean-François ZOBRIST : Cash Flow https://www.youtube.com/watch?v=4xLAvuWo6Qw - Frederic LEGUEDOIS : référence en France du “No Estimate” - VUCA : volatility, uncertainty, complexity and ambiguity - Lean Management : https://www.youtube.com/watch?v=R-bIpD-ED3Y Recommandations de Jean-Pierre - Livre « The Principles of Product Development Flow » de Donald G. REINERTSEN - Formation Deviens meilleur(e) Scrum Master : https://scrumlife.tv/meilleursm/ Pour suivre l'actualité de Jean-Pierre - LinkedIn : https://www.linkedin.com/in/jp-lambert/ - Scrum Life : https://scrumlife.tv/ ▬▬▬▬▬▬▬▬▬▬ Postproduction Audio : Guillaume Lefebvre Music by MADiRFAN from Pixabay

Free Resources NEW! The Small Batches Slack App for Teams Toyota Kata Pocket Guide The Flow Collective DevOps Email Course Project to Product Email Course War & Peace & IT Pocket Guide Recommend Reading The New Economics by Dr. Deming The High-Velocity Edge by Dr. Steven Spear The Fifth Discipline by Peter Senge The Toyota Way by Jeffery Liker The Toyota Kata by Mike Rother The Principles of Product Development Flow by Donald Reinersten Making Work Visible by Dominica de Grandis Modern Software Engineering by Dave Farley The DevOps Handbook by Gene Kim, Jez Humble, Patrick de Bois, John Willis The Phoenix Project by Gene Kim, Kevin Behr, and George Stafford Team Topologies by Matthew Skelton, Manuel Pais Recommended Listening Small Batches #50: Introducing Dr. Deming with John Willis Small Batches #39: The High-Velocity Edge (Part One) Small Batches #65: Systems Thinking Small Batches #53: The Toyota Way Small Batches #60: The Principles of Product Development Flow Small Batches #59: Making Work Visible Small Batches #63: Modern Software Engineering Small Batches #1: The Three Ways of DevOps Small Batches #16: The Story of Parts Unlimited Small Batches #18: Team Topologies Links Adam Hawkins on Twitter Adam Hawkins on LinkedIn Adam Hawkins' website

Free Resources NEW! The Small Batches Slack App for Teams Toyota Kata Pocket Guide The Flow Collective DevOps Email Course Project to Product Email Course War & Peace & IT Pocket Guide Recommend Reading The New Economics by Dr. Deming The High-Velocity Edge by Dr. Steven Spear The Fifth Discipline by Peter Senge The Toyota Way by Jeffery Liker The Toyota Kata by Mike Rother The Principles of Product Development Flow by Donald Reinersten Making Work Visible by Dominica de Grandis Modern Software Engineering by Dave Farley The DevOps Handbook by Gene Kim, Jez Humble, Patrick de Bois, John Willis The Phoenix Project by Gene Kim, Kevin Behr, and George Stafford Team Topologies by Matthew Skelton, Manuel Pais Recommended Listening Small Batches #50: Introducing Dr. Deming with John Willis Small Batches #39: The High-Velocity Edge (Part One) Small Batches #65: Systems Thinking Small Batches #53: The Toyota Way Small Batches #60: The Principles of Product Development Flow Small Batches #59: Making Work Visible Small Batches #63: Modern Software Engineering Small Batches #1: The Three Ways of DevOps Small Batches #16: The Story of Parts Unlimited Small Batches #18: Team Topologies Links Adam Hawkins on Twitter Adam Hawkins on LinkedIn Adam Hawkins' website

Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Salvatore was working in a startup with a team that, on paper, was a star team. However, when he started to observe how they worked, he noticed that the team was rarely sticking to what they had planned for the Sprint, and even the PO was at a loss on how to help the team stay on track and focus on what they had planned. In this segment, we refer to Cost of Delay, one of the topics discussed in The Principles of Product Development Flow, and share some tips on how to help a team that is stuck in this situation. Featured Book of the Week: The Goal by Elyahu Goldratt In The Goal: A Process of Ongoing Improvement by Eliyahu Goldratt, Salvatore found the principles behind lean thinking as well as a model that helped him in his work as a Scrum Master. The Goal is a book where Theory Of Constraints is introduced to a business focused audience concerned with improving the performance of their businesses. In this segment, we also refer to The Principles of Product Development Flow: Second Generation Lean Product Development by Don Reinertsen, which helped Salvatore understand how the flow of work can be investigated and improved in organizations. How can Angela (the Agile Coach) quickly build healthy relationships with the teams she's supposed to help? What were the steps she followed to help the Breeze App team fight off the competition? Find out how Angela helped Naomi and the team go from “behind” to being ahead of Intuition Bank, by focusing on the people! Download the first 4 chapters of the BOOK for FREE while it is in Beta! About Salvatore Rinaldo Salvatore is an Agile Coach and Scrum Master based in London. His background is in telecommunications and software engineering. For the past 7 years, Salvatore has been helping organizations leverage Lean, agile, Flow principles and system thinking to achieve better business agility. You can link with Salvatore Rinaldo on LinkedIn. 

Free Resources NEW! The Small Batches Slack App for Teams Toyota Kata Pocket Guide The Flow Collective DevOps Email Course Project to Product Email Course War & Peace & IT Pocket Guide Recommend Reading The New Economics by Dr. Deming The High-Velocity Edge by Dr. Steven Spear The Fifth Discipline by Peter Senge The Toyota Way by Jeffery Liker The Toyota Kata by Mike Rother The Principles of Product Development Flow by Donald Reinersten Making Work Visible by Dominica de Grandis Modern Software Engineering by Dave Farley The DevOps Handbook by Gene Kim, Jez Humble, Patrick de Bois, John Willis The Phoenix Project by Gene Kim, Kevin Behr, and George Stafford Team Topologies by Matthew Skelton, Manuel Pais The Obstacle is the Way by Ryan Holiday Recommended Listening Small Batches #50: Introducing Dr. Deming with John Willis Small Batches #39: The High-Velocity Edge (Part One) Small Batches #65: Systems Thinking Small Batches #53: The Toyota Way Small Batches #60: The Principles of Product Development Flow Small Batches #59: Making Work Visible Small Batches #63: Modern Software Engineering Small Batches #1: The Three Ways of DevOps Small Batches #16: The Story of Parts Unlimited Small Batches #18: Team Topologies Links Adam Hawkins on Twitter Adam Hawkins on LinkedIn Adam Hawkins' website

Dragan returns to talk with us about why small batch sizes are valuable, and how to apply this idea way beyond just release frequency, to pull requests, co-creation, and more. Transcript: https://agileconversations.com/blog/smallest-batch-is-pair-dragan-pt2/ SHOW LINKS: - Dragan: - draganstepanovic.com - https://twitter.com/d_stepanovic - https://www.linkedin.com/in/dstepanovic/ - Systems Thinking: https://www.extremeuncertainty.com/an-introduction-to-systems-thinking/ - Promiscuous Pairing: https://csis.pace.edu/~grossman/dcs/XR4-PromiscuousPairing.pdf - Theory of Constraints: https://en.wikipedia.org/wiki/Theory_of_constraints - Donald Reinertsen, The Principles of Product Development Flow: https://www.goodreads.com/book/show/6278270-the-principles-of-product-development-flow --- Our book, Agile Conversations, is out now! See https://agileconversations.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us at info@agileconversations.com

This episode continues the theme of the past two episodes. Tl;DR: understand the price of work, optimize for flow through queues, use WIP constraints, reduce batch sizes, and prefer decentralization.Free Resources NEW! The Small Batches Slack App for Teams Toyota Kata Pocket Guide The Flow Collective DevOps Email Course Project to Product Email Course Links Adam Hawkins on Twitter Adam Hawkins on LinkedIn Adam Hawkins' website Principles of Product Development Flow Episode 59: Time Thieves Episode 58: Queuing Theory

How should you make difficult decisions? What are common kinds of difficult decisions in the games industry? What are common decision-making models? What are important distinctions between types of decisions? Deep dive on this very important topic in great depth and with our typical philosophical approach! HOSTS: - Joseph Kim, CEO at LILA Games - Brett Nowak, CEO at Liquid & Grit LINKS: The Principles of Product Development Flow, by Donald Reinertsen Extreme Ownership: How U.S. Navy SEALs Lead and Win, by Jocko Willink Making Smart Choices: 8 Keys to Making Effective Decisions blog Win With Character, Win with Cruelty, Jim Harbaugh Read about it in the GameMakers newsletter --- Send in a voice message: https://anchor.fm/gamemakers/message

This episodes connects Principles of Product Development Flow by Donald Reinersten and Making Work Visible by Dominica DeGrandis via the five time thieves.The thieves are: too much WIP (work-in-progress), unknown dependencies, conflicting priorities, neglected work, and (the most annoying of the bunch) interrupts.Free Resources NEW! The Small Batches Slack App for Teams Toyota Kata Pocket Guide The Flow Collective DevOps Email Course Project to Product Email Course War & Peace & IT Pocket Guide Links Adam Hawkins on Twitter Adam Hawkins on LinkedIn Adam Hawkins' website Principles of Product Development Flow Making Work Visible Dominica DeGrandis on the Profound Podcast Get InvolvedFollow @smallbatchesfm on Twitter and tweet me with your comments. Want a topic covered on the show? Then call +1-833-933-1912 and leave your request in a voice mail. Preference goes to to listener requests.Support the Show!Tell me about you in the listener survey! Rate this show on iTunes. Share this episode with your friends and colleaagues. Feedback is love, so send some my way.

With long histories in product management specifically in the games industry, we have a REAL discussion on what it takes to be a great PM. Hardcore and real talk from guys who have worked on very successful products. I led the #1 top-grossing game King of Avalon plus a lot of other shit. Brett was a lead PM on Zynga Poker which was contributing 22% of Zynga's revenue at the time. Real talk you won't get anywhere else. This talk is for hardcore PMs only! Follow this channel if you want to hear more philosophy on current and important issues in the F2P games industry. The story behind JK getting assassinated: HERE Recommended Books on PM: 1. The Principles of Product Development Flow by Donald G. Reinertsem 2. Principles by Ray Dalio 3. Extreme Ownership by Jocko Willink 4. The Hard Thing About Hard Things by Ben Horowitz 5. Atomic Habits by James Clear 6. The Score Takes Care of Itself by Bill Walsh Read about it in the GameMakers newsletter: https://gamemakers.substack.com/ --- Send in a voice message: https://anchor.fm/gamemakers/message

Dragan Stepanović is our guest, and he brings his heuristic: “Continuous code reviews enable higher team's throughput”. We dive into Dragan's research on how async code reviews affect the quality and throughput of teams that create and maintain software. He also shares how his research challenged some of his assumptions, and we finalise discussing his experiences bringing his research to management. Dragan recommends the following resources: The Principles of Product Development Flow from Donald G. Reinertsen The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win from Gene Kim, Kevin Behr and George Spafford The Goal from Eliyahu M. Goldratt Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation from Jez Humble and Dave Farley Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations from Nicole Forsgren, Jez Humble and Gene Kim Dragan (@d_stepanovic) is based in Berlin and currently works as a principal engineer at HelloFresh. Typically on the search for better ways of working, exploring ends of the spectrums, and helping teams and organisations try out counter-intuitive ideas that initially don't make a lot of sense but end up as completely opposite of that. It's been a long time since he fell in love with eXtreme Programming, Domain-Driven Design, and software as a craft (founder of Software Crafting Serbia community). In the last couple of years, he enjoys endless discussions connecting the Theory of Constraints, Systems Thinking, Lean and socio-technical topics.

Probabilistic modeling is useful for answering all kinds of questions, from assessing financial risk to making engineering time estimates. Yet spreadsheets are poor at this job, which is why Taimur and his colleagues are building Casual. Taimur talks with Mark and Adam about ranges as an intuitive way to estimate; the usefulness of Monte Carlo simulations; and the role of math in dating cave paintings. @MuseAppHQ hello@museapp.com Show notes Taimur Abdaal Casual Not Overthinking Airtable Drake‘s equation line of best fit “not even wrong” Flatland Monte Carlo simulation R closed-form solution RoboCup Slack (management book) queueing theory The Principles of Product Development Flow tail risk expected value gambler’s fallacy distribution shapes e.g. bell curve fan chart Samo Burja of Bismark Analysis meta-analysis preregistered studies confidence interval false positive, false negative onboarding episode A/A testing carcinization combinatorics two-tailed test

Sorti en 2018, le livre Accelerate (écrit par Nicole Forsgren, Jez Humble et Gene Kim) est un peu la nouvelle référence littéraire dans le milieu technologique. L'ouvrage reprend et développe les conclusions de 4 années de sondage pour démontrer (chiffres à l'appui) que la performance des équipes de développement logiciel est déterminée par une multiplicité de facteurs techniques, mais aussi produits, managériaux et culturels.L'un d'entre eux, emblématique, est la faculté à livrer en production le plus souvent possible, car contrairement à la croyance populaire, la stabilité du produit n'en souffre pas, bien au contraire ! Pourtant, aujourd'hui, la mise en production est bien souvent une étape redoutée par les équipes et  se fait trop souvent dans la douleur...Alors, accélérer la livraison logicielle, est-ce vraiment possible ? Faire mieux, plus rapidement, comment m'y mettre ? Et est-ce que ça fait mal ? Plus globalement, qu'est-ce que proposent les auteurs d'Accelerate et peut-on leur faire confiance ? Au micro de Laure Constantinesco, Maria Mokbel, consultante chez OCTO, vous explique tout dans ce quatrième épisode de OCTO Buzzword Bingo !Ressources :Livres :Accelerate: The Science Behind Devops: Building and Scaling High Performing Technology Organizations, Nicole Forsgren, Jez Humble, Gene Kim, IT Revolution Press, 2017.The Goal,  Eliyahu M. GoldrattContinuous Delivery, Jez Humble et David FarleyThe principles of Product Development Flow,  Donald G. ReinertsenToyota Kata,  Mike RotherL' Étude Accelerate sur le site de Google : Accelerate State Of DevOps Report La Matinale OCTO consacrée à Accelerate, un talk à voir ou revoir sur notre blogLa formation dispensée par OCTO Academy, pour adopter les bonnes pratiques et être plus performant en delivery Crédits :Un podcast proposé par OCTO Technology, écrit, réalisé et enregistré par LACOLAB (Laure Constantinesco et Charlotte Abdelnour). Description du podcast : Natalie SchmitzSound Design et mixage : Paul Love (The Clean Sound). Musique originale : AudioJungle / Ocean_Studio.

Vic (@AgileCoffee) and Larry (@LarryLawhead) teamed up with Lakshmi Ramaseshan (@LakshmiRamases2) and Professor Hadar Ziv (UCI - Dept of Informatics ) in a virtual coffee shop to discuss the following topics: Did the Agile Open SoCal work as a virtual event?Playing to Your Strengths - Using Strengthsfinder (book) with TeamsWhat is a Value Hypothesis (and why was it following Larry all day?)Creating a Values & Principles Based Culture Please HELP support us by becoming a Patron: patreon.com/agilecoffee Here's the MIRO board that Lakshmi created for our virtual event: Books and resources mentioned in this episode: Lakshmi's presentation on The Power of InceptionsVic's old post about InceptionsScrum PLoP! one-piece continuous flowThe Principles of Product Development Flow - by Donald ReinertsenHigh Performance Tree (Lyssa Adkins) Agile Coffee is Proud to be a part of the Agile Podcast Network Looking for MORE Scrum videos? We've got you covered. Tune in!

Vic (@AgileCoffee) and Larry (@LarryLawhead) were joined by Ben Rodilitz (@BenRodilitz) and Chris Hurney (@chris_hurney) in a virtual coffee shop to discuss the following topics: the Weakness of One-piece FlowDo you need Team Maturity before you Scale?the Imperitive to improve our industry's Diversity, Equity and InclusionHow well do you understand your Product Owner's world? Are you looking for a game to teach self-organization and empirical process control to teams? CardZinga! can be played in-person or online. Get the instructions and see examples at CardZinga.com Books and resources mentioned in this episode: Scrum PLoP! one-piece continuous flowThe Principles of Product Development Flow - by Donald ReinertsenDiversity, Equity and Inclusion:The Sword and the Shield: The Revolutionary Lives of Malcolm X and Martin Luther King Jr. - by Peniel E. JosephThe Autobiography of Malcolm X: As Told to Alex Haley - by Malcolm X and Alex HaleyThe Meta-Cast, episode 169 "Discover your Superpower"White Fragility: Why It's So Hard for White People to Talk About Racism - by Robin DiAngelo and Michael Eric DysonSo You Want to Talk About Race - by Ijeoma OluoCompassionate Coding - founded by @AprilWenselWomen in AgileRole of Product Owner:ebgconsulting.com/blog/product-manager-product-owner/romanpichler.com/blog/product-manager-vs-product-owner/productcoalition.com/the-collide-of-product-management-and-product-ownership-439105363028Monte Carlo forecasting in Scrum (Scrum.org) Looking for Scrum/Kanban training in Southern California or Nashville, TN? Rocket Nine has got you covered. Visit RocketNineSolutions.com today.

In the latest episode of The Idealcast, Gene Kim is joined by Michael Nygard, a senior vice president at Sabre and author of the bestselling Release It! Nygard has helped businesses and technology leaders in their transformation journeys over his long career and was even one of the inspirations behind The Unicorn Project’s protagonist, Maxine.   In their discussion, Kim and Nygard explore how we can enable thousands or even tens of thousands of engineers to work together toward common objectives, including the structure and dynamics required to achieve it. They also examine what truly great architecture looks like and the continuing importance and relevance of Conway’s Law.   Bio: Michael Nygard strives to raise the bar and ease the pain for developers around the world. He shares his passion and energy for improvement with everyone he meets, sometimes even with their permission. Living with systems in production taught Michael about the importance of operations and writing production-ready software. Highly-available, highly-scalable commerce systems are his forte. Michael has written and co-authored several books, including 97 Things Every Software Architect Should Know and the bestseller Release It!, a book about building software that survives the real world. He is a highly sought speaker who addresses developers, architects, and technology leaders around the world. Michael is currently Senior Vice President, Travel Solutions Platform Development Enterprise Architecture, for Sabre, the company reimagining the business of travel.   Twitter: @mtnygard LinkedIn: https://www.linkedin.com/in/mtnygard/ Website: https://www.michaelnygard.com/ You’ll Learn About: How to build great architecture for large teams. The real implications of Conway’s Law. Architecture as an organizing logic and means of software construction. Real-life stories of technology leaders’ transformation journeys. Decentralized economic decision making. The fear cycle and predictability. The after effects of the Yegge memo. A great definition of what great architecture is.  Leadership and the relationship between the business’ architecture and the technology architecture of the business. RESOURCES Release It!: Design and Deploy Production-Ready Software (Pragmatic Programmers) by Michael T. Nygard Clojure programming language Transaction Processing Facility (TPF) operating system Totality Corporation The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen MCDP1: Warfighting Conway's law Team of Teams: New Rules of Engagement for a Complex World by General Stanley McChrystal with Tantum Collins, David Silverman and Chris Fussell The Fear Cycle by Michael T. Nygard State of DevOps Report DevOps Enterprise Summit 2020 Coherence Penalty for Humans by Michael T. Nygard Michael Nygard on Cognicast podcast   TIMESTAMPS   [00:07] Intro [02:12] Meet Mike Nygard [04:36] What is TPF operating system? [05:40] Finding the perspective to write Release It! [11:07] Totality Corporation [13:54] Moving large teams towards common objective [18:37] Decentralized economic decision making [19:52] The Principles of Product Development Flow [23:38] Tale of two outages [27:27] Distance incentive supply [32:00] Architecture is one top predictors of performance [35:05] Other attributes of good architecture [39:19] The Fear Cycle [43:40] An amazing finding in State of DevOps Report [45:02] Amazon replatforming example [50:35] The universal takeaways [53:07] DevOps Enterprise Summit 2020 [54:55] Characteristics of reorganizations and structural changes [1:00:00] Self-contained systems [1:02:40] Mike’s definition of architecture [1:07:13] Coherence Penalty for Humans [1:10:10] Leadership’s responsibility to the architecture

We review our holiday reading and watching plans for listeners who might want to join us in exploring lean and agile ideas over the break. We also list our top 5 episodes from 2019 and preview a few events planned for 2020. SHOW LINKS: - Ed Catmull on conversations and other challenges at Pixar: https://www.youtube.com/watch?v=k2h2lvhzMDc - Kent Beck on throughput vs latency: https://medium.com/@kentbeck_7670/inefficient-efficiency-5b3ab5294791 - Mark Schwartz, War and Peace and IT: https://itrevolution.com/war-and-peace-and-it/ https://twitter.com/schwartz_cio - Subscribed by Tien Tzuo and Gabe Weisert.: https://en.wikipedia.org/wiki/Subscribed_(book) - The Five Dysfunctions of a Team by Lencioni : https://www.goodreads.com/book/show/21343.The_Five_Dysfunctions_of_a_Team - Lean Thinking by Womack and Jones: https://www.goodreads.com/book/show/289467.Lean_Thinking - The Phoenix Project by Gene Kim : https://www.goodreads.com/book/show/17255186-the-phoenix-project - The Unicorn Project by Gene Kim : https://www.goodreads.com/book/show/44333183-the-unicorn-project - Four Steps to the Epiphany by Steve Blank: https://www.goodreads.com/book/show/762542.The_Four_Steps_to_the_Epiphany - The Reflective Practitioner by Donald Schön : https://www.goodreads.com/book/show/29916803-the-reflective-practitioner - The Lean Startup by Eric Ries : https://www.goodreads.com/book/show/10127019-the-lean-startup - The Principles of Product Development Flow by Donald Reinertsen : https://www.goodreads.com/book/show/6278270-the-principles-of-product-development-flow - Team Topologies by Skelton and Pais: https://itrevolution.com/team-topologies/ Top 5 episodes in 2019: 5. How to Detect Agile BS - Part 1 : https://soundcloud.com/troubleshootingagile/how-to-detect-agile-bs-part-1 4. Values of the Give Up Control Model : https://soundcloud.com/troubleshootingagile/values-of-the-give-up-control-model 3. Mutual Learning Model: Accountability and Compassion : https://soundcloud.com/troubleshootingagile/mutual-learning-model-accountability-and-compassion 2. Agile is Dead, Long Live Agile : https://soundcloud.com/troubleshootingagile/agile-is-dead-long-live-agile 1. Ryan Singer on Basecamp and Shape Up, Part I : https://soundcloud.com/troubleshootingagile/ryan-singer-on-basecamp-and-shape-up-part-i *** 
 Our new book, Agile Conversations, will be out in May 2020! See https://conversationaltransformation.com where you can pre-order! New video of us at the Las Vegas Devops Enterprise Summit 2019 is now available: https://www.youtube.com/watch?v=RMT_Tqzf_vc 
 We'd love to hear any thoughts, ideas, or feedback you have about the show. 
 Email us: see link on troubleshootingagile.com 
 Tweet us: twitter.com/TShootingAgile 
 Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

Join Joe Vallone, SAFe Fellow and SPCT, and Don Reinertsen, author of Principles of Product Development Flow, as they discuss how to apply WSJF in a SAFe context using dollars, not just Fibonacci numbers, and how to involve finance in WSJF conversations.

We continue our series responding to Martin Fowler's State of Agile 2018 speech. This week we look at Fowler's second claim - that agile software development has forgotten that it's about software, and that technical excellence in practises like refactoring, testing, and architecting should be (but isn't) central to discussions of good agile practise. We agree with Fowler and go even further, arguing that we should be making the (strong) case for technical excellence as a source of business value - to make our products more flexible, easier to use, and more satisfying to users. SHOW LINKS: - Fowler on the State of Agile 2018: https://martinfowler.com/articles/agile-aus-2018.html - Marick on forgotten agile ideas: http://www.exampler.com/discipline-and-skill.html and http://www.exampler.com/blog/2007/05/16/six-years-later-what-the-agile-manifesto-left-out/ - Reinertsen, The Principles of Product Development Flow (cost of delay): https://www.amazon.co.uk/Principles-Product-Development-Flow-Generation/dp/1935401009 - Accelerate book: https://itrevolution.com/book/accelerate/ - Our previous episode on technical excellence and the agile principles: https://soundcloud.com/troubleshootingagile/enhancing-agility-through-technical-excellence-and-good-design *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

The O’Reilly Programming Podcast: Embracing late changes, plurality, and decentralization.In this episode of the O’Reilly Programming Podcast, I talk with Michael Nygard, a software architect at Cognitect. He has spoken about “architecture without an end state” at numerous O’Reilly Software Architecture events, and he is the author of the book Release It! Design and Deploy Production-Ready Software.Discussion points: Architecture without an end state means accepting that “changes you’re starting now will co-exist with changes that started last year and the year before,” Nygard says. “If you adopt that perspective, then you stop trying to rip up the pavement and do something completely new, and you focus a lot more on incremental change.” Quoting Mary Poppendieck, Nygard says that changes in scope should be embraced as an opportunity. “It’s not only reality that we’re going to have technical disruptions to our systems; we’re going to have business disruptions as well,” he says. “Embracing plurality” is one of Nygard’s eight rules for architecting systems that are built to accept change. “When you build a service, it should allow for many consumers, some of whom you have no prior knowledge about— they just show up and start using your system,” he says. Other links: Nygard’s presentation Maneuverable Architecture from the 2016 O’Reilly Software Architecture Conference Nygard’s 2016 blog post on the “twilight period” in software development and deployment for cloud native systems Nygard’s workshop at QCon San Francisco on November 16th The book The Principles of Product Development Flow by Donald Reinertsen

The O’Reilly Programming Podcast: Embracing late changes, plurality, and decentralization.In this episode of the O’Reilly Programming Podcast, I talk with Michael Nygard, a software architect at Cognitect. He has spoken about “architecture without an end state” at numerous O’Reilly Software Architecture events, and he is the author of the book Release It! Design and Deploy Production-Ready Software.Discussion points: Architecture without an end state means accepting that “changes you’re starting now will co-exist with changes that started last year and the year before,” Nygard says. “If you adopt that perspective, then you stop trying to rip up the pavement and do something completely new, and you focus a lot more on incremental change.” Quoting Mary Poppendieck, Nygard says that changes in scope should be embraced as an opportunity. “It’s not only reality that we’re going to have technical disruptions to our systems; we’re going to have business disruptions as well,” he says. “Embracing plurality” is one of Nygard’s eight rules for architecting systems that are built to accept change. “When you build a service, it should allow for many consumers, some of whom you have no prior knowledge about— they just show up and start using your system,” he says. Other links: Nygard’s presentation Maneuverable Architecture from the 2016 O’Reilly Software Architecture Conference Nygard’s 2016 blog post on the “twilight period” in software development and deployment for cloud native systems Nygard’s workshop at QCon San Francisco on November 16th The book The Principles of Product Development Flow by Donald Reinertsen

  Do Product Owners need to have estimates? If you’re like most people, it’s been an assumption we’ve had for a long time that of course, we need estimates. There is, however, a growing movement to get away from being estimate driven and to focus on more valuable things.  So what exactly is the #NoEstimates crowd on about, and what might we PO’s need to do to understand and support it? On this episode, we welcome Ryan Ripley from Agile for Humans to talk about his view of what it means to not be led by estimates and how to get there.   Feedback: twitter - @deliveritcast email - deliveritcast@gmail.com   Links: Co-host Post - Looking for a co-host Ryan Ripley - Twitter - @RyanRipley - https://ryanripley.com/  - Twitter - @agileforhumans Ryan Ripley - AFH 020: #NoEstimates with Vasco Duarte Ryan Ripley - The #NoEstimates Movement - #Path17 Barry Overeem - The #NoEstimates Movement Matthew Heusser - Why your execs don't get agile and what you can do about it Don Reinertsen- The Principles of Product Development Flow  

In our third podcast focusing on Cost of Delay, LeadingAgile’s Dean Steven explains how he has used Cost of Delay with management working on defining priority for items at the portfolio level. Dean also explains why the problem Cost of Delay helps you solve is not a math problem, but a collaboration problem. SHOW NOTES 00:08 Interview Begins 00:56 Some background on the work Dean does day to day for LeadingAgile 01:43 Does Senior Mgmt. normally have a specific technique for prioritizing work across the portfolio? 02:40 Clarifying teams at the project, program and portfolio management 03:33 How does a team work at the portfolio level 04:27 What is a Business Architect 05:20 Why do we need Cost of Delay and what question does it help us solve? 06:35 It’s not a math problem, it’s a collaboration problem 07:12 How Cost of Delay will help you develop an understanding of relative business value 09:00 How to calculate Cost of Delay = (User Business Value + Time Criticality + Opportunity Enablement) / Effort SWAG 11:57 Defining Opportunity Enablement 13:18 What happens after all the work is sized? 15:40 When you get to re-estimate the values in Cost of Delay and adjust the relative priority 16:04 An example of how Dean used CoD with a client to align multiple programs of work across the organization and define relative priority for each of them 17:44 It’s not a math problem, it’s a collaboration problem 20:15 Dean’s focus on the portfolio level with Cost of Delay 21:38 Ordering vs. Prioritizing 22:18 Validating your understanding of relative User Business Value 23:40 Using the data and the math to figure out where to point the compass 24:46 What is an MVP? 25:13 Where to go for more information on Cost of Delay 25:57 How to to get in touch with Dean 26:19 Podcast Ends LINKS FROM THE PODCAST An Overview of Cost of Delay with Jim Hayden https://www.leadingagile.com/podcast/an-overview-of-cost-of-delay-with-jim-hayden-and-dave-prior/ Calculating Cost of Delay with Marty Bradley https://www.leadingagile.com/podcast/calculating-cost-delay-marty-bradley/ The Principles of Product Development Flow by Don Reinertsen http://amzn.to/2m6u0xL CONTACTING DEAN You can reach Dean: LeadingAgile https://www.leadingagile.com/guides/dean-stevens/ CONTACTING DAVE You can reach Dave: On the LeadingAgile site On Twitter at twitter.com/mrsungo On his personal site at: drunkenpm.net FEEDBACK/QUESTIONS If you have comments on the podcast, or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at dave.prior@leadingagile.com LEADINGAGILE CSM AND CSPO CLASSES For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to: www.leadingagile.com/our-gear/training/ Use the discount code: LA_Podcast to receive a 15% discount on the class.

This is the second interview in a series we are doing on Cost of Delay. The first interview, where Jim Hayden provided an overview of Cost of Delay can be found here: http://bit.ly/2lUDWFR In Part 2 of the series, Marty Bradley explains how Cost of Delay actually works. During the interview we discuss things like Weighted Shorted Job First (WSJF), how to determine relative Business Value of different features or projects and how to evaluate that value against different factors like risk. During the interview Marty refers to two different graphics that help explain Cost of Delay. Here are links to the two graphic files*: The Formula for Weighted Shortest Job First (WSJF)https://www.dropbox.com/s/slfrifz9pqqqgex/WSJF%20Formula.jpg?dl=0 The Cost of Delay Table https://www.dropbox.com/s/9lwrd0tjs5wcmqy/WSJF%20Table.jpg?dl=0" * These graphics are based on examples Marty was referencing in the interview. The originals can be found at http://www.scaledagileframework.com/wsjf/. Show Notes 00:08 Interview Begins 00:34 Background on Marty 01:47 Intro to the topic 01:54 It’s okay to be confused about what Cost of Delay actually is 02:36 Dave “mansplains” the basics of Cost of Delay 03:05 Why people are using Cost of Delay to prioritize work 05:00 Weighted Shortest Job First (WSJF) (see link above) 05:49 Using a table to calculate WSJF (see link above) 06:19 Using relative sizing to determine User Business Value and the other WSJF factors 06:44 What is “Business Value”? 08:39 How relative sizing works 09:10 How to use the table to get guidance on prioritization 11:07 The actual value of Cost of Delay may not be mathematically quantifiable, and that’s ok because it’s all about relative sizing 13:00 Be careful about bias and gaming the scores 13:24 Using the iPhone 7/Apple Bluetooth Headphones example 14:45 Adding columns to the table so that it works best for you 16:27 Deciding what to do first, second and what to kill 16:40 WSJF - a simple explanation 17:18 The formula for determining WSJF 17:44 Examples of how WSJF can help 19:50 Resources you can use to learn more about Cost of Delay 22:49 Understanding and measuring “value” 23:18 Are we getting smarter about understanding value or just delaying understanding it? 23:45 Key indicators of value and the importance of smaller batch size 25:32 Getting in touch with Marty 25:50 Podcast Close Links from the Podcast An Overview of Cost of Delay with Jim Hayden https://www.leadingagile.com/podcast/an-overview-of-cost-of-delay-with-jim-hayden-and-dave-prior/ The Principles of Product Development Flow by Don Reinertsen http://amzn.to/2m6u0xL Black Swan Farming http://blackswanfarming.com Contacting Marty: You can reach Marty: On the LeadingAgile site: https://www.leadingagile.com/guides/marty-bradley/ Email: marty.bradley@leadingagile.com LinkedIn: https://www.linkedin.com/in/martybradley/ Contacting Dave You can reach Dave: On the LeadingAgile site: https://www.leadingagile.com/guides/dave-prior/ On Twitter at twitter.com/mrsungo On his personal site at: www.drunkenpm.net Feedback/Questions If you have comments on the podcast, or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at dave.prior@leadingagile.com LeadingAgile CSM and CSPO Classes For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to: www.leadingagile.com/our-gear/training/ Use the discount code: LA_Podcast to receive a 15% discount on the class.

This podcast is the first in a series we intend to do on Cost of Delay. This podcast features LeadingAgile Enterprise Transformation Consultant, Jim Hayden, and Dave Prior discussing the ideas behind Cost of Delay at a fairly high level. If you are new to the subject, or are struggling with understanding it, this may help provide clarity on what Cost of Delay is and how it works. In a future podcast on this subject we will look at Cost of Delay from a more Reinertsen-centric viewpoint. We also plan to do at least one podcast that offers a case study on how Cost of Delay has been put into practice within an Agile organization. We will look at how they are using it to understand and prioritize work at the project, program and portfolio level. Show Notes 00:09 Podcast Begins 1:12 Why (and how) we are talking about Cost of Delay 2:52 Some background on Jim Hayden 3:16 What is Cost of Delay 3:37 Example 1: Laptop Manufacturer with a set window of sales opportunity 4:22 Example 2: Selecting between two different projects based on time to develop and ROI 5:10 Is Cost of Delay vs. opportunity cost? 5:54 Understanding the impact of deferring a release 8:43 What if you delay your launch and a competitor beats you to the market and your customer 9:15 Example 3: Apple launching the iPhone 7 without the bluetooth headphones 10:15 Visualizing and understanding the Cost of Delay across multiple projects 12:08 Why understanding the Cost of Delay and decision making process is not solely about revenue 14:31 When new projects arise… determining where to prioritize them against existing work 15:57 The organization’s cost for doing the project 17:03 Additional factors to consider when understanding the value a project provides 18:00 Standardizing rules around how to prioritize work 18:59 Decomposing work to understand the value better 19:51 Defining “value” and Cost of Delay within your organization 21:57 Why it is so important for a Product Owner to have a method for prioritizing work that is understood by all stakeholders 23:04 When value is vague, Cost of Delay becomes more important 23:57 Example 4: Prioritizing 12 projects across an entire year 27:39 Adding a new project mid-year 29:10 How does sunk cost factor in? 30:37 Again with the logic! 31:29 We value starting things, not finishing things 33:27 Why we want to work in small batches 33:51 Where to find more information on Cost of Delay 34:26 Getting in touch with Jim Hayden 34:39 Closing Links from the Podcast An Introduction to Cost of Delay by Derek Huether https://www.leadingagile.com/2015/06/an-introduction-to-cost-of-delay/ The Principles of Product Development Flow by Don Reinertsen http://amzn.to/2m6u0xL Black Swan Farming http://blackswanfarming.com Contacting Jim Hayden You can reach Jim on the LeadingAgile site at www.leadingagile.com/guides/jim-hayden/ Email: jim.hayden@leadingagile.com Contacting Dave You can reach Dave on the LeadingAgile site at www.leadingagile.com/guides/dave-prior/ On Twitter at twitter.com/mrsungo Or on his personal site at: drunkenpm.net Feedback/Questions If you have comments on the podcast, or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at dave.prior@leadingagile.com LeadingAgile CSM and CSPO Classes For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to: www.leadingagile.com/our-gear/training/ Use the discount code: LA_Podcast to receive a 15% discount on the class.

The Project Management Office (PMO) has traditionally been responsible for providing governance over projects, programs and portfolios; ensuring projects are managed according the standards set forth by the PMO; and to provide reporting on progress to leadership. When Agile is introduced into an organization, along with new ways of tracking work, self-organizing teams and new ways of understanding priority, the value the PMO provides comes into question. In a recent blog post, LeadingAgile SVP and Executive Consultant Marty Bradley addressed the question “Should the PMO Go Away?” In this episode of LeadingAgile’s SoundNotes, Marty and Dave dig deeper on this topic and explore what PMO’s (and PMO Leaders) need to do in order to remain relevant to an organization transitioning to Agile. Show Notes 00:08 Podcast Begins 00:35 What does a LeadingAgile Executive Coach actually do 01:40 When the Executives say “Stop saying Agile.”, it’s actually a good thing. 3:05 Should the PMO go away? Who’s asking and why? 07:12 Why do we need a PMO and governance if the teams are supposed to be self organizing? 08:38 If we do not have trust, how can we have self-organization and Agility? 09:39 All night deployments and the impact of not trusting the team 10:43 When the people who “know better” create a system that fosters missed deadlines and failure, they create a very dysfunctional form of predictability 12:15 How the PMO can maintain its’ relevancy in an organization transitioning to Agile. 13:27 How do we maintain the necessary non-agile elements when we transition to Agile? 14:55 How can we have more empathy for the members of the PMO and the massive personal and career change they are facing in maintaining the stability of a traditional approach while supporting the change to Agile? 16:29 Changing the focus and the metrics used to track the work 17:10 The impact on Development Managers 18:12 Why would I want to eliminate the need for my own position (if we transition from waterfall to Agile) 18:42 Coping with transition: “This is my job,…I got a family…What am I supposed to do?” 19:55 Maintaining a balance between preserving the necessary domain knowledge and changing as fast as you can 20:29 What PMO Leaders need to know before the Agile transition team shows up - “Not everything needs to be perfect Agile.” 23:51 If I am in a PMO and I want to get up to speed and maintain my own relevancy, what do I need to learn? 25:10 “I’d look at my company and figure out what is value in my company?” How do you define value? 27:02 Finding your organization’s own definition of value 27:46 Closeout Contacting Marty Email: marty.bradley@leadingagile.com Twitter: https://twitter.com/AskCoachMarty Contacting Dave Email: dave.prior@leadingagile.com Twitter: https://twitter.com/mrsungo Related Links: Should the PMO Go Away? (Marty’s blog post mentioned in the interview) http://bit.ly/2jwshAS Cost of Delay http://bit.ly/2jVLfx4 Agile Governance at eVestment - A More Agile Approach to PMO http://bit.ly/2khDBhq Agile Governance - An interview with Liana Dore from Agile 2016 http://bit.ly/2kRXj6F Kanban http://bit.ly/1cXGeK9 Lean Startup http://bit.ly/1ky8H1h Don Reinertsen “The Principles of Product Development Flow” http://amzn.to/2jYlyOY Feedback/Questions If you have comments on the podcast, or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at dave.prior@leadingagile.com LeadingAgile CSM and CSPO Classes For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to: www.leadingagile.com/our-gear/training/

Craig and Tony are at YOW! Conference and are privileged to spend some time with Don Reinertsen, who is considered one of the leading thinkers in the field of lean product development and author of numerous books including “Principles of Product Development Flow” “Principles of Product Development Flow” book and why there is a waterfall … Continue reading →

We had a chance to sit down with Steve Hazel of Sauce Labs. Steve is the CTO, co-founder of the Sauce Labs. There has been so much written lately about the role of automated testing in DevOps and what the role of QA is going forward. Listen to what an industry veteran and thought leader has to say on the subject. Also Steve recommended The Phoenix Project in our interview as a great book to read. Afterwards he had another great selection that we wanted to include: The Principles of Product Development Flow by Donald G. Reinertsen is never going to be a best seller, but it's a real engineer's book on process. If you aspire to push the state of the art forward beyond today's Agile and DevOps ideas, this book will show you a deeper and more rigorous way of thinking about product development processes.

One last week in mixtape format! I am completing a trip that is a mixture of vacation and a board meeting but that does not mean you have to forego your weekly SPaMCAST.  In place of our normal format, I am posting a mix tape of the answers to the “If you could change two things” question I have been asking interviewees for nearly ten years.  This week on SPaMCAST 393 we feature our top downloaded podcasts from the year 2010: SPaMCAST 85 – Cory Foy on Agile Coaching   http://bit.ly/1Qmmx0g Cory used his wishes to discuss the obsession with certification rather than performance and bring user into making critical business decisions so that usability is maximized. SPaMCAST 92 – Don Reinertsen on Product Development Flow  http://bit.ly/1WERCDZ Don used his wishes to ask that people understand the economics of product development and then to use that understanding to measure and reduce WIP queues. SPaMCAST 94 - Ivar Jacobson on SEMAT http://bit.ly/1SYSmhA Ivar discussed the SEMAT core defining software engineering and how SPaMCAST listeners can support the development of SEMAT. If these excerpts tickled your fancy listen to the whole interview by clicking on the links shown above. Next week we will return to regular programming with a thought provoking interview.

Global Product Management Talk is pleased to bring you episode 012 of... The Everyday Innovator with host Chad McAllister, PhD. The podcast is all about helping people involved in developing and managing products become more successful, grow their careers, and STANDOUT from their peers. Our Guest:  David Paulson has over 20 years of product development experience and still remembers his first day at work. That’s when he found out how inefficient the product development process was. He’s been working to fix that ever since. Highlights from the discussion include: Apply Lean product development to cut time to market in half and create successful products – something all innovators want to know how to accomplish!Lean has many different definitions, but in the product development context, it has three specific characteristics: (1) focus on value to the customer, (2) rapidly learn, and (3) maximize desired results while minimizing effort.In addition to the benefits of creating more profitable products, applying Lean product development also impacts the organizational culture, resulting in happier and more effective employees.First time David applied Lean product development to a project, the time-to-market decreased from the expected 30 months to 12 months, finished 20% under budget, and generated an additional $3 million profit by being early to market.Good books on the topic of Lean product development are from Don Reinersten, including “Managing the Design Factory” and “The Principles of Product Development Flow.” Read “Managing the Design Factory” first.

Vic is joined by Brett Palmer (@brett_palmer) and Larry Lawhead (@LarryLawhead) for a lively morning of Agile and coffee. Today our heroes discuss the following topics: Agile Planning - discussed WSJF and Donald Reinertsen's book "The Principles of Product Development Flow" User Story Mapping Roles in pair-coaching Servant Leadership AgileGathering.com has the info about our upcoming Agile Coach Camp US West, April 10-12, 2015

In this episode an interview with Don Reinertsen. We speak with Don about topics from his book The Principles of Product Development Flow - Second Generation Lean Product Development. We talk about Lean principles in the context of manufacturing and product development, and how these apply to software development. Don explains how variability is important for innovation, and how reduction in batch sizes and queues will improve flow. We discuss the economic model and the focus on quality vs utility. Don also discusses agile software methods like Scrum and Kanban and how they use some of the principles of product development. Don was in the Netherlands for the Lean & Kanban 2011 Benelux conference. His keynote 'Is It Time to Rethink Deming' can be viewed here courtesy of @agileminds. Read more from Don on the Reinertsen & Associates website. On twitter he is @dreinertsen. This interview was recorded on the 27th of September 2011 at the TouchDown Center in Haarlem. Interview by @freekl en @arnetim.Audio post-production by @mendelt Links for this podcast Book: Donald G. Reinertsen - The Principles of Product Development FLOW, Second Generation Lean Product Development. Celeritas Publishing, 2009. Book: Donald G. Reinertsen - Managing the Design Factory, a Product Developer's Toolkit. Free Press, 1997. Book: Jeffrey Liker - The Toyota Way. McGraw-Hill, 2003.

Welcome to the Software Process and Measurement Cast 92! The interview in the SPaMCAST 92 features a discussion with Don Reinertsen .  We discussed his current book, THe Principles of Product Development Flow including the concepts of queues, lean and economic value just to name a few topics. This was an incredible interview. For three decades Don Reinertsen has focused on improving the management of product development. His best-selling books have been perpetual favorites for hardcore engineering professionals. They lie dog-eared and underlined on engineering bookshelves around the world. Thousands of people have his public seminars at Caltech, The Management Roundtable, and overseas. Don constantly pushes the state of management thinking and delivers a rare combination of rigor, practicality, and clarity. His latest awarding winning book, The Principles of Product Development Flow: Second Generation Lean Product Development, has been praised as, “… quite simply the most advanced product development book you can buy.” Website:  http://www.reinertsenassociates.com/ e-mail:   don@ReinertsenAssociates.com Citrix GoToAssist Express is sponsoring SPaMCAST Solve technical issues faster with GoToAssist Express. Try it FREE for 30 days. On July 21st Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself was published by J. Ross Publishing.  Murali and I wrote this book from the standpoint of a project manager working in a software development organization.  We think this makes Mastering a unique guide that explains software project management in its entirety, including project acquisition and execution with backward linkages to concepts that play a facilitation role in successful project management. If you a project manager or know project managers buy yourself a copy and a second to lend co-workers! Contact information for the Software Process and Measurement Cast Email:  spamcastinfo@gmail.com Voicemail:  +1-206-888-6111 Website: www.spamcast.net Twitter: www.twitter.com/tcagley Facebook:  http://bit.ly/16fBWV Conferences and Speaking Engagements in 2010 (To Date)   ISMA Cinco in São Paulo September 13-15.  I will be one of the featured speakers.  THe title of the presentation is Function Points:  Past, Present and Future.  The website to get more information is http://www.ifpug.org/conferences/  I hope to see you there! Next! The next Software Process and Measurement Cast will feature the continuation the essay on process improvement and project management codes of ethics.