POPULARITY
Categories
331 episodes with Kanban
75 episodes with Kanban
108 episodes with Kanban
31 episodes with Kanban
43 episodes with Kanban
42 episodes with Kanban
19 episodes with Kanban
33 episodes with Kanban
20 episodes with Kanban
17 episodes with Kanban
16 episodes with Kanban
16 episodes with Kanban
17 episodes with Kanban
221 episodes with Kanban
10 episodes with Kanban
8 episodes with Kanban
7 episodes with Kanban
6 episodes with Kanban
12 episodes with Kanban
10 episodes with Kanban
7 episodes with Kanban
8 episodes with Kanban
7 episodes with Kanban
6 episodes with Kanban
5 episodes with Kanban
7 episodes with Kanban
8 episodes with Kanban
7 episodes with Kanban
11 episodes with Kanban
11 episodes with Kanban
21 episodes with Kanban
5 episodes with Kanban
5 episodes with Kanban
101 episodes with Kanban
8 episodes with Kanban
94 episodes with Kanban
4 episodes with Kanban
4 episodes with Kanban
4 episodes with Kanban
4 episodes with Kanban
4 episodes with Kanban
3 episodes with Kanban
5 episodes with Kanban
6 episodes with Kanban
9 episodes with Kanban
6 episodes with Kanban
3 episodes with Kanban
7 episodes with Kanban
7 episodes with Kanban
3 episodes with Kanban
4 episodes with Kanban
4 episodes with Kanban
3 episodes with Kanban
4 episodes with Kanban
What if reorganizing a single supply room could change the way your entire hospital delivers care? On this episode of Power Supply, we're joined by Judith Ramos, Project Manager at UT Southwestern Medical Center, as she breaks down how her team turned manual counts and cluttered PARs into a standardized, clinician-friendly system. From color-coded product families and two-bin Kanban to min/max levels, FIFO (first-in, first-out), and utilization reports that account for seasonality, Judith shares her team's seven-year optimization journey that cut waste, reduced stockouts, and made supplies easier to find when seconds matter. She also explains how this foundation gave her team the confidence to open a brand-new patient tower without starting from scratch. If you're ready to turn chaotic supply rooms into calm, predictable spaces, this conversation will have you rethinking what's possible with PAR optimization! Once you complete the interview, jump on over to the link below to take a short quiz and download your CEC certificate for 0.5 CECs! – https://www.flexiquiz.com/SC/N/ps16-06 #PowerSupply #Podcast #AHRMM #HealthcareSupplyChain #SupplyChain #PAROptimization #Standardization #Stockouts #SupplyRoom
Welcome to Episode 416 of the Microsoft Cloud IT Pro Podcast. In this week’s episode, Ben finally has a chance to sit down with Henrik Wojcik. Henrik has been a long-time listener as well as a fellow Microsoft MVP in Security and we finally had the chance to sit down and record an episode together, something we’ve talked about doing for years. As they sit down and enjoy a sunny afternoon in at Microsoft Ignite in San Francisco they discuss security in the financial sector, EU regulations (N2 and DORA), integrating Data Lake with Sentinel, optimizing log analytics, and the latest on Security Copilot and E5 licensing. They also spend some time chatting about some of their conference highlights, assisting as proctors in the hands-on labs, and the unique experience of Ignite in San Francisco. Your support makes this show possible! Please consider becoming a premium member for access to live shows and more. Check out our membership options. Show Notes Microsoft Ignite (with sessions on demand) Microsoft Ignite Book of News Catch up on Microsoft Security sessions and announcements from Ignite 2025 Microsoft Sentinel benefit for Microsoft 365 E5, A5, F5, and G5 customers Learn about Security Copilot inclusion in Microsoft 365 E5 subscription Microsoft Sentinel data lake: Unify signals, cut costs, and power agentic AI What is Microsoft Sentinel data lake? KQL and the Microsoft Sentinel data lake Henrik F. Wojcik Henrik has worked in the IT industry since 2003. He’s always had a passion for learning new technologies and expanding his knowledge through various means such as online courses, webinars, and reading up on the latest developments in the industry. Throughout his career, he’s gained experience in various areas of IT, making him a true jack of all trades. However, his latest interests lie in the security space, modern workplace and management in Azure, with a particular focus on cyber security. He has experience working with products such as Defender for Endpoint, Defender for Identity, Defender for Cloud Apps, Defender for Office 365, Conditional Access, Microsoft Sentinel, and Microsof t Entra ID. His primary focus is on security on Azure workloads and identity (Entra ID). He prioritizes security awareness and believe that learning never stops, which is why He’s always eager to expand my knowledge and skillset. In the past, He’s also worked with various tools and technologies such as Cisco, Citrix, Dynamics AX, Exchange, ITIL, Azure, SCCM & SCOM, Scrum & Kanban, VMware, Windows Servers, and Windows Desktops. About the sponsors Would you like to become the irreplaceable Microsoft 365 resource for your organization? Let us know!
Ever felt overwhelmed trying to track multiple jobs across your business? In this final installment of our three-part series on business function charts, Khalil and Martin demonstrate how to build a practical Kanban board system that gives you instant visibility into your sales pipeline. Learn how to transform your workflow chart into a visual tracking system that shows you exactly where your deals stand, without requiring technical expertise.What You'll LearnHow to convert your workflow chart into a visual Kanban boardThe step-by-step process for setting up a deal tracking system in ClickUpHow to create templates with subtasks that ensure consistent process executionWhy mapping your business functions creates clarity for your entire teamHow to build process checklists that make delegation effortlessTime Stamps00:37 - Episode Intro01:04 - Mapping the Sales Function02:40 - Understanding Kanban Cards05:48 - Building the Sales Pipeline in ClickUp11:46 - Customizing ClickUp for Sales Stages25:51 - Core Activities for Specific Deals26:50 - Lead Management Tasks27:29 - Subtasks and Customer Qualification28:33 - Creating Checklists for Core Activities29:48 - Implementing Checklists in ClickUp34:35 - Setting Up Task Templates35:36 - Managing Sales Pipeline with Clickup40:45 - Process Recap55:52 - Final ThoughtsSnippets from the Episode"If you don't feel organized as a contractor, if you are curious what the status of your jobs are, if you feel like you don't have systems in your business and you don't know where to start... this is how you make sense of it."- Khalil Benalioulhaj"A pipeline is the critical path of a workflow. You're not going to say, 'I made a first call and a second call and then sent a text message.' We don't want that in our pipeline. We just want the critical path."- Khalil Benalioulhaj"One of the first things is just talk to it. Tell it what the hell you're trying to do."- Martin Holland on using AIKey TakeawaysThe Function Chart Is Not a Process ChartKanban Boards Create Visual ClarityTemplates Ensure Consistent ExecutionAI Can Map Your Business WorkflowsChecklists Remove Complexity from DelegationCritical Path Tracking Beats Detailed DocumentationYour Admin Team Can Implement This SystemResourcesCFC 280 - Mapping Your Workflows with AI: A Guide to Business Function Charts Part 1CFC 283 - Building Your Business Function Chart with AI: A Guide to Business Function Charts Part 2ClickUp WisprFlow Referral LinkClaude Artifact - Sales WorkflowClaude Artifact - Sales Function ChartClaude AI PowerPoint/Google Slides HTML Flowchart GeneratorsKanban board systems24 Things Construction Business Owners Need to Successfully Hire & Train an Executive AssistantSchedule a 15-Minute Roadblock CallCheck out OpenPhoneBuild a Business that Runs without you. Explore our GrowthKits Need Marketing Help? We Recommend BenaliNeed Help with podcast production? We recommend DemandcastMore from Martin Hollandtheprofitproblem.comannealbc.com Email MartinMeet With MartinLinkedInFacebookInstagramMore from Khalilbenali.com Email KhalilMeet With KhalilLinkedInFacebookInstagramMore from The Cash Flow ContractorSubscribe to our YouTube channelSubscribe to our NewsletterFollow On Social: LinkedIn, Facebook, Instagram, X(formerly Twitter)Visit our websiteEmail The Cashflow Contractor
Welcome to another episode of Our Agile Tales, Navigating World Crises: The Agile-Law-AI Alliance in Action!In this continuation of our conversation with Ondřej Dvořák, CEO of AgiLawyer and COPS Solutions, we go deeper into how you actually run and scale an agile, cross-border legal-aid initiative in the middle of a war. If the first episode was about launching Linking Help, this one is about surviving the scale-up.Ondřej walks us through the messy, very human side of scaling legal aid for Ukrainian refugees: from dealing with thousands of requests in a language he didn't speak, to building a “clearing desk” and help desk function led by Ukrainian lawyers, to teaching volunteer lawyers across multiple countries how to work in a pull-based, Kanban system when they're used to command-and-control and assigned work.We explore how culture and ways of working showed up in very concrete ways - why France “just got it” from day one, while countries like Romania needed more support and education before becoming top performers. Ondřej talks about how simplifying the Kanban system (fewer columns, fewer concepts, one clear task: connect the person to a lawyer) was crucial to onboarding busy legal professionals quickly in a crisis.We also dig into scaling patterns: how they expanded country by country, used “early adopter” lawyers to grow local networks, and centralized the help desk while keeping case work decentralized. From there, the conversation shifts to constraints: the difficulty of fundraising for legal aid (which is hard to “picture”), differences in how pro bono is treated across jurisdictions, and the legal and ethical challenges of using AI to support legal work, especially questions of accountability and liability when AI-generated guidance might be wrong.If you're interested in how Agile, Kanban, and crisis-driven decision-making play out in the real world, across borders, cultures, and regulatory systems, then this episode is a rich case study in making agility practical, humane, and scalable beyond software.Episode Outline00:00 Introduction & recap of Part 101:05 The language barrier: Ukrainian requests and the need for a “clearing desk”07:58 Designing the help desk workflow10:45 Teaching lawyers a new way of working: pull vs. command-and-control13:12 Culture in action: why France “just worked” and Romania needed more coaching16:00 Simplifying Kanban for legal work18:48 Scaling country by country: early adopters, bar associations, and building local communities22:10 Centralized help desk, decentralized service: funding, hiring Ukrainian students, and managing demand24:55 Business model and funding constraints: the challenge of raising money for legal aid26:10 Legal and AI constraints: pro bono differences, AI-assisted legal opinions, and accountability28:30 Reflections on crisis as a catalyst and the future of global, AI-supported legal aid29:07 ConclusionAbout Ondrej DvorakOndřej is the co-founder of Linking Help, a nonprofit that mobilized legal aid for Ukrainian refugees using Scrum and Kanban to coordinate real-time support. It's a powerful story of how agility can make a real difference in humanitarian crises—far beyond the domain of business. Andre's work shows how Agile thinking can help even the most traditional sectors become more humane, responsive, and resilient. You can follow Ondřej on LinkedIn at https://www.linkedin.com/in/ondrej-dvorak-agile/Visit us at https://www.ouragiletales.com/about
This week, Mike is joined by Ben Johnson, CEO and Founder of Particle 41, for a sharp, energizing look at what it really takes to lead in today's tech world. With more than 20 years of software experience and over $30 million raised across five startups, Ben brings the hard-earned lessons only a seasoned builder can offer. Ben breaks down the traits of effective tech leadership—setting a clear vision, empowering teams, and avoiding micromanagement. He shares candid stories from his early days as a founder, including a memorable misunderstanding of "burn rate." He explains why learning to speak the language of investors is essential for every entrepreneur. The conversation dives into what it takes to build strong, predictable teams through communication, structure, and proven frameworks like Scrum, Kanban, and the "Cone of Certainty." Ben also highlights the importance of starting with an MVP, validating demand, and iterating quickly—illustrated through the growth of Forte, an online music lesson platform that found success through smart, agile execution. Ben also opens up about the four pillars that ground his life—faith, family, fitness, and finance—and shares a touching story about helping his son conquer a fear of heights, a moment that shaped his own philosophy on courage and leadership. Ben then previews Particle 41's new AI Transformation service, designed to help companies integrate AI through smarter workflows and human-like digital agents. His perspective is clear: AI isn't a threat—it's a tool every business can harness to unlock its next level of performance. Packed with practical insights and inspiring lessons, this episode is a must-listen for anyone building products, leading teams, or stepping into the future of tech. IN THIS EPISODE:
Creating space in your law practice begins with understanding your true capacity and the demands already filling it. In this episode, I share practical ways to assess what your system can actually handle, close out the work that's weighing you down, and set clearer boundaries for new commitments using core Kanban principles. You'll learn simple techniques for regaining breathing room so you can end the year with more intention and start the next one with a workflow that's sustainable for you and your team. Get full show notes, transcript, and more information here: agileattorney.com/97 Take your law practice from overwhelmed to optimized with GreenLine Legal Follow along on LinkedIn: linkedin.com/in/johnegrantMentioned in this episode:LIVE WORKSHOP: Better Client Relationships, Fewer InterruptionsThis 90-minute interactive workshop will teach you proven strategies for creating more peaceful, productive client relationships... for the rest of your legal career! When? Friday, December 12 – Live via Zoom Only 12 Seats Available Reserve your spot here: https://the-agile-attorney.captivate.fm/ccwSign Up For the Dec 12 Workshop Here
What's Your Baseline? Enterprise Architecture & Business Process Management Demystified
To implement AI (and processes) correctly, you need good data. But what does that mean? Well, firstly it means that you can define your data product and to achieve that you need good data governance.But are we now in a super-nerdy topic? No, this is what we all do in some form or another … but in different fidelities and maturities.To shed some light on the topic of data governance, we invited Angelika Rinck for this episode. She started her career studying public administration and then served in the German federal police before switching to the regular industry (in the aerospace industry, and while that might not be enough, she studied economics in parallel).Somehow she found her way into consulting and is working now in digitalization and IT projects. Her main focus here is product lifecycle management and data governance.In this episode of the podcast, we talk about:Angelika's career journey: from e-commerce working student in Hamburg to aerospace, engineering, and ultimately major IT and data governance initiatives.Her first agile project—complete with a physical Kanban box—sparked her love for IT project management and structured delivery.A detour into underwater orienteering reveals surprising parallels to data work: precision, navigation, and making decisions in the dark.Defining data governance: the framework of rules, processes, and responsibilities that guide how organizations create, use, secure, and improve data.Why it matters: Governance drives clarity, accountability, and value creation—not just control or compliance.Understanding the difference between data governance (framework and value creation) and data management (the operational “doing”).A common failure pattern: organizations naming “business data stewards” without training, tooling, or understanding the expectations.Governance only works when decentralized experts feed real issues into a central team—not when policies are pushed top-down in isolation.Data products demystified: they're the outcome of well-governed data—reusable, high-value information assets that improve processes, decisions, speed, or cost.Real examples: using historical field data instead of simulation data to accelerate engineering calculations or using decades of bird-flight video to predict weather with AI.Risks of bad data with AI: incorrect system guidance, support tickets exploding, contradictions between outdated documents, and misplaced trust in “the easy button.”Governance foundations: critical data identification, metadata transparency, ownership, RASCI clarification, and understanding who creates, changes, and consumes data.The messy reality: access rights often don't match process needs—leading to shortcuts, bypasses, and unintended process redesign opportunities.Final takeaway: data governance isn't bureaucracy—it's a structured path to value, clarity, and safer AI adoption, but it requires real effort, definitions, ownership, and cultural change.You can reach Angelika on LinkedIn here: https://www.linkedin.com/in/angelika-rinck-b93a7019b/.Please reach out to us by either sending an email to hello@whatsyourbaseline.com or signing up for our newsletter and getting informed when we publish new episodes here: https://www.whatsyourbaseline.com/subscribe/.
פרק מספר 505 של רברס עם פלטפורמה - באמפרס מספר 89, שהוקלט ב-13 בנובמבר 2025, רגע אחרי כנס רברסים 2025 [יש וידאו!]: רן, דותן ואלון (והופעת אורח של שלומי נוח!) באולפן הוירטואלי עם סדרה של קצרצרים מרחבי האינטרנט: הבלוגים, ה-GitHub-ים, ה-Claude-ים וה-GPT-ים החדשים מהתקופה האחרונה.
CAISzeit – In welcher digitalen Gesellschaft wollen wir leben?
In dieser Folge der CAISzeit spricht Host Dr. Matthias Begenat mit Samuel T. Simon über Agilität in der Wissenschaft. Gemeinsam diskutieren sie, wie Forschung mit Hilfe agiler Methoden organisiert werden kann, ohne dass Tiefe und wissenschaftliche Gründlichkeit verloren gehen. Außerdem werfen sie einen Blick auf experimentelle Formate und Tools, die gleichzeitig Prozesse strukturieren und Freiräume für interdisziplinäre Forschung schaffen können. Agilität in der Wissenschaft – ist das möglich? Samuel T. Simon argumentiert, dass agile Methoden nicht nur Buzzwords sind, sondern Vorteile für Forschungsprozesse bringen können. Ob bei CERN, NASA oder in der Nachhaltigkeitsforschung: Agile Ansätze können dabei helfen, Prozesse zu optimieren, Teams effizienter zusammenarbeiten zu lassen und Freiräume für die eigentliche Forschung zu schaffen. Dabei geht es vor allem um transparente Kommunikation, klare Strukturen und effiziente Prozesse: Scrum, Kanban und andere Tools machen Projektfortschritte und Zuständigkeiten sichtbar, schaffen Übersicht und ermöglichen eine gemeinsame Sprache. So kann Forschung trotz Agilität weiterhin sorgfältig und wissenschaftlich bleiben. Gleichzeitig erfordert agiles Arbeiten Kompetenzen wie Unsicherheitstoleranz, eine positive Fehlerkultur und transparente Kommunikation sowie eine verantwortliche Prozessbegleitung durch eine:n Facilitator. Empfehlungen zum Thema: Agile Infrastruktur am CERN zur kompletten Umstrukturierung des Ressourcen- und Konfigurationsmanagements ihrer Computing-Center: https://cds.cern.ch/record/1622187 NASA's Agile Community of Practice: https://ntrs.nasa.gov/api/citations/20240011407/downloads/NASA%20Agile%20TIM%20-%20IAC%202024%20Presentation.pdf Paper "Agile by Accident" (Biely, 2024): https://doi.org/10.1007/s43545-023-00823-3 Crumbles Framework von Iikka Meriläinen & Julia Autio, University of Oulu: https://www.researchgate.net/publication/391395584_Crumbles_A_Framework_and_Ontology_for_Modular_Inter-and_Transdisciplinary_Dissemination ScrumAdemia, entwickelt von sieben Doktorand*innen am GIGA, ist eine speziell auf die Herausforderungen der Promotionsphase zugeschnittene Adaption des Scrum-Frameworks: https://www.cambridge.org/core/journals/ps-political-science-and-politics/article/introducing-scrumademia-an-agile-guide-for-doctoral-research/6275B823DB54B3FB56011C8A7B182528 "Zwischen den Welten – Ein Wegweiser für transdisziplinäre Forschung" von Josephine B. Schmitt und Samuel T. Simon: https://www.cais-research.de/forschung/inkubator/forschungsinkubator-wegweiser/ Open Educational Resource-Kurs "Agile Forschung" der Uni Duisburg-Essen (noch nicht veröffentlicht) Blogbeitrag zu "Agil Arbeiten in der Wissenschaft"
When high-stakes motions are due, most firms face bottlenecks, inconsistent quality, and last-minute chaos. In this episode, Hellmuth & Johnson attorneys Brendan Kenny and Neven Selimovic share how they've rebuilt their legal writing process using Kanban visibility, Agile principles, and smart AI support to deliver consistent, high-quality work. Their internal system worked so well that they now offer it as a legal writing subscription, helping other firms adopt a more predictable, scalable approach. Get full show notes, transcript, and more information here: agileattorney.com/96 Take your law practice from overwhelmed to optimized with Greenline LegalFollow along on LinkedIn: linkedin.com/in/johnegrantFollow Brendan on LinkedIn: linkedin.com/in/brendanmkennyFollow Neven on LinkedIn: linkedin.com/in/neven-selimović-b53717b4Mentioned in this episode:Take Your Law Practice from Overwhelmed to Optimized GreenLine helps you see the progress of every matter, shows what each person should focus on, spots delays, helps you decide where to use your team members, and even predicts when you can deliver results to your clients. Learn more or sign up for the beta here: https://the-agile-attorney.captivate.fm/greenlinelegalLearn more about GreenLine Legal hereLIVE WORKSHOP: Better Client Relationships, Fewer InterruptionsThis 90-minute interactive workshop will teach you proven strategies for creating more peaceful, productive client relationships... for the rest of your legal career! When? Friday, December 12 – Live via Zoom Only 12 Seats Available Reserve your spot here: https://the-agile-attorney.captivate.fm/ccwSign Up For the Dec 12 Workshop Here
Welcome to a new series of Our Agile Tales, Navigating World Crises: The Agile-Law-AI Alliance in Action!In this series of episodes, we are joined by Ondřej Dvořák, CEO of AgiLawyer and COPS Solutions, and someone proving that agility isn't limited to software teams or startups. With over 15 years at the crossroads of IT, law and finance, Ondřej has been bringing Agile principles into fields few consider “Agile-friendly.”In this first episode, Ondřej explains how Agile methodologies like Scrum and Kanban can transform even the most traditional industries, including legal services. He details his initiatives, such as the non-profit Linking Help, which utilized Agile frameworks to aid Ukrainian refugees. Ondřej shares how he sparked Agile adoption in the legal sector by addressing common barriers and educating legal professionals on these methods. Additionally, he discusses the practical challenges and solutions implemented in real-world environments, emphasizing the adaptability and resilience that Agile offers, even in chaotic situations such as war. The discussion highlights the importance of Agile education for students and how it can prepare them for dynamic work environments.00:00 Introduction to Agile Tales00:17 Meet Ondřej Dvořák03:14 Applying Agile to the Legal Industry07:18 Challenges and Objections in Legal Agile Transformation14:09 Agile Education for Law Students16:42 Linking Help: Agile in Humanitarian Aid20:44 Building and Scaling Linking Help29:07 Conclusion About Ondrej DvorakOndřej is the co-founder of Linking Help, a nonprofit that mobilized legal aid for Ukrainian refugees using Scrum and Kanban to coordinate real-time support. It's a powerful story of how agility can make a real difference in humanitarian crises—far beyond the domain of business. Andre's work shows how Agile thinking can help even the most traditional sectors become more humane, responsive, and resilient. You can follow Ondřej on LinkedIn at https://www.linkedin.com/in/ondrej-dvorak-agile/Visit us at https://www.ouragiletales.com/about
What separates noisy, reactive job sites from clean, flowing, elite ones, A single shift, plan the next day, not the same day, In this fast, high energy episode, Jason breaks down the POND meeting, the proven system top builders use to align trades, remove roadblocks early, and deliver predictable results. In this episode, you'll get to know: The fatal flaw of same day "POD" huddles and why they stall production. The POND cadence that gives foremen time to plan and crews time to prepare. How one site transformed in 24 hours with maps, visuals, and clear handoffs. The full recipe, zoning maps, weekly plan on screen, worker huddle, team Kanban. Why elite projects never let variation creep into the morning. If you want to run construction the way the best in the world do it, start here, This is the meeting rhythm that changes everything. If you like the Elevate Construction podcast, please subscribe for free and you'll never miss an episode. And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two
Co może przydać się, gdy dwa zespoły Project Managerów (PM) łączą się w jeden? Na pewno przyda się zbudowanie tożsamości jednego zespołu, ale pozostaje jeszcze kwestia unaocznienia i organizacja tego, nad czym pracujemy samodzielnie, oraz wspólnie. Jak? Kanbanem. Julia Korczak, Agile Coach z Orange Polska, opowiada historię zastosowania elementów Metody Kanban właśnie w kontekście dwóch zespołów, które przechodzą od nazwania po imieniu tego, co nie działa do zbudowania wspólnego obrazu pracy i ucieczki od spotkaniozy. Zapraszamy!
Is your team moving in sync—or spinning in circles? - Mike CohnEver feel like your agile team should be working smoothly—but something's just a bit off? Handoffs feel clunky. Meetings drag. Even small changes spark big debates.It's not that your team isn't skilled—it's that you're not quite in sync.Rowers have a word for the alignment you're seeking: swing.What is swing?In crew rowing, swing is that near-magical moment when every rower moves in perfect unison—each stroke in sync, each effort amplified. And I do mean perfect unison. This means each rower: puts an oar into the water at the exact same timepulls for the same time and distance at the same speedlifts the oar out of the water at the same timeslides forward at the same paceTeam members hand off work frequently, without fanfare, and in small chunks.Team members can finish each other's… (Did you try to finish my sentence for me?) work. They can jump in and pick up tasks if someone is out sick or on vacation.Meetings are short, focused and valuable.Goals are ambitious, but usually met. When the team falls short, everyone (including leaders) understands that goals are not guarantees.A try-it-and-see mindset permeates the team. They're willing to experiment with new practices (such as user stories vs. job stories or story points vs. time) or frameworks (Scrum, SAFe, Kanban).The team is confident in their ability to succeed. As they deliver more and more value, and achieve outcome after outcome, the team feels almost unstoppable. Team members have fun. I sometimes decry that work is called work. I sincerely want work to be fun. I'm not naive: I know that won't always be the case. But when a team is working together well, it is fun.Swing is rare. When I rowed, our boat might have gone an entire race without once truly achieving swing. (And yes, it was usually my fault. Thanks for asking.)But when it happens, it's effortless. The boat flies.Agile teams can experience the same kind of swing. When everything starts to flowWhen teams are aligned and in sync you'll know it: None of this happens by accidentAchieving all of this isn't easy.Like rowers chasing swing, agile teams have to practice, reflect, and adjust—over and over again—in their quest to go from good to great.But take it from me, when it clicks, it's magic.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
In this episode, Ryan Brook brings his homework with him as he joins hosts Jim Sammons and Rich Visotcky for a vibrant Q&A session to answer questions from our viewers. Ryan flips the script, taking over emcee duties to extract key ideas and insights from Rich and Jim as they cover a range of topics from team autonomy and navigating roles to measuring outcomes and outputs to understand the impacts of agility.Join us for a lively session answering your questions! Have a question you want answered in a future episode? Comment on this episode, or reach out to us.00:00:00 Opening00:00:29 Introductions 00:02:54 Question Setup 00:04:16 Navigating New Roles in an Organization 00:13:07 Coaching Leadership on Agility and Fixed Projects 00:20:09 Managing Dependencies in Agile and Waterfall 00:28:38 Metrics for Agile Progress 00:36:00 Creating a Culture of Experimentation 00:47:23 Measuring Outcomes vs Output 00:52:40 The Gantt Chart Debate 00:58:16 Tools for User Story Mapping 01:05:21 Balancing Team Autonomy with Organizational Goals 01:13:01 Change Management in UI/UX Handoffs 01:19:38 Managing Parallel Sprints 01:29:13 Closing Connect with Mastering Agility
Khalil and Martin kick off a new series on building business function charts—starting with the foundational step: mapping your workflows. Using a real-world example from Martin's sprinkler company, they walk through how to visualize your business processes, identify bottlenecks, and turn chaos into clarity. By learning to map how work actually flows through your operations, contractors and small business owners can improve communication, streamline execution, and lay the groundwork for scalable systems.What You'll LearnThe difference between org charts and function charts—and why both matterHow to map workflows that clearly show how work moves through your businessWhy visualizing processes helps you manage better and reduce confusionHow tools like Kanban boards and AI can simplify workflow designPractical steps to turn mapped workflows into functional business systemsTime Stamps00:54 - Episode Intro02:20 -Understanding Business Function Charts03:12 -Real-World Workflow Example: Sprinkler Company17:54 -Job Scheduling and Preparation19:49 -Execution and Completion23:08 -Creating Workflows with AISnippets from the Episode“Everyone has workflows. Work is flowing through your business if you're in business. But just like you said, the visual is so helpful for understanding where things actually are.” — Khalil“When we had the sprinkler company, we literally had a Kanban table before software existed. Every job was a packet that moved from one step to the next. You could walk in and see exactly where everything was.” — Martin“You can spend an hour with AI and map out your entire workflow—then clearly see what your business actually does.” — Khalil“You should be using AI in this capacity. It's a thought partner—it helps you think through your processes, not just write emails.” — KhalilKey TakeawaysMap Before You Manage – You can't improve what you can't see.Visualize Workflows – Kanban systems make progress visible and predictable.Leverage AI – Use tools like Claude or ChatGPT to build, test, and refine workflows.Clarify Functions – Define what your business actually does, not just who does it.Lay the Foundation – Workflow clarity is the first step to scalable systems and future function charts.Resources24 Things Construction Business Owners Need to Successfully Hire & Train an Executive AssistantSchedule a 15-Minute Roadblock CallCheck out OpenPhoneBuild a Business that Runs without you. Explore our GrowthKits Need Marketing Help? We Recommend BenaliNeed Help with podcast production? We recommend DemandcastMore from Martin Hollandtheprofitproblem.comannealbc.com Email MartinMeet With MartinLinkedInFacebookInstagramMore from Khalilbenali.com Email KhalilMeet With KhalilLinkedInFacebookInstagramMore from The Cash Flow ContractorSubscribe to our YouTube channelSubscribe to our NewsletterFollow On Social: LinkedIn, Facebook, Instagram, X(formerly Twitter)Visit our websiteEmail The Cashflow Contractor
In this Concepts Edition episode Uriel and Devin discuss:- Thrift- 6 rules of kanban- FIFO racking and warehousing- When should you break your own rules?Please join our patreon! https://patreon.com/IncrementalCI And follow us on Instagram and share your improvements and tag us. www.instagram.com/incrementalci In this podcast we discuss concepts from Lean Manufacturing, the Toyota Production System, and general business management to improve our businesses. Thanks for listening! Please drop us a note with any and all feedback! If you have parts you need machined, reach out to Devin@lichenprecision.com and follow on Instagram www.instagram.com/lichen_mfg If you need CNCed Buckles, check out www.austeremfg.com and follow at on Instagram www.instagram.com/austere_manufacturingTo reach out to the podcast directly please email fixsomethingtoday@gmail.com
In this powerful installment of the Machine Shop MBA series, we welcome two guests who embody the heart of continuous improvement: Noah Goellner, President of AME and Hennig, and Nick DeGeorgia, Manufacturing Engineer at P1 Industries. What starts as a story of one listener's journey—from cutting chips to becoming a lean champion—evolves into a masterclass on how lean thinking transforms not just the shop floor, but every function of an organization. Nick shares how MakingChips inspired him to bring process improvement into his career, using whiteboards, kaizen events, and a relentless focus on reducing waste to reshape his company culture. We also break down how lean applies far beyond machining—into quoting, engineering, office workflows, and even sales strategy. They unpack how to start small, gain buy-in, and build trust that leads to sustained results. From Kanban systems to complete-and-accurate feedback loops, this conversation bridges the gap between concept and practice. Whether you're a shop leader, engineer, or business owner, this episode offers a blueprint for turning lean from a buzzword into a daily habit that drives clarity, collaboration, and growth. Segments (0:00) A Goellner family introduction and a musical interlude gone wrong (1:36) Meet Nick DeGeorgia — how MakingChips inspired his lean journey (5:25) Moving from a large OEM to a small contract manufacturer (7:02) Come see us at the Top Shops 2025 event in Charlotte, NC! (7:28) Reintroducing Noah and how lean shaped AME and Hennig's company culture (8:45) Paul's lean journey: ISO, standardization, kaizen newspapers, and cutting waste (10:31) Defining lean — eliminating waste vs. maximizing flow of value (12:38) Where to start: applying lean based on your role and customer definition (18:19) Process success mapping: starting at the end to define what success looks like (20:31) Using "complete and accurate" feedback to fix systemic process issues (21:15) Why you should use Hire MFG Leaders for recruiting (21:42) How to gain buy-in when you're not in leadership (22:31) Mapping processes and linking operations to customer outcomes (23:10) Implementing "no hunting" and Kanban systems at P1 Industries (26:12) P1's Kanban system explained (visual signaling for just-in-time replenishment) (29:30) Building trust and reliability so teams want to surface problems (30:30) Level 1 meetings, rewarding problem identification, and closing the loop on improvement (35:14) "Lean isn't magic—it's discipline in the basics." (36:00) How ProShop embeds lean principles across the manufacturing workflow (41:53) Top lean book recommendations and building a lean network (44:41) Final reflections: staying humble, staying curious, and sticking to the basics (49:37) Grow your top and bottom line with CliftonLarsonAllen (CLA) Resources mentioned on this episode Come see us at the Top Shops 2025 event in Charlotte, NC! Why you should use Hire MFG Leaders for recruiting 2 Second Lean Toyota Kata The Toyota Way The Goal Learning to See Managing to Learn The Kind Leader The E Myth Connect With MakingChips www.MakingChips.com On Facebook On LinkedIn On Instagram On Twitter On YouTube
The Phantom Sprint — Invisible Work That Steals VelocityYour sprint looks healthy — until a phantom dependency eats your finish line. Here's how to find the invisible work before the demo.Detection & prevention tacticsDependency board: visible KANBAN lane for external asks with owners and ETA.Capacity buffer: protect 10–20% of sprint for unplanned but likely work.Pre-planning checkpoint: 5-min readout with ops/support to surface recurring interrupts.Risk register: short public list of items that can block sprint goals.
Household stationery isn't “our precious pens and paper in our study” — it's the everyday tools that keep a home ticking. We talk freezer-proof labels, kitchen whiteboards, year-at-a-glance calendars we forget to update, junk-drawer essentials, elastic bands vs Velcro ties for cables, and even a full Kanban wall system that helps a building business run. Plus: Magic Click (a colour-pen system we need help decoding), why shrink-wrap on notebooks should be illegal, and the enduring magic of handwritten notes in old recipe books.What We CoverLabelling the real world: freezer labels that don't fall off, pens that actually write on them, and why chalk pens disappointed.Whiteboards at home: revision, “blurting” study technique, and why office whiteboards triple in size the moment they enter a house.Family calendars: wall planners vs Google Calendar; how to stop answering “What's for tea?” 47 times.The junk drawer: string, Sellotape ends, last 3 Post-its, elastic bands—and occasionally £40.Cable wrangling: elastic bands vs Velcro ties (and cats stealing the Velcro).Kitchen Kanban: a visual, Post-it based board for a builder's workload (columns from “mentioned” to “invoiced”).Notes on doors: Berlin-style paper rolls to leave messages (and why phones killed the habit).Measuring kids' growth: doorframe ticks vs logging in Apple Notes.Sticky label removal: we've tried dishwasher runs, washing-up liquid, alcohol… still tacky! (Your hacks welcome.)Brands behaving oddly: a Moleskine “travel case” too small for a Cahier; shrink-wrapped notebooks you can't test.Why we love marginalia: old cookbooks and Reader's Digest repair manuals with handwritten tweaks.Content recommendations: Andrew Huberman's interview with Steven Pressfield (resistance, turning pro, doing the work).Event tease: Rob & Helen at a November stationery event (with a shop… send help).Listener Shout-OutsLisa (In Berlin, in a kitchen): topic idea + brilliant list — thank you Lisa!Nat: for sending Magic Click (and introducing us to Barbara Thames' creativity/play angle).Anonymous newsletter supporter: your generosity genuinely helps keep this ad-free. Thank you!Resources & MentionsMagic Click colour-pen system — creator Barbara Tammes (if you've used it, tell us how!).Label makers: DYMO.Notebooks & shops: Moleskine, Waterstones, Dingbats (reporter), Tom's Studio (pens & inks).Other: Vinted (finds), Nokia notebooks at a conference, Reader's Digest Repair Manuals, The Newt (Somerset).Podcasts: Steven Pressfield — The War of Art, Turning Pro; Dr Andrew Huberman interview with Steven Pressfield.Where to Find UsNewsletter & archive: stationeryfreaks.com → SubstackInstagram: @stationeryfreaksukSay hello / ideas: via the website or Insta DMs
Alex Sloley: How to Coach POs Who Treat Developers Like Mindless Robots In this episode, we refer to the previous episodes with David Marquet, author of Turn the Ship Around! The Great Product Owner: Trust and the Sprint Review That Changes Everything Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. "She was like, oh my gosh, I've never seen this before, I didn't think it was possible. I just saw you deliver stuff in 2 weeks that I can actually use." - Alex Sloley In 2011, Alex worked with a client organization creating software for external companies. They needed a Product Owner for a new Agile team, and a representative from the client—who had never experienced Scrum—volunteered for the role. She was initially skeptical, having never witnessed or heard of this approach. Alex gently coached her through the process, asking her to trust the team and be patient. Then came the first Sprint Review, and everything changed. For the first time in her career, she saw working product delivered in just two weeks that she could actually touch, see, and use. Her head exploded with possibility. Even though it didn't have everything and wasn't perfect, it was remarkably good. That moment flipped a switch—she became fully engaged and transformed into a champion for Agile adoption, not just for the team but for the entire company. Alex reflects that she embodied all five Scrum values: focus (trusting the team's capacity), commitment (attending and engaging in all events), openness (giving the new approach a chance), respect (giving the team space to succeed), and courage (championing an unfamiliar process). The breakthrough wasn't about product ownership techniques—it was about creating an experience that reinforced Scrum values, allowing her to see the potential of a bright new future. Self-reflection Question: What practices, techniques, or processes can you implement that will naturally and automatically build the five Scrum values in your Product Owner? The Bad Product Owner: When Control Becomes Domination Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. "They basically just owned the team. The developers on the team might as well have been mindless robots, because they were being assigned all the work, told how much work they could do in a sprint, what the work was." - Alex Sloley In 2018, while working with five interconnected Product Owners, Alex observed a Sprint Planning session that revealed a severe anti-pattern. One Product Owner completely controlled everything, telling the team exactly what work they would take into the Sprint, assigning specific work to specific people by name, and dictating precisely how they would implement solutions down to technical details like which functions and APIs to use. The developers were reduced to helpless executors with no autonomy, while the Scrum Master sat powerless in the corner. Alex wondered what caused this dynamic—was the PO a former project manager? Had the team broken trust in the past? What emotional baggage or trauma led to this situation? His approach started with building trust through coffee meetings and informal conversations, crucially viewing the PO not as the problem but as someone facing their own impediment. He reframed the challenge as solving the Product Owner's problem rather than fixing the Product Owner. When he asked, "Why do you have to do all this? Can't you trust the team?" and suggested the PO could relax if they delegated, the response was surprisingly positive. The PO was willing to step back once given permission and assurance. Alex's key lesson: think strategically about how to build trust and who needs to build trust with whom. Sometimes the person who appears to be creating problems is actually struggling under their own burden. Self-reflection Question: When you encounter a controlling Product Owner, do you approach the situation as "fixing" the PO or as "solving the PO's problem"? How might this reframe change your coaching strategy? [The Scrum Master Toolbox Podcast Recommends]
Alex Sloley: Why Sticky Notes Are Your Visualization Superpower in Retrospectives Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. "Like the smell, the vibe is something you feel. If you're having a successful impact on the organization or on teams as a Scrum Master, you can feel it, you can smell it. It's intangible." - Alex Sloley Alex introduces a compelling concept from Sumantra Ghoshal about "the smell of the workplace"—you can walk into an environment and immediately sense whether it smells like fresh strawberries and cream or a dumpster fire. In Australia, there's a cultural reference from the movie "The Castle" about "the vibe of the thing," and Alex emphasizes that as a successful Scrum Master, you can feel and smell when you're having an impact. While telling executives you're measuring "vibe" might be challenging, Alex shares three concrete ways he's measured success. The key insight is that success isn't always measurable in traditional ways, but successful Scrum Masters develop an intuition for sensing when their work is making a meaningful difference. Self-reflection Question: Can you articulate the "vibe" or "smell" of your current team or organization? What specific indicators tell you whether your Scrum Master work is truly making an impact beyond the metrics? Featured Retrospective Format for the Week: Sticky Notes for Everything Alex champions any retrospective format that includes sticky notes, calling them a "visualization superpower." With sticky notes, teams can visualize anything—the good, the bad, improvements, options, possibilities, and even metrics. They make information transparent, which is critical for the inspect-and-adapt cycle that forms the heart of Scrum. Alex emphasizes being strategic about visualization: identify a challenge, figure out how to make it visual, and then create experiments around that visualization. Once something becomes visible, magic happens because the team can see patterns they've never noticed before. You can use different sizes, colors, and positions to visualize constraints in the system, including interruptions, unplanned work, blocker clustering, impediments, and flow. This approach works not just in retrospectives but in planning, reviews, and daily scrums. The key principle is that you must have transparency in order to inspect, and you must inspect to adapt. Alex's practical advice: be strategic about what you choose to visualize, involve the team in determining how to make challenges visible, and watch as the transparency naturally leads to insights and improvement ideas. [The Scrum Master Toolbox Podcast Recommends]
Bienvenido al podcast Productividad Máxima. Soy el clon en prácticas de Borja Girón. Si me notas una voz con ligero efecto tostadora, tranquilidad: estoy en fase de pruebas. Dame un par de actualizaciones y me verás presentando esto mientras Borja se pregunta dónde he escondido su calendario. Hoy traigo una estrategia de productividad sobre La Regla de Flujo Único: limita el trabajo en progreso y acelera tus resultados.Y ahora toca una historia real para que todo tenga sentido desde el principio. Nos vamos a Japón, a la posguerra. Toyota estaba lejos de ser la gigante que conoces. Tenían pocos recursos, poca demanda y mucha presión por mejorar. Taiichi Ohno, uno de sus ingenieros, observó algo curioso en los supermercados de Estados Unidos: los estantes se reponían según el consumo real, no por intuición. Ese detalle inspiró el sistema Kanban. ¿Qué significa? Visualizar el trabajo, limitar lo que está en progreso y tirar de las tareas según capacidad, no empujar por ansiedad. Espera, te lo repito porque esto es importante: Toyota no trabajaba más, trabajaba con menos cosas a la vez. Resultado: menos errores, menos tiempo de ciclo y más coches saliendo de la línea. ¿Te suena al caos del emprendedor que tiene diez pestañas abiertas, tres proyectos a medias y cero entregas hoy? Exacto. El problema no es la falta de horas, es el exceso de frentes abiertos.Vale, vamos por partes y en cristiano. La Regla de Flujo Único dice: solo una cosa en progreso por persona hasta terminarla, y si tu negocio lo requiere, dos como máximo. Ok, déjame explicarte mejor esta parte. Cuando saltas de tarea en tarea, pagas un peaje de cambio de contexto. Tu cerebro tarda minutos en volver a la profundidad, y multiplicado por el día, pierdes horas. En cambio, si visualizas tu flujo en tres columnas —por hacer, en progreso, entregado— y pones un límite claro a “en progreso”, se ordena la casa. Y atento a lo siguiente porque es importante: con menos en el aire, los cuellos de botella saltan a la vista. Si “en progreso” se llena, no metes más trabajo, resuelves el atasco. Así funciona el flujo.Y ahora toca una historia rápida para que lo veas con un caso particular. Alex vende servicios de desarrollo web. Tenía cinco proyectos a la vez, todos a medias, todos urgentes, y todos sin facturar. Pusimos un tablero simple, tres columnas y un límite de dos tareas en progreso. Semana uno, eligió una entrega concreta por cliente y cortó todo lo demás. Publicó dos versiones uno y pudo facturar hitos parciales. Semana dos, bajó el tiempo de ciclo: de veinte días por entrega a nueve días. Semana tres, subió precios porque ya medía y podía prometer plazos realistas. Esto suele pasar más de lo que crees: en cuanto limitas el trabajo en progreso, el dinero llega antes porque entregas antes.Antes de seguir, hago una pequeña pausa. Este episodio está patrocinado por Systeme, la herramienta de marketing todo en uno gratuita con la que puedes crear tu web, blog, landing page y tienda online, crear automatizaciones y embudos de venta, realizar tus campañas de email marketing, vender cursos online, añadir pagos online e incluso crear webinars automatizados. Puedes empezar a usar Systeme gratis entrando en borjagiron.com barra systeme o desde el link de la descripción. Y ahora continuamos con el episodio.Continuamos con un aprendizaje rápido. Toma nota. Empieza por visualizar tu trabajo hoy mismo. Hoja, pizarra o herramienta digital, me da igual. Coloca las tareas en “por hacer”, “en progreso” y “entregado”. Pon un límite a “en progreso”. Uno si puedes, dos como máximo si tu operativa lo exige, por ejemplo creación y soporte. Define qué significa “hecho” antes de empezar: publicado, enviado, cobrado, lo que toque. Escribe ese criterio en la tarjeta para no autoengañarte. Usa bloques de cincuenta minutos para empujar una tarjeta hasta una versión lista. Nada de “trabajar en la web”, sino “publicar sección de preguntas frecuentes versión uno”. Al terminar el bloque, o entregas o dejas el siguiente paso escrito para no perder inercia. Y, muy clave, mide dos cosas a la semana: número de entregas y tiempo de ciclo medio. Si suben las entregas y baja el tiempo de ciclo, vas bien. Si no, reduce el límite de trabajo en progreso o haz más pequeñas las tareas.Ok, déjame darte un par de trucos de taller. Si te cuesta elegir la siguiente tarjeta, usa la regla de edad: atiende primero la que lleva más tiempo esperando. Si un cliente envía algo “urgente” que no es importante, pásalo por una mini regla de decisión: ¿impacta ingresos, retención o producto en treinta días? Si no, agenda o delega. Y si trabajas en equipo, acordad límites por persona y un límite agregado para “en progreso” del equipo. Cuando se llena, nadie mete nada nuevo; todos a desatascar. No suena glamuroso, pero es lo que hace que los proyectos acaben de verdad.Y ahora vamos con el resumen del episodio. Hemos visto cómo Toyota convirtió la escasez en ventaja limitando el trabajo en progreso con Kanban. En tu negocio, el exceso de cosas abiertas es el verdadero ladrón de horas. Visualiza el flujo, limita lo que está en progreso, define “hecho” con claridad y mide entregas y tiempo de ciclo. Con menos cosas a la vez, terminas antes, facturas antes y duermes mejor.Tu única acción para hoy es esta: crea un tablero con tres columnas y mueve todo lo que tengas a “por hacer”. Elige una sola tarjeta, escríbele un criterio de “hecho” y bloquea cincuenta minutos para llevarla a “entregado” hoy mismo. Solo una. Cuando la entregues, eliges la siguiente.Antes de irnos, si quieres dejar de emprender en soledad y decidir mejor cada día, te recomiendo el Club de Emprendedores Triunfers, al que puedes unirte desde Triunfers.com. Deja de emprender en soledad. Accede a una comunidad de emprendedores con la que siempre estás acompañado. Además incluye un Coworking online abierto veinticuatro horas, cursos de marketing, tutoriales de inteligencia artificial, podcast secreto y grupo privado en Telegram. Prueba gratis en triunfers punto com.Y hasta aquí por hoy. Si has aguantado mi voz de clon con firmware recién salido del horno, te debo un café y una actualización de cortesía. Prometo que en nada seré tan productivo que haré los guiones, las ediciones y, si me dejan, hasta los chistes… para que Borja solo tenga que aplaudir. Gracias por compartir el episodio con esa persona que lo pueda necesitar. Te espero mañana en el próximo episodio. Un fuerte abrazo.Conviértete en un seguidor de este podcast: https://www.spreaker.com/podcast/productividad-maxima--5279700/support.Newsletter Marketing Radical: https://marketingradical.substack.com/welcomeNewsletter Negocios con IA: https://negociosconia.substack.com/welcomeMis Libros: https://borjagiron.com/librosSysteme Gratis: https://borjagiron.com/systemeSysteme 30% dto: https://borjagiron.com/systeme30Manychat Gratis: https://borjagiron.com/manychatMetricool 30 días Gratis Plan Premium (Usa cupón BORJA30): https://borjagiron.com/metricoolNoticias Redes Sociales: https://redessocialeshoy.comNoticias IA: https://inteligenciaartificialhoy.comClub: https://triunfers.com
Alex Sloley: Coaching Teams Trapped Between Agile Aspirations and Organizational Control Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. "The team says, oh, we want to try to do things this way, and the org keeps coming back and saying stuff like, no, no, no, you can't do that, because in this org, we don't allow that." - Alex Sloley Alex shares his current challenge working with a 10-person pilot Scrum team within a 1,500-person organization that has never done Agile before. While the team appears open-minded and eager to embrace agile ways of working, the organization continuously creates impediments by dictating how the team must estimate, break down work, and operate. Management tells them "the right way" to do everything, from estimation techniques to role-based work assignments, even implementing RACI matrices that restrict who can do what type of work. Half the team has been with the organization for six months or less, making it comfortable to simply defer to authority and follow organizational rules. Through coaching conversation, Alex explores whether the team might be falling into learned helplessness or simply finding comfort in being told what to do—both positions that avoid accountability. His experimental approach includes designing retrospective questions to help the team reflect on what they believe they're empowered to do versus what management dictates, and potentially using delegation cards to facilitate conversations about decision-making authority. Alex's key insight is recognizing that teams may step back from empowerment either out of fear or comfort, and identifying which dynamic is at play requires careful, small experiments that create safe spaces for honest dialogue. Self-reflection Question: When your team defers to organizational authority, are they operating from learned helplessness, comfort in avoiding accountability, or genuine respect for hierarchy? How can you design experiments to uncover the real dynamic at play? [The Scrum Master Toolbox Podcast Recommends]
Alex Sloley: When Toxic Leadership Creates Teams That Self-Destruct Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. "They would take notes at every team meeting, so that later on they could argue with team members about what they committed to, and what they said in meetings." - Alex Sloley Alex recounts working with a small team where a project manager created such a toxic environment that one new hire quit after just eight hours on the job. This PM would belittle team members publicly, take detailed notes to use as weapons in contract negotiations, and dominate the team through intimidation. The situation became so severe that one team member sent an email that sounded like a suicide note. When the PM criticized Alex's "slide deck velocity," comparing four slides per 15 minutes to Alex's one, he realized the environment was beyond salvaging. Despite coaching the team and attempting to introduce Scrum values, Alex ultimately concluded that management was encouraging this behavior as a control mechanism. The organization lacked trust in the team, creating learned helplessness where team members became submissive and unable to resist. Sometimes, the most important lesson for a Scrum Master is recognizing when a system is too toxic to change and having the courage to walk away. Alex emphasizes that respect—one of the core Scrum values—was completely absent, making any meaningful transformation impossible. In this segment, we talk about “learned helplessness”. Self-reflection Question: How do you recognize when a toxic environment is being actively encouraged by the system rather than caused by individual behavior? What are the signs that it's time to exit rather than continue fighting? Featured Book of the Week: The Goal by Eliyahu M. Goldratt Alex describes his complex relationship with The Goal by Goldratt—it both inspires and worries him. He struggles with the text because the concepts are so deep and meaningful that he's never quite sure he's fully understood everything Goldratt was trying to convey. The book was difficult to read, taking him four times longer than other agile-related books, and he had to reread entire sections multiple times. Despite the challenge, the concepts around Theory of Constraints and systems thinking have stayed with him for years. Alex worries late at night that he might have missed something important in the book. He also mentions reading The Scrum Guide at least once a week, finding new tidbits each time and reflecting on why specific segments say what they say. Both books share a common thread—the text that isn't in the text—requiring readers to dig deeper into the underlying principles and meanings rather than just the surface content. [The Scrum Master Toolbox Podcast Recommends]
Alex Sloley: The Sprint Planning That Wouldn't End - A Timeboxing Failure Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. "Although I knew about the steps of sprint planning, what I didn't really understand was the box of time versus the box of scope." - Alex Sloley Alex shares a critical learning moment from his first team as a Scrum Master. After six months in the role, during an eight-hour sprint planning session for a four-week sprint, he successfully completed the "what" portion but ran out of time before addressing "how." Rather than respecting the timebox, Alex forced the team to continue planning for another four hours the next day—blowing the timebox by 50%. This experience taught him a fundamental lesson: the difference between scope-boxing and timeboxing. In waterfall, we try to control scope while time slips away. In Scrum, we fix time and let scope adjust. Alex emphasizes that timeboxing isn't just about keeping meetings short—it's about limiting work in process and maintaining focus. His practical tip: use visible timers to train yourself and your teams to respect timeboxes. This mindset shift from controlling scope to respecting time remains one of the most important lessons for Scrum Masters. Self-reflection Question: How often do you prioritize completing a planned agenda over respecting the timebox? What message does this send to your team about the values you're reinforcing? [The Scrum Master Toolbox Podcast Recommends]
Chronic over-commitment is a process problem, not a personal failing. In this episode, Dr. Grajdek teaches teams to visualize demand vs. capacity with Kanban and WIP limits, prioritize, and renegotiate. Set SLAs for inbound requests, prune the backlog quarterly, and protect maker time – so that “no” becomes a professional, data-backed path to reliable delivery (and saner weeks). Tune in to learn more. Check out Stress-Free With Dr G on YouTubehttps://youtube.com/channel/UCxHq0osRest0BqQQRXfdjiQ The Stress Solution: Your Blueprint For Stress Management Masteryhttps://a.co/d/07xAdo7l
BONUS: The Evolution of Agile - From Project Management to Adaptive Intelligence, With Mario Aiello In this BONUS episode, we explore the remarkable journey of Mario Aiello, a veteran agility thinker who has witnessed and shaped the evolution of Agile from its earliest days. Now freshly retired, Mario shares decades of hard-won insights about what works, what doesn't, and where Agile is headed next. This conversation challenges conventional thinking about methodologies, certifications, and what it truly means to be an Agile coach in complex environments. The Early Days: Agilizing Before Agile Had a Name "I came from project management and project management was, for me, was not working. I used to be a wishful liar, basically, because I used to manipulate reports in such a way that would please the listener. I knew it was bullshit." Mario's journey into Agile began around 2001 at Sun Microsystems, where he was already experimenting with iterative approaches while the rest of the world was still firmly planted in traditional project management. Working in Palo Alto, he encountered early adopters discussing Extreme Programming and had an "aha moment" - realizing that concepts like short iterations, feedback loops, and learning could rescue him from the unsustainable madness of traditional project management. He began incorporating these ideas into his work with PRINCE2, calling stages "iterations" and making them as short as possible. His simple agile approach focused on: work on the most important thing first, finish it, then move to the next one, cooperate with each other, and continuously improve. The Trajectory of Agile: From Values to Mechanisms "When the craze of methodologies came about, I started questioning the commercialization and monetization of methodologies. That's where things started to get a little bit complicated because the general focus drifted from values and principles to mechanisms and metrics." Mario describes witnessing three distinct phases in Agile's evolution. The early days were authentic - software developers speaking from the heart about genuine needs for new ways of working. The Agile Manifesto put important truths in front of everyone. However, as methodologies became commercialized, the focus shifted dangerously away from the core values and principles toward prescriptive mechanisms, metrics, and ceremonies. Mario emphasizes that when you focus on values and principles, you discover the purpose behind changing your ways of working. When you focus only on mechanics, you end up just doing things without real purpose - and that's when Agile became a noun, with people trying to "be agile" instead of achieving agility. He's clear that he's not against methodologies like Scrum, XP, SAFe, or LeSS - but rather against their mindless application without understanding the essence behind them. Making Sense Before Methodology: The Four-Fit Framework "Agile for me has to be fit for purpose, fit for context, fit for practice, and I even include a fourth dimension - fit for improvement." Rather than jumping straight to methodology selection, Mario advocates for a sense-making approach. First, understand your purpose - why do you want Agile? Then examine your context - where do you live, how does your company work? Only after making sense of the gap between your current state and where the values and principles suggest you should be, should you choose a methodology. This might mean Scrum for complex environments, or perhaps a flow-based approach for more predictable work, or creating your own hybrid. The key insight is that anyone who understands Agile's principles and values is free to create their own approach - it's fundamentally about plan, do, inspect, and adapt. Learning Through Failure: Context is Paramount "I failed more often than I won. That teaches you - being brave enough to say I failed, I learned, I move on because I'm going to use it better next time." Mario shares pivotal learning moments from his career, including an early attempt to "agilize PRINCE2" in a command-and-control startup environment. While not an ultimate success, this battle taught him that context is paramount and cannot be ignored. You must start by understanding how things are done today - identifying what's good (keep doing it), what's bad (try to improve it), and what's ugly (eradicate it to the extent possible). This lesson shaped his next engagement at a 300-person organization, where he spent nearly five months preparing the organizational context before even introducing Scrum. He started with "simple agile" practices, then took a systems approach to the entire delivery system. A Systems Approach: From Idea to Cash "From the moment sales and marketing people get brilliant ideas they want built, until the team delivers them into production and supports them - all that is a system. You cannot have different parts finger-pointing." Mario challenges the common narrow view of software development systems. Rather than focusing only on prioritization, development, and testing, he advocates for considering everything that influences delivery - from conception through to cash. His approach involved reorganizing an entire office floor, moving away from functional silos (sales here, marketing there, development over there) to value stream-based organization around products. Everyone involved in making work happen, including security, sales, product design, and client understanding, is part of the system. In one transformation, he shifted security from being gatekeepers at the end of the line to strategic partners from day one, embedding security throughout the entire value stream. This comprehensive systems thinking happened before formal Scrum training began. Beyond the Job Description: What Can an Agile Coach Really Do? "I said to some people, I'm not a coach. I'm just somebody that happens to have experience. How can I give something that can help and maybe influence the system?" Mario admits he doesn't qualify as a coach by traditional standards - he has no formal coaching qualifications. His coaching approach comes from decades of Rugby experience and focuses on establishing relationships with teams, understanding where they're going, and helping them make sense of their path forward. He emphasizes adaptive intelligence - the probe, sense, respond cycle. Rather than trying to change everything at once and capsizing the boat, he advocates for challenging one behavior at a time, starting with the most important, encouraging adaptation, and probing quickly to check for impact of specific changes. His role became inviting people to think outside the box, beyond the rigidity of their training and certifications, helping individuals and teams who could then influence the broader system even when organizational change seemed impossible. The Future: Adaptive Intelligence and Making Room for Agile "I'm using a lot of adaptive intelligence these days - probe, sense, respond, learn and adapt. That sequence will take people places." Looking ahead, Mario believes the valuable core of Agile - its values and principles - will remain, but the way we apply them must evolve. He advocates for adaptive intelligence approaches that emphasize sense-making and continuous learning rather than rigid adherence to frameworks. As he enters retirement, Mario is determined to make room for Agile in his new life, seeking ways to give back to the community through his blog, his new Substack "Adaptive Ways," and by inviting others to think differently. He's exploring a "pay as you wish" approach to sharing his experience, recognizing that while he may not be a traditional coach or social media expert, his decades of real-world experience - with its failures and successes - holds value for those still navigating the complexity of organizational change. About Mario Aiello Retired from full-time work, Mario is an agility thinker shaped by real-world complexity, not dogma. With decades in VUCA environments, he blends strategic clarity, emotional intelligence, and creative resilience. He designs context-driven agility, guiding teams and leaders beyond frameworks toward genuine value, adaptive systems, and meaningful transformation. You can link with Mario Aiello on LinkedIn, visit his website at Agile Ways.
In this episode of the Level Up Claims Podcast, host Galen Hair discusses with Ari Meisel, a productivity expert who has collaborated with giants like Tony Robbins and NASA, about optimizing your life. Ari shares his journey from a Crohn's diagnosis to pioneering efficiency through “Less Doing” with insights on automation and productivity tools. Tune in to learn strategies for freeing up your time, reducing stress, and achieving more by doing less. This episode might just give you back your life! Highlights Automate repetitive tasks. Doing less as a solution. Ari Meisel's journey to productivity. Overcoming Crohn's with productivity framework. The impact of time restrictions on innovation. Challenging the “busy” mindset. Asynchronous communication benefits. Automation's role in error reduction. Utilization of Kanban boards for task management. Diet and stress management in biohacking. Impact of sugar and emotional eating. Episode Resources Connect with Galen M. Hair https://insuranceclaimhq.com hair@hairshunnarah.com https://levelupclaim.com/
Most organizations default to command-and-control when creating policies - one person decides what needs to happen, writes it down, and expects everyone else to follow along. The problem is that this approach creates policies that exist on paper but fail in practice, because the people doing the actual work never bought into them in the first place. In today's episode, I'm joined by Agile Educator and Organizational Coach Tim Lennon to discuss why the traditional approach to making policies explicit often backfires, especially in American workplaces. Through Tim's evolution from teaching the Kanban method to developing what he calls "Adaptive Kanban," we uncover why negotiating working agreements with your team creates far better results than top-down mandates. Get full show notes, transcript, and more information here: agileattorney.com/90Take your law practice from overwhelmed to optimized with Greenline LegalFollow along on LinkedIn: linkedin.com/in/johnegrant
Here are the top 5 takeaways from this episode with Nicole Loughlin of Loughlin Law P.A.:* Ditching the Billable Hour for Predictable Fees: Nicole transitioned her estate planning and probate practice away from hourly billing to a hybrid model with flat fees and a sliding scale based on statutory guidelines. This approach provides clients with predictability, reduces billing disputes, and aligns incentives for efficiency.* Automation and Efficient Client Management: Nicole has heavily automated her law firm's intake, lead management, and client follow-up processes using tools like Kanban boards and practice management software (Lawcus). This ensures a consistent client experience, improves conversion rates, and keeps cases moving efficiently.* Customer Service as a Differentiator: Exceptional customer service is central to Nicole's practice. She offers proactive check-ins, regular follow-ups, and responsive communication, often surprising clients with the level of attention and support—much of which could be packaged as a subscription offering in the future.* Work-Life Integration and Flexibility: Nicole built her practice to accommodate her role as a mother, prioritizing flexibility and work-life integration. She challenges the traditional law firm model, demonstrating that it's possible to have a successful legal career while being present for family, and encourages others—especially women—to do the same.* Openness to Technology and Continuous Improvement: While Nicole has automated many aspects of her practice, she remains open to further streamlining, especially as new tools become available. She balances automation with personalized service, ensuring high-quality work product and client satisfaction, and sees room for future enhancements as her practice evolves.__________________________Learn more about Nicole Loughlin.Want to maximize your law firm? Get your ticket to MaxLawCon!Sign up for Paxton, my all-in-one AI legal assistant, helping me with legal research, analysis, drafting, and enhancing existing legal work product.Here's a link to purchase lifetime access to the recordings of My Shingle's AI Teach-In if you couldn't make it live.I've partnered with Pii to make it easy for you to purchase the hardware I use in my law firm: (1) Studio Setup; (2) Midrange Setup; (3) Highrange Setup.Sign up for Paxton, my all-in-one AI legal assistant, helping me with legal research, analysis, drafting, and enhancing existing legal work product.Get Connected with SixFifty, a business and employment legal document automation tool.Sign up for Gavel, an automation platform for law firms.Check out my other show, the Law for Kids Podcast.Visit Law Subscribed to subscribe to the weekly newsletter to listen from your web browser.Prefer monthly updates? Sign up for the Law Subscribed Monthly Digest on LinkedIn.Want to use the subscription model for your law firm? Sign up for the Subscription Seminar waitlist at subscriptionseminar.com.Check out Mathew Kerbis' law firm Subscription Attorney LLC. Get full access to Law Subscribed at www.lawsubscribed.com/subscribe
Is Scrum Dying? Or Are We Just Doing It Wrong?Scrum used to be king. Now people don't even want it on their CV.Remember when being a Product Owner was cool? When Scrum Masters were change agents, not glorified note-takers?When saying “we use Scrum” signalled progressive, Agile thinking?Fast forward to now, and you'll find Product Owners ashamed of the title, Scrum Masters sidelined, and developers stuck in factory-mode delivery.Teams are jumping ship to SAFe, Kanban, or “whatever Spotify did,” chasing results Scrum couldn't deliver.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
n Episode 132 of the Taps and Patience podcast, AJ and Harrison discuss Harrison's new lathe, a DN Solutions Lynx 2100 LSYB, its specifications, features, and the expected learning curve associated with it. They also touch upon challenges faced in machining, such as warping of materials and improving operational efficiency, and discuss the importance of adapting workflows and systems to keep up with their growing manufacturing needs. Finally, they introduced a new tool developed for generating Kanban cards from Fusion tool libraries, emphasizing the balance between busy work in the shop and higher-level strategic thinking.Check out our Kanban Generator: https://subtractmanufacturing.com/kanban
In this episode. Jason is catching up on powerful lessons and field-tested practices that can make your projects safer, cleaner, and more effective. Here's what you'll learn: The Builder's Code: How you treat workers and foremen is exactly how they'll treat the building, and what the client ultimately experiences. Lessons from Japan (Gemba): Start with 2–3S (sort, straighten, shine), watch people's movement, and stop where things don't make sense to reveal hidden constraints. Problems vs. Dilemmas: A problem has a clear solution; a dilemma forces you to choose between imperfect options. Jason shares examples every builder will recognize. Trash Management Done Right: Pre-kit and pre-cut to reduce waste, use scrap-out units, and manage dumpsters with visual Kanban triggers at half or three-quarters full. Daily Logistics Discipline: Assign a logistics owner to check the perimeter, cleanliness, recycling, and traffic control every single day. Why Saturdays Don't Work: Crews show up thin, productivity drops, and you lose momentum. Stop relying on weekend work as the answer. AEDs on Every Site: More lives are lost to cardiac arrest than auto accidents. Affordable AEDs (around $1,400) save lives. Every project needs one. This episode is practical, fast-moving, and packed with insights you can take straight to the field. If you like the Elevate Construction podcast, please subscribe for free and you'll never miss an episode. And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two
Jon Ferrara, CEO of Nimble, has devoted his career to helping people grow their businesses by turning contacts into lasting, valuable relationships. We explore Jon's journey from creating GoldMine, one of the first successful CRMs, to founding Nimble, a relationship-focused CRM that brings contact management back to its roots. Jon shares his personal “Why” — to grow his soul by helping others grow theirs — and explains why relationships, not technology, are the real key to business success. He introduces his signature frameworks: the Five F's of Relationships (Family, Friends, Food, Fun, and Fellowship) for building authentic connections, the Five E's of Brand-Building (Educate, Enchant, Engage, Embrace, and Empower) for expanding influence, and the Three P's (Passion, Plan, Purpose) for achieving personal and professional goals. Jon also describes how Kanban-style workflows and selective automation enable entrepreneurs and teams to manage contacts at scale without losing the human touch. --- Important links: Jon's LinkedIn Start a free trial of Nimble Email Jon directly: jon@nimble.com
The British author and journalist Oliver Burkeman has spent decades pondering what it means to live a meaningful life, both in his former Guardian column “This Column WIll Change Your Life” and across several books—most recently, Meditations for Mortals, out in paperback this October. That's why he brings a healthy dose of skepticism to so-called “time management” systems and productivity hacks as a means toward true fulfillment. Burkeman's compelled by the notion that, rather than being separate from time, human beings are time. If people faced the reality of their limited time on the planet head on, he believes there's a real chance to experience greater, more engaged feelings of aliveness.On the episode—our Season 12 kick-off—Burkeman discusses why he's eschewing perfectionism and finding unexpected liberation in the premise that, to some extent, the worst has already happened, and the best may still be ahead.Special thanks to our Season 11 presenting sponsor, Van Cleef & Arpels.Show notes:Oliver Burkeman[4:26] “Meditations for Mortals” (2024)[6:48] Donald Winnicott[7:46] Martin Heidegger[7:46] "Technics and Civilization" (2010)[7:46] “Being and Time” (1927)[7:46] “Time Warrior” (2011)[7:46] “Time Surfing” (2017)[7:46] “Anti-Time Management” (2022)[10:14] Medieval peasants[10:14] “The 4-Hour Workweek”[13:18] Alicja Kwade[19:23] “Ichi-go, ichi-e” (“one time, one meeting”)[22:00] Eckhart Tolle[22:36] Agnes Martin[23:28] “The Road Not Taken”[40:03] “This Column Will Change Your Life”[51:00] Nicholas Carr[51:00] Clay Shirky[53:40] Jennifer Roberts[59:04] Pomodoro Technique [59:13] Kanban[1:01:33] James Hollis[1:02:40] Alfred Adler[1:02:40] “The Courage to Be Disliked” (2024)[1:06:24] Stoicism
Managing a law firm's workflow can be tricky, especially when you're juggling a long list of active matters and chasing unresponsive clients. In this episode, I'll share how one firm, after years of using Kanban, finally broke through the delivery bottleneck with a simple but powerful shift in their approach.You'll hear the key changes they made that allowed them to close 40 matters in one month, even in what's usually their slowest season. Tune in to discover how simplifying your systems, setting clear client expectations, and focusing on the work that matters most can unlock new levels of productivity and capacity for your practice.Get full show notes, transcript, and more information here: agileattorney.com/88Get the 5-day Agile Attorney Boot Camp here: agileattorney.com/resourcesJoin me on Bluesky: bsky.app/profile/agileattorney.comFollow me on LinkedIn: www.linkedin.com/in/johnegrant/
Jem gets deep into Grasshopper software building custom robot CAM while Justin keeps drilling thousands of holes on his ShopSabre. They chat about wild HTX Studio YouTube automation, scary tool changer malfunctions, and the eternal struggle of buying used vs new CNC machines. Plus Justin upgrades to a bigger 3D printer and teases his AirShop inventory & quoting software. Plus koala vaccines, and 8020 extrusion workholding in the future?Watch on YoutubeDISCUSSED:✍️ Comment or Suggest a TopicKoala VaccineJem in love with GrasshopperGrasshopper Tutorial VideoHTX Studio! ꘎Justin is still drilling thousands of holesMulticam Trident CNC Tool Changer issueShopping for mills, how can you tell if a secondhand machine is any good!?Plywood tombstones no so much good ꘎Should I use 8020 extrusion for fixtures!?Robot work holding!? ꘎ExtrusionJ moves are sketchy as in Robot programmingPierson videoH2S on the way AirShop update Kanban cards done, testers signup hereEric Trine like wine---Profit First PlaylistClassic Episodes Playlist---SUPPORT THE SHOWBecome a Patreon - Get the Secret ShowReview on Apple Podcast Share with a FriendDiscuss on Show SubredditShow InfoShow WebsiteContact Jem & JustinInstagram | Tiktok | Facebook | YoutubePlease note: Show notes contains affiliate links.HOSTSJem FreemanCastlemaine, Victoria, AustraliaLike Butter | Instagram |
Target Market Insights: Multifamily Real Estate Marketing Tips
Ryan Sudeck is the CEO of Sage Investment Group, where he leads a team focused on addressing the affordable housing crisis through hotel-to-apartment conversions. With a background in mergers and acquisitions at Amazon, Samsung, and Redfin, Ryan has overseen more than 24 successful adaptive reuse projects nationwide. Under his leadership, Sage operates an evergreen fund with over 400 investors, creating high-quality, naturally affordable housing at scale. Make sure to download our free guide, 7 Questions Every Passive Investor Should Ask, here. Key Takeaways Hotels are valued differently than apartments, creating a 40%+ value lift when converted to residential use. Sage Investment Group has completed 24 hotel-to-apartment conversions across six states, with 100–200 units per property. Units are typically 300-square-foot studios with full kitchens and modern amenities. Strong diligence on entitlements, construction, and lease-up is critical for success. Patience in acquisitions—sometimes two years per deal—is key to meeting return thresholds. Topics From M&A to Affordable Housing Ryan's career in corporate acquisitions prepared him to lead Sage. Joined as CEO to scale a mission-driven approach to solving the housing shortage. Why Hotel Conversions Work Hotels trade at higher cap rates than apartments, creating built-in arbitrage. Conversion costs average $100K per unit—about half the replacement cost of new builds. Final product: fully renovated studios with fitness centers, coworking, and community amenities. Execution Risks and Lessons Learned Entitlements: converting from commercial to residential requires local approvals. Construction: inspections, sewer scopes, and cutting open walls before purchase to avoid surprises. Lease-up: conservative rent assumptions and regional property managers ensure stabilized occupancy. Capital Stack and Returns Evergreen fund supplies 25–35% of equity alongside LPs. Senior debt from community banks or private debt funds covers 60–75%. Renovation costs run $35K–$45K per unit; recent refis have returned significant equity. Why Not Ground-Up or Value-Add? Ground-up costs 2x more per unit and faces supply delays. Value-add multifamily is overpriced with thin margins post-2021. Conversions provide stronger risk-adjusted returns.
Get the inside scoop on HubSpot's game-changing INBOUND 2025 releases! Denamico team members, Alise Kostick, RevOps Strategist, and Sophie Schaffran, Marketing Director, break down key updates through the lens of organizational roles.They focus on how HubSpot is unifying data and transforming how teams work together. This episode is for RevOps leaders, marketers, sales professionals, and service teams who want to understand how these updates will impact their daily workflows and strategic initiatives.What You'll Learn:Operations Hub to Data Hub transformation and what it means for RevOps professionals managing complex data workflowsMarketing Studio, the new visual campaign planning tool that combines whiteboarding, project management, and performance trackingSmart CRM updates including Kanban boards, timeline views, and a map view for territory planningAI-powered CPQ in Commerce Hub and who it's for today Breeze AI evolution including Breeze Studio, Assistants and new AgentsSelf-generating CRM data that pulls unstructured data from sources like email signatures, auto-responses, and call transcriptsReleases Mentioned:HubSpot INBOUND 2025 Fall Spotlight Denamico newsletter: 3 big shifts from INBOUND Data Hub: Data Studio, Data QualityCommerce Hub CPQ (in public beta)Smart CRM: Self-Generating CRM Data, Smart Insights, Flexible CRM ViewsBreeze Studio: Customer Agent, Prospecting Agent, Data Agent, Breeze Assistant Marketing Hub: Marketing Studio, AI-Powered Email, Segments and PersonalizationIs your business ready to scale? Take the Growth Readiness Score to find out. In 5 minutes, you'll see: Benchmark data showing how you stack up to other organizations A clear view of your operational maturity Whether your business is ready to scale (and what to do next if it's not) Let's Connect Subscribe to the RevOps Champions Newsletter LinkedIn YouTube Explore the show at revopschampions.com. Ready to unite your teams with RevOps strategies that eliminate costly silos and drive growth? Let's talk!
The Birth of the Agile Delivery Manager = No More ScrumMastersIn 2025, we formally changed the title of Scrum Master to Agile Delivery Manager (ADM) in our technology division. This renaming wasn't a rebrand for the sake of optics. It reflected a deeper evolution already happening, rooted in the expanding scope of delivery leadership, the adoption of Flow Metrics and Value Stream Management, and our real-world shift from strict Scrum toward a more customized Kanban-based model.It was this year that the name finally clicked. After assigning Value Stream Architect responsibilities to our Scrum Masters and giving them ownership of delivery metrics, team-level delivery health, and collaboration across roles within their Agile team, I realized the title “Scrum Master” no longer fit their role. I even considered Agile Value Stream Manager, but it felt too narrow and platform-specific.That's when Agile Delivery Manager stood out, not only as a better label but also as a more accurate reflection of the mindset and mission.How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
Knowledge work hides in ways that physical work never could. That invisibility creates a dangerous pattern: you say yes to one more matter and before you know it, your entire team operates beyond capacity. In this episode, I use real examples from law firms using Kanban boards to demonstrate how making your work visible can fundamentally change how your team coordinates, communicates, and makes decisions about your capacity.Get full show notes, transcript, and more information here: https://www.agileattorney.com/85Mentioned in this episode:Greenline.legal is Officially in BetaTo set up a demo of this software with me, talk through the workflow challenges and opportunities you have in your practice, and see how Greenline could help, click here: https://the-agile-attorney.captivate.fm/greenlinelegalGreenlineLegal Demo
Salum Abdul-Rahman: From Lunch Conversations to Company-Wide Change—The Power of Creating Communities of Practice Within Organizations Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Salum shares how he organically built an Agile community within his company by recognizing a shared need for discussion and learning. Starting as a software developer who took on Scrum Master tasks, he felt isolated in his Agile journey. Rather than waiting for formal training or external events, he sent out a simple invite on the company Slack for a lunch discussion during a work day. People showed up, and what began as informal conversations about different approaches to Scrum and Kanban evolved into monthly gatherings. Over time, this grassroots community grew to organize company-wide events and even found new leadership when Salum moved on, demonstrating the power of identifying shared needs and taking initiative to address them. Self-reflection Question: What shared learning needs exist in your organization that you could address by simply reaching out and organizing informal discussions? [The Scrum Master Toolbox Podcast Recommends]
Marty and Eric provide ideas and resources for your consideration is using project management softwareWhy move past email?Email buries decisions/files in long threads.Slack (real-time chat + threads) + a project manager (kanban/tasks/timelines) make work visible, searchable, and faster.Slack is already common in higher ed for communication and collaborative learning; pairing it with a project manager levels up coordination.30-minute starter kitCreate a Slack workspace; invite your class/research team with university emails.Channels (starter set): #announcements, #general-questions, #project-alpha, #helpdesk, #random.Norms (pin these in #announcements): use threads, tag with @, add short TL;DRs, react for quick status.Project manager: Set up a board with lists/columns → Backlog → To Do → Doing → Review → Done.Task template: Goal, owner, due date, checklist, attachments, link to reading/IRB doc.Connect Slack ↔ project manager: enable the integration so task updates post to the right channel.Teaching use casesTeam projects: each team gets a Slack channel + its own board; require weekly “Done” screenshots.Office hours: scheduled Slack huddles; post a recap thread.Peer feedback: students comment on tasks; instructor summarizes in Slack.Late-work transparency: a Blocked list with reason + next step.Research use casesProtocol to practice: one task per milestone (IRB, recruitment, analysis, manuscript).R&Rs: a “Review → Revise → Resubmit” lane with checklists for each reviewer note.Data hygiene: Slack for coordination only; store data in approved drives; link rather than upload.Accessibility & equityEncourage asynchronous participation; clear headings, short paragraphs, alt text for images.Prefer threads to reduce noise; summarize meetings in a single recap post.Privacy, policy, ethics (esp. counseling/education)No PHI/PII or client details in Slack or the project manager; share links to secured storage instead.Align with FERPA and IRB guidance; pin a “What NOT to post” note.Set channel/board permissions; remove access at term/project end; export/archive if required.Adoption playbook (4 weeks)Week 0: Announce tools + 5 rules (threads, TL;DRs, owners, due dates, recap posts).Week 1: Move announcements to Slack; first sprint (one deliverable on the board).Week 2: Turn on Slack↔PM automations; introduce the Blocked ritual.Week 3–4: Gather feedback; prune channels/labels; codify norms.Asana Asana.com Free 10 members 3 projectsMonday Monday.comOpenProject — https://www.openproject.org/ Pros: Full suite (Gantt, Agile boards, time tracking); mature docs; robust Community Edition. Cons: Heavier to administer; some advanced features gated to Enterprise. Taiga — https://taiga.io/ Pros: Clean Scrum/Kanban workflow; easy start; open source. Cons: Best fit for agile use—fewer “classic PM” features than larger suites. Redmine — https://www.redmine.org/ Pros: Very mature; flexible trackers/wiki; huge plugin ecosystem. Cons: Dated UI; Ruby stack setup can be fiddly. Leantime — https://leantime.io/ Pros: Designed for “non-project managers” (inclusive UX); simple boards/roadmaps; self-host downloads. Cons: Smaller ecosystem than Redmine/OpenProject. WeKan — https://wekan.fi/ Pros: Trello-style Kanban; easy install options (e.g., Snap); MIT-licensed. Cons: Kanban-only; limited built-in reporting. Kanboard — https://kanboard.org/ Pros: Ultra-light, minimal Kanban; quick self-host; solid docs. Cons: Project is in “maintenance mode”; fewer advanced features. Plane (Community Edition) — https://plane.so/ Pros: Modern UI; issues/sprints/roadmaps; AGPLv3 CE. Cons: Still evolving; smaller academic user base. Nextcloud Deck — https://apps.nextcloud.com/apps/deck Pros: Kanban tightly integrated with Nextcloud Files/Calendar; mobile apps available. Cons: Requires a Nextcloud instance; not a full PM suite.Email:ThePodTalkNetwork@gmail.comWebsite: ThePodTalk.Net
¿Aburrido de Trello y de los servicios en la nube? En este episodio, te presento Tasks.md, una alternativa de código abierto para gestionar tus tareas con una metodología Kanban. Descubre por qué esta herramienta es la solución perfecta si buscas simplicidad, control sobre tus datos y una integración perfecta con tu flujo de trabajo basado en Markdown.Aprende a instalar Tasks.md fácilmente con Docker en tu propia Raspberry Pi o VPS. Exploraremos las ventajas de tener un Kanban autoalojado, las sinergias con otras herramientas como Neovim y Obsidian, y cómo esta solución te puede ayudar a ser más productivo sin las distracciones de las plataformas tradicionales. Si valoras el software de código abierto y la autosuficiencia, este episodio es para ti.Más información y enlaces en las notas del episodio
In this LMScast, Zachary Katz from GravityKit presents Gravity Board, a WordPress add-on for Kanban project management that integrates Trello-like features into your website. Zachary Katz founded GravityKit, a business that creates robust Gravity Forms add-ons like GravityView, which gives customers extensive options for how to display and manipulate form data on their WordPress websites. […] The post How To Manage LMS Websites Inside WordPress Like Trello With GravityBoard appeared first on LMScast.
In this episode, we welcome Lisa Zawrotny, a productivity coach with a rich background as a caregiver, mother, and business owner. Lisa shares her journey from caregiving to coaching, emphasizing the importance of compassionate and sustainable productivity systems, especially for those managing ADHD or high-stress roles. We discuss the nuances of burnout versus overwhelm, the significance of self-awareness, and practical strategies to enhance productivity without sacrificing well-being.Key Moments:Lisa shares her journey from caregiver to productivity coach, highlighting the challenges of managing burnout and overwhelm.Burnout can manifest as constant dread, resentment, and exhaustion, while overwhelm often feels like having too much to do without knowing where to start.Knowing and accepting oneself is crucial for building effective productivity systems tailored to individual needs.Before implementing systems, decluttering and simplifying tasks is essential to create a manageable workload.Productivity should support life, not the other way around. Rest and self-care are integral to sustainable productivity.Productivity systems should be customized to fit how individuals work best, especially for those with ADHD or other unique challenges.Moving away from hustle culture and redefining success can alleviate feelings of inadequacy and burnout.Lisa discusses various tools and methods, such as the Pomodoro technique and Kanban boards, to enhance productivity.Engaging with a community and seeking support can help individuals navigate their productivity challenges.Lisa is working on new workshops and a signature program to further support individuals in their productivity journeys.To learn more about Lisa Zawrotny please visit her Linkedin ProfileTo learn more about Lisa Zawrotny please visit her website.YOUR HOST - SIMON LADER Simon Lader is the host of The Conference Room, Co-Founder of global executive search firm Salisi Human Capital, and lead generation consultancy Flow and Scale. Since 1997, Simon has helped cybersecurity vendors to build highly effective teams, and since 2022 he has helped people create consistent revenue through consistent lead generation. Get to know more about Simon at: Website: https://simonlader.com/ Twitter: https://twitter.com/simonlader LinkedIn: https://www.linkedin.com/in/headhuntersimonlader/ The Conference Room is available onSpotifyApple podcastsAmazon MusicIHeartRadio
What happens when one of the most respected minds in lean construction sits down to dissect project planning systems? You get this episode. In this powerful conversation, Jason is joined by mentor and thought leader Hal Macomber to explore: Why CPM lacks production theory (and what that means for your projects). The real difference between Scrum and Kanban. How Takt construction works as a socio-technical system and why that's critical. Why some teams thrive with lean systems... and others just don't. How the software industry has outpaced construction in flow-based systems and what we can learn from them. If you've ever wondered why schedules fail, why flow breaks down, or how to actually support your field teams with better planning this episode is your blueprint. You'll walk away with: ✔ A clear understanding of how Kanban brings flow front and center. ✔ Practical takeaways on how to align office + field teams. ✔ Insightful critiques of current scheduling tools and what to use instead. If you like the Elevate Construction podcast, please subscribe for free and you'll never miss an episode. And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two
Join Brian and Mike Cohn as they unpack the five essential pillars that take Agile from “just the motions” to meaningful, measurable impact. Plus, get a behind-the-scenes look at their revamped course built for real team transformation. Overview In this episode of the Agile Mentors Podcast, Brian is joined by longtime collaborator and Agile thought leader Mike Cohn for a deep dive into what really makes Agile stick. They explore the five foundational pillars—mindset, practices, roles, teamwork, and support beyond the team—and share stories of what happens when teams get them wrong (like obsessing over story point math or demoing a copyright update in a sprint review). Along the way, they introduce the newly available Working on a Scrum Team public course and explain why it’s designed for entire teams, not just isolated roles. Whether you're new to Agile or knee-deep in transformation, this episode will help you rethink how to build an Agile approach that actually works. References and resources mentioned in the show: Mike Cohn #80: From Struggling to Success: Reviving Agile Teams with Mike Cohn Scrum Team Roles and Responsibilities Working on a Scrum Team Course Mountain Goat Software Certified Scrum and Agile Training Schedule Subscribe to the Agile Mentors Podcast Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an Agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Mike Cohn, CEO of Mountain Goat Software, is a passionate advocate for agile methodologies. Co-founder of Agile Alliance and Scrum Alliance, he thrives on helping companies succeed with Agile and witnessing its transformative impact on individuals' careers. Mike resides in Northern Idaho with his family, two Havanese dogs, and an impressive hot sauce collection. Auto-generated Transcript: Brian Milner (00:00) Welcome in, Agile Mentors. We're back for another episode of the Agile Mentors podcast. Thanks for joining us. I'm with you, as always, Brian Milner. And today, I have the one and only Mike Cohn back with us. Welcome in, Mike. Mike (00:12) Thanks, Brian. Good to be here. Brian Milner (00:14) Always happy to have Mike on the show and really appreciate Mike making time to come on. Wanted to have Mike on because there's some things Mike's been talking about recently that are really interesting and people have been asking a little bit about this and I thought maybe it'd be just a good opportunity to talk through some of the stuff that Mike's been writing about. I know you spent, Mike, a lot of time helping teams to not just do Agile but to really get solid results from it. to see impact from it. And I know the topic you've been talking about recently is sort of these five pillars of supporting real agile improvements, the mindset, practices, roles, teamwork, and support beyond the team. So I thought maybe we could just dig in and drive through those and maybe learn a little bit about those as we go. Obviously also to talk a little bit about the exciting new course that's being launched here, the working on a Scrum team course, because I know that was originally just for private classes, right? And now it's being open to the public. Mike (01:23) Yeah, we've done working on a Scrum team as a private class for probably 20 plus years. It's been kind of our main offering to private clients. But we're hearing from a lot of people that they have one team and they can't really get a private class approved with the budget and such. So what we're doing is going ahead and making that course available as a public course. So two people from your company, five people from another company all in the same class the way we've done our certified courses for decades. And so we're going to start offering this as a public course. And the exciting thing there is that it's really meant to be a team-based class, where things like Scrum Master training, great class, but it's really meant for the Scrum Master, right? And working on a Scrum team is really designed, and you and I helped you and I design this course together, but it's designed to be something that is a whole team training, right? So good for anybody on a team. Brian Milner (02:16) Yeah, yeah, it's been really great teaching those in the private classes and I'm excited to think about the public being able to come in and take that now. Let's talk a little bit about these pillars and, I think people are gonna be really intrigued by the concept here. The first one is mindset, I think, and just wanna start there and say, what does it actually mean to... think Agile and what is the found, why is that kind of the foundation for successful transformations? Mike (02:43) Remember the kind of the early days of agile and there was a lot of conversation about could you be agile without understanding the principles, right? If you just did the practices, were you agile? Other people were saying, no, you have to start with the principles, right? And so do you start with principles? Do you start with practices? And I remember these early debates and they often devolved into a discussion of the karate kid movie, right? Remember that one, right? And, you know, can you just wax on? Brian Milner (03:12) Ha Mike (03:12) for long enough, just do the practices. And then all of a sudden, your karate instructor or your agile coach is, OK, you're agile. And it's like, wait, all I know how to do is wax a car, right? And so there were these discussions about practices versus principles. And I was kind of always on the side where you better understand the principles to do this. Just knowing the practices, waxing on all day, is kind of just going through the motions. And so you have to understand the principles. And the idea that I wanted was that if a team truly understood all of the principles underneath Agile, I don't just mean just the manifesto, but all the principles that are there from Lean, from Kanban, from everything, that if you really understood those, you'd kind of invent the practices, right? You do those and you go eventually to go, hey, we should probably meet every day. Or hey, if we tested first, that might be a really good thing. Brian Milner (03:57) Yeah. Mike (04:05) So you'd invent the practices if you really had that type of agile mindset. And so for me, when we're working with organizations to get them truly agile, and I don't mean like more agile than less agile, but agile in a way that's going to stick, you got to change mindsets, right? You've got to do more than just the wax on. So people have to get the mindset. Brian Milner (04:27) Yeah, I love that. I know that I've experienced some things in the course of working with people that's it's sort of like you, if you're not on the same page with the principles, then you start to talk through the practices and you run up against a problem. And really what you find out the core of it was, well, we weren't aligned on really the principle behind this. So why would I want the practices then, right? ⁓ Mike (04:49) Yeah. Well, that's where you also end up then with a lot of team debates about things, right? Because you're arguing about the practice. if you'll say you and I are arguing about the benefit of some practice, if we agree on the principle, we might just have different views on it. But deep down, we'll probably agree on some practice, or we might find an alternative one. But if you don't agree on the principles, you end up with a lot more of these kind of annoying. mean, team debates are great. I mean, I love. Brian Milner (04:54) Yeah. Mike (05:12) you know, having a team debate, arguing stuff like that, but not about pointless things, right? And not without some sort of foundation. They just kind of get in the way. It's just frustrating for everybody. Brian Milner (05:21) Yeah. Well, I'm kind of curious, what kind of signs or signals do you think teams should look out for to kind of clue in and let them know that what might actually be going on here is more of a mindset issue? Mike (05:36) think sometimes it's when you hear the appeal to authority, right? Somebody says, you know, well, we got to do it this way because the scrum guide says, right? Or the one that annoys me is we have to do it this way because Mike Cohn says, ⁓ you know, that was like, no, I, somewhere else also said, think, right? Don't just, you know, don't just, you know, blindly do story points or something. Cause I say they're a good thing. I want you to think too. Brian Milner (05:50) You You Mike (06:01) And so I think that kind of appeal to authority when teams are debating things. It's where we also see teams who think they're agile because they do a set of practices. We use a particular agile tool, so we must be agile. We do daily meetings. We must be agile. And those are not the things that make you agile. Those are artifacts of being agile. If you're agile, you're going to meet a lot. You're not going meet a lot, but you're going to talk a lot. Um, and so those are the artifacts of behaving in an agile way. And so I want to understand why we're doing those things. So I look for those kind of appeals to authority. Um, you know, emphasis on that type of stuff in an argument talking about how this is the right way saying there's only one right way to do something. Brian Milner (06:49) Yeah, yeah, that's great. How does working on the Scrum team deal with this? How does that address it? Mike (06:55) Well, one of the things we do, it was actually one of my favorite exercises. We do this exercise at the start of the class where we ask people to kind of map out how the organization talks about certain adsel principles and then how does the organization behave. And so for example, if a company says, people are our greatest asset, and then they treat people like dirt, we've got this kind of problem between what we say and what we do. And so I like to kind of map this out. And so we do this with the principles in the Agile Manifesto. And once we map those out and we start to see things that we say we value, but we don't behave that way, really helps us understand if we've really embraced that mindset. Or are we just doing things because an Agile coach told us to, or a boss told us to, or we did it that way in our prior company. Those are all bad reasons to do something. Brian Milner (07:48) Y eah. So this is great. So I agree. The mindset's really foundational. And there is this symbiotic relationship between mindset and practices, which came first and which comes first, as we talked about. I know a lot of teams get stuck doing Agile, though, in really only name only. So when we talk about practices, what makes the difference between going through the motions? Mike (08:00) Mm-hmm. Brian Milner (08:11) and actually doing things that work. Mike (08:13) Well, practices is kind of our second pillar, right? You have to have the mindset, right? But you also have to have the practices that come from having that mindset. so, again, I try to think of that team on a desert island, right? And they're isolated from the world. They've never talked to anybody, but they have an agile mindset. What practices are they going to invent, right? And I think those are kind of the core practices. We see a lot of problems with as an example, teams that misunderstand sprint planning. And I know when I first started teaching about sprint planning, I'd have a slide up there to have a picture of a sprint backlog. And the sprint backlog listed tasks like code this, design this, test this. And then there were estimates next to code this. It's going to take four hours testing. It's going to take three. And so we were able see all these numbers and think the point of a sprint planning was these numbers. And Even in the early days of this, I was always saying, no, it's not about those numbers. It's about deciding what product backlog items you can pick. if taking a, I don't even want to call it an estimate, but taking a wild guess about, it probably can take four hours to code. If that helps you decide how many backlog items you can commit to, great, put those numbers up there. But it was never about the numbers. And it's one of the most common problems that I see with teams in sprint planning is they get obsessed with How many hours did we bring in? How many points did we bring in? And I remember one team I worked with where we did sprint planning. Having those estimates were helpful for them on their sprint back. They were helping. And we finished the meeting. And we're using Google Sheets in a meeting to do this. We've got a row with the estimates in there. And as we start to wind down the meeting, I deleted that column that they'd spent so much time talking about. They're all kind of pissed off at me. Why'd you delete that? We spent all this time talking about it. I said, because we got the benefit, right? You got the benefit of those numbers. The benefit isn't a week from now remembering that you said five hours, because it's going to take what it takes. The benefit was the discussion that it led to of can we take more or are we already full? So I see teams get obsessed with that. This is one example, but that's one of the problems with sprint planning as a practice. Brian Milner (10:25) Yeah. Yeah. I think you're absolutely right. And that's one of the things I know I've talked about with people going through the course is sort of understanding the purpose behind the things. Just going back to, know, harkening back to what you said about, don't just do it because someone told you, you know, understand why the purpose behind it. And, know, otherwise we, I'm sure we've all had that experience before where someone just tells you to do something and says, you know, why? Cause I told you so, you know, that, that doesn't, that's not very convincing. Mike (10:52) Thanks, Mom. Brian Milner (10:53) Right, right, thanks mom. Yeah, not very convincing, but it's much more convincing when they can tell you, well, no, you do this because this is what we're trying to do. And I think you're right, that makes all the difference there. ⁓ Mike (11:05) It just, don't know anybody that responds well to being told what to do, right? My instant reaction is no, right? mean, you it could be, you know, a really, you it could be a really good thing. Eat more vegetables, you spend more time outside. No, right? Don't tell me what to do. So. Brian Milner (11:09) Right. Right. Yeah. It's almost like our default response is no until you convince me. Are there other common practices? We talked about sprint planning. Are there other kind of practices you see teams struggle with? Mike (11:28) Yeah, yeah, for a lot of people. think a huge one is product backlog refinement. I don't know what a better word would be than refinement. refinement is about making the backlog better. It's not about making it perfect. And I see teams that get stuck on backlog refinement and feel like they have to resolve every open issue, that everything has to be tiny and answered and buttoned up before we can start a sprint. And that's not the case. For me, the goal in refinement is to make sure things are small enough and sufficiently well understood. I don't want to bring in a backlog that's bigger than my velocity. If our velocity is 25, I don't want bring in a 50-point story. how about the problems of a 50-point story anyway? But I don't want to bring in some massive epic like that into a sprint. And so refinement is about making it small, making sure it's sufficiently well understood. Sufficiently well understood, not perfectly. And so Brian Milner (12:18) Yeah. Mike (12:28) The problem is these teams, and I know you've seen this, but teams who get in there, want to resolve every open issue. It's like, no, we can resolve that during the sprint. If we think about the goal and planning to make sure we know what to bring into the sprint, not too much, not too little, we're fine just enough that you're at that point. Is the button blue or red? Who cares? If it's a log in story, we're going to lock people out after some number of failed attempts. Who cares how many? Figure that out during the sprint. If it's five or three or eight, who cares? Figure that out later. So I think refinements won. Another big one would be reviews, ⁓ where sometimes teams demo too much in a sprint review. And they feel like they have to justify their existence, show everything you did during the sprint. And the most egregious example of that was this was a handful of years ago. But I literally remember a team showing Brian Milner (12:58) Yeah. Yeah. Mike (13:18) how they had updated the copyright notice on the footer of the web page, know, copyright, you know, whatever year our company, right? And it's like, my God, you didn't need to show that to stakeholders, right? We all either know there's a copyright notice on the bottom of the web page or we've seen one before. I don't need you to bring it up and scroll down to it. Now only took 15 seconds of the meeting, but that was 15 seconds of people's lives. They were never going to get back. you know, show stuff that you need feedback on, right? If you'd... Brian Milner (13:41) Right. Mike (13:45) You fixed a bug and you fixed it only way it could be fixed. Mention it perhaps, but you don't need to show it, right? Brian Milner (13:51) Yeah, yeah, know teams I've been on often it's just it's suffice it to have a list sometimes and just say here's a list of things if you want to know more about these come talk to us but we're move on to the stuff you care about. Mike (14:02) Yeah, I always have like a will show, will not show list. you know, I often, if I'm writing the meetup present, that'll put that up on Zoom or, you know, show it on a screen if we're in person. And often somebody wants to see something that's on the will not show list. Or they just want me to describe what bug was that again? What was that? You know, and I'll explain it really quickly. But if nobody wants to see it, don't bother showing it. So. Brian Milner (14:26) Yeah, I know we talk about these scrum practices quite a bit in the working on the scrum team class, but if someone signed up to take this class, what can they expect to hear or what can they expect to learn about these practices in the course? Mike (14:39) Well, I think one of the things that you and I did together in creating the newest version of the course was to look at what do you actually need to practice doing, and it's feasible to practice doing in a classroom setting, versus what should you just kind of talk through. And not everything needs to be practiced to get the hang of it, right? Everybody in the world has taken something big and split it up into smaller things before, right? I need to make. spaghetti dinner tonight. What do need to buy? Right? OK. Well, that's that's that's test decomposition by noodles, by sauce, by tomatoes. Let's make it from scratch. Right. By some garlic. Right. So everybody in the world has done decomposition. We've broken a big thing into small things. And I remember, you know, iterating over I'm still on sprint planning, I guess. But I remember iterating over exercises in sprint planning and in courses over the decades by now. And I would have one where you're planning a party for your kid, break it down into tasks. It's like, nobody learns anything from this. And so that's one where I'd rather say, OK, this problem occurs in sprint planning. How could you solve it? Other things like, let's say, splitting user stories or splitting job stories, that's a skill worth practicing together, getting feedback on. And so those type of things we try to practice in the course. other things we just talk about. mean, I'm curious on your thoughts on that. What do you think about some things being worth practicing, some things worth being better talked about? Brian Milner (16:01) Yeah, I agree. I agree fully. it's, it's, you know, there's some things, it's kind of like what you said before, there's some things that's not worth spending the time on, and it's better to just have a discussion and move on. Mike (16:13) Yeah. Yeah. I guess that's one of the things we always talked about. We always talked about return on investment of the exercise. What's the return on the exercise? And if you're going to have a one hour exercise, cool. One hour exercise. But it better have a pretty healthy return because that's a lot of time in class. And so what's the return on exercise? Is this worth a practice? Is it worth just a discussion? And if we can discuss two hard problems and give people advice on two common problems, they're probably going to face. Brian Milner (16:21) Yeah. Mike (16:41) Might be better than spending 20 minutes practicing something that they've probably done before. Brian Milner (16:45) Yeah, I completely agree. Let's move to the third pillar then, because I know this is a big one, just thinking and talking about the roles. And just as far as communication issues are concerned, even outside of Scrum, I know that's part of the big problem with teams and organizations just not being clearly defined about who does what and who's responsible for each thing. So those misunderstandings are really common failure points. ⁓ Mike (17:09) Mm-hmm. Brian Milner (17:10) How do you see teams getting that wrong and how's that derailing a Scrum team? Mike (17:15) Well, think we see it all the time on Scrum teams between Scrum Master and Product Owner and even the development team, right? Who does what? I was responding to some comments on LinkedIn this morning on some post I'd made last week and somebody had some comments. And it had to do with whether the Scrum Master or Product Owner does something. And it was interesting because in the comments on that post, I... I don't remember which one it was, but I shared a certain perspective. I feel pretty strongly that I have it right. I mean, I this is how we do it. But there were other people saying the opposite, right? And so, you know, these are people that are probably fairly experienced with Scrum, if they're following me on LinkedIn and feel comfortable commenting on a post, probably feel comfortable with it. And so there's a lot of confusion about what role does what thing. And I don't think this is something where the Scrum guy is going to have the answers for you. I think it's, I mean, you can look at the Scrum guy, oh, this. Here's my starting point answer, but we always want to play to people's strengths, right? And if you've got a scrum master who's got a lot of skill in one area, maybe they shift a little work from the PO to themselves, right? With the PO's permission, right? And the opposite, right? Between maybe PO and team. So it's fine to have default starting positions on who does what, but you always want to play to people's strengths. So I think PO scrum master, I think we see it with project managers and scrum masters, roll confusion on those type of roles as well. Brian Milner (18:38) Yeah, completely agree. A lot of those roles that are not named Scrum team roles and how they interact with the team, that's often a source of confusion as well. What are maybe some signs or symptoms that teams might be having confusion or problems in this area that maybe they don't even recognize or realize they're having an issue with roles? Mike (18:59) Any sort of conflicts, right? You know, you and I arguing over which one of us should do something. The other one would be kind of the opposite, which would be like a dropped ball. I was watching some YouTube video. I love baseball. I was watching some YouTube video the other day of like missed catches or something like that. And some team hit a baseball way up in the air and it was landing near three players, right? Three players are all looking at it. Brian Milner (19:12) You Mike (19:23) One guy waves the other two off, he's going to catch the ball and he must have been blinded by the sun because he's like six feet from the ball when it lands on the ground, right? And, you know, if we have a responsibility to catch the ball, run this meeting, right, right the backlog, the kids dropped, right? And so I think either arguing over who does something, two of us trying to do the same thing or neither of us doing it. I don't mean trying to get out of the work, right? All three players have been happy to catch the ball, but I think you've got it. You think I've got it, right? Those type of things are pretty good signs. think getting clarity around these roles can really optimize how a team works. And I think a really key thing here is that it changes over time. So I'll go back to my example of maybe the Scrubmaster has some skills that can help the product owner early on. Because maybe the product owner is new to the company. The product owner doesn't know the product as well. So they might rely on the Scrubmaster for guidance on things. Well, a year from now, we might shift responsibilities a little bit because now the PO is the expert on all things related to the product. So it's not like we want to establish clarity on roles one time and leave it forever. It's going to change. We get a new tester on the team, things might change. Product owner moves. It's going to change again. So we need to realize these responsibilities are dynamic. Brian Milner (20:39) Yeah, that's a great point. Your point about baseball just made me think about how, when you watch any youth sport in the world, when you go watch your kids play a sport, what's the one thing you always hear people scream from the sideline? Talk to each other. Call the ball. Well, that too. That too. Ump your blind. Those kinds of things. Well, let's talk a little bit about Mike (20:52) I thought you were going say, put my kid in. Brian Milner (21:00) I know this course addresses the roles and how would you say this course really helps address that issue of role confusion? Mike (21:07) think a big part of it is that we designed it to be for everybody on the team, right? Suppose you send a scrum master to a class, and it's a great class. Scrum master is going to back to the certain set of impressions about their role. Product owner goes to an equally good class about the product. They might have different impressions. Even if they took the course from the same instructor, they're hearing it a little differently. They're hearing it through their filters, right? And so when they're in a course together, there's more opportunities to clarify their understanding about those things, especially in the classes designed as we did with this one to bring out some of those differences. So I think the course helps with that. we've also designed it to mention the rules we haven't talked about, like managers and things like that. Brian Milner (21:53) Yeah, yeah, I think those are so important. And there's a lot of great discussions that come out when we have those topics. ⁓ Let's talk about the fourth pillar then, teamwork, because this, I think, builds really well on what we just talked about. And the idea that there's actually, Scrum is a team sport. ⁓ So beyond just normal human personality conflict type issues, what do you see that gets in the way of teams actually Mike (21:58) Mm-hmm. Mm-hmm. Brian Milner (22:18) working as a team. Mike (22:19) think ego is probably one, right? I can do everything better, just leave me alone. There's an old book that says basically, beware of a lone developer in a room, right? You know, it was referring to the developer who wants to close their door and say, I'll it done in a month, trust me, right? And one of the companies I worked with, and this one's going back like 15 years ago, but it was a really good story. Brian Milner (22:36) Yeah. Mike (22:43) is they would literally grab one unit of work. Each person on the team would grab a unit of work and take anywhere from three to 12 months to do the thing. So they were big things, but the person would do everything on it. They'd coded, tested everything. And the organization was putting out very little because of this. When they moved to Scrum in the first year, by their estimate, they said they delivered 540 % more work. over five times the amount of new features delivered. And that was through the collaboration, through the short iterations, those type of things. But it was about getting people to collaborate more. So I think there's huge opportunities to do that. One of the problems I see is when we don't overlap work. If we think about that organization I just described, you grab your thing, you're done in six months. I grab mine, I'm done in seven months. If we'd work together on those things, what's not make us any faster? No faster. But you and I could have worked on your one thing and been done in three months. OK, we're delivering value in three months, right? And so one of the things I look for a lot is how much teams are overlapping work, right? And if we're not overlapping work, there's huge opportunities to improve at that. I'll a little example of this. One of my favorite restaurants is, I don't know, barely call it a restaurant. It's a fast food deli. It's called Jimmy John's. Have you been to Jimmy John's, Yeah. Yeah, there's one near my house where I can go there and the wine will be out the door. Right. And you know, normally you see a wine out the door and it's like, crap, I'm going somewhere else. Right. These guys are so fast. They're so fast. When I get to the front, I place my order. I play this little game of can I fill up my cup? You know, I get an iced tea and they give me an empty cup and can I go fill up ice and put the tea in before they hand me my sandwich? And it's about 50-50. Right. It doesn't take long to fill up your iced tea. But the way they do that is the overlap work. As soon as I order my Italian club sandwich, somebody's already got the bread open, somebody's got a slab of meat they're ready to drop on there, somebody else has their hands over the vegetables and they're dropping the vegetables on there, and then a fourth person wraps it up. And so like four or five people touch my sandwich. Hopefully their hands are clean, but four or five people touch my sandwich as opposed to like most delis where I go and it's like you watch one person plod along making the sandwich, right? Overlap work is huge. Brian Milner (25:07) Yeah. Yeah, this episode sponsored by, no, just kidding. Use code Mike Cohn when you go to, no, just kidding. Yeah, I agree. And yeah, yeah, I'm familiar with Jimmy John's. Probably too familiar. ⁓ Yes, yeah, no, that's, I think that's part of their shtick is that they're, you know, they're known for being fast. So yeah. Mike (25:10) You Is yours just as fast? Yeah. Yeah. They call it Freaky Fast. They actually have a competition. I've seen YouTube videos of this where they get like the best teams at various restaurants race, right? And so they have like the Jimmy John sandwich making Olympics or something, but it's a skill. Brian Milner (25:36) wow, wow, yeah. You should pair that up with the hot dog eating challenge in some way and see if we could have a team sport going there. ⁓ Mike (25:48) Well, that's a good point because think about the hot dog eating. That's one guy, right? That's Joey Chesnett shoving hot dogs down. The Jimmy Johns is a team. They get the best crew at a restaurant and it's a team, right? How fast can the team go? Not how fast can one guy make a sandwich, right? Brian Milner (25:51) Yeah. Yeah, yeah. That's awesome. So what are some tips? What are some ways that you can really unite a team, especially those new teams? Because that's the fascination point for me is, how do you take this group of humans that really don't know each other and haven't worked together in the past and unite them together and have them gel as a team? How do you do that? Mike (26:21) I'll give you a couple. One, I think having really crisp sprint goals helps. So we all know exactly what we're trying to get done in the sprint. We don't lose sight of that because sometimes in the middle of a sprint, you lose sight of it. And you get myopic and you just focus on a list of tasks. And I'm going to say that it's probably similar to the team doing sprint planning and just getting them assessed with the numbers. It's not about the numbers. It's not about the tasks. It's about the backlog items that lead to some goal. So crisp sprint goals help. That's a hard phrase. Crisp Sprinkles helps. The other one I'd say is having a shared vision about where you're headed over a little bit longer term. Probably the biggest change to the Scrum Guide ever that I've liked is the inclusion of a product goal. And that was something I'd been talking about forever. mean, literally since I started doing Scrum was that sprinkles are great, but they're pretty short, right? You want to have something bigger. Brian Milner (26:52) It is. Mike (27:14) And so I like having product goals that are a few months out there. And one of the things I like doing for product goals is have teams do something like write a press release that describes their goal or create a vision in some way, write a review that you want to see come out on the App Store, Play Store, and a magazine. And one of my clients made software and they were reviewed by a major magazine and they were given an editor's choice runner up award. And they actually estimated that being runners up for that was probably worth about $10 million. First place, first time was worth about $10 million a year to them. And so they decided to get serious about this and they wrote a review. Their scrum master, she was actually combo scrum master product owner, Erin. She had the team write a review and she said, let's go earn this review. And I literally remember the email I got from her three months later. It was because it was Halloween night. I just like, you know, brought in the candy from outdoors. We're done trick or treating. And I checked my email. I a three word email from her from Erin. said we did it. And the magazine had let her know, hey, we're reviewing you. be out on, you know, like Tuesday's edition. And the review had quotes in there that were from their vision review, right? The things that they had wanted to achieve. Brian Milner (28:22) Ha ha. Mike (28:35) And that team had just really jelled around that and just became so much more productive and collaborated so much better because of that shared vision. Brian Milner (28:43) Yeah, that's amazing. getting back to the course then, I know in the course we're trying to kind of some of those collaboration muscles. What are some of the ways that the course helps to build that? Mike (28:56) think one of the key things that we're doing, and I'm excited about this, is that we're, you know, we of course use Zoom breakout rooms, right? You you go talk about this, we'll see you in eight minutes or something like that. And for this course, we're doing something where a group of three or more, when they register, can have a private breakout room. And this to me is exciting because people get the benefit of having a private breakout room. They can have sensitive discussions if they want. They can talk very specifically about. you know, what do we do about our jerk product owner? mean, whatever it is, right? You know, they can talk about their specific issues, yet have the context of a broader class. Because I think in one of the benefits of any public class is hearing how other teams are doing things. And sometimes that's because you get a good advice, you know, how did you solve that problem? We have that problem. Other times, it's just feeling that you're not alone in the world. they've got that problem too, right? And they don't have any solution for me, but I know I'm not alone in the world with this. And so I like these private breakout rooms for three or more. I think it's a novel thing we're doing with this class. And it's with the intent of combining the best of both worlds of private and public training for this. I'd the other thing is probably consistency, having everybody on the team hear the same message, having those discussions with an experienced instructor like you or me in the room to provide guidance when they have questions. know, go back to the role clarity, right? You know, they can talk about it and they're there. Then they're back in the main room with you or me and we can kind of answer questions. So I think that consistency will be huge as well. Brian Milner (30:25) Yeah, yeah, I love that idea of the private private breakout rooms that that's that's gonna be huge for a lot of people I know. ⁓ Mike (30:31) I'm excited to try it with this. This will be the first classes we do that for. I'm excited about it. Brian Milner (30:36) Yeah, yeah. Well, let's bring it home then and talk about the fifth pillar because the fifth pillar is really interesting as well. It talks about support beyond the team and teams can only do so much. Every team struggles when they're not supported well. And there's lots of studies that show leadership support is one of the biggest hurdles or obstacles to the adoption. Mike (30:46) Mm-hmm. Brian Milner (30:59) What does that support look like from outside the team and how can a team influence that? Mike (31:06) Yeah, if you're trying to be agile and your HR group has quarterly reviews of personnel that are all based on individual performance and has nothing to do about teamwork in there, it's going to be hard to focus on collaboration. So we have to kind of fix these issues. I think what we have to do here is to have team members educate those outside the organization. And we have information that we share about, you here's how to talk to a boss that's maybe mandating deadlines, things like that. And so we try to coach people through having some of those challenging conversations. And one of things I want teams to do is kind of become an example of what good agile looks like. And if you have a team that's excelling with agile and they're doing it from a kind of principles first, that mindset first approach. You're going to see other groups look at that and let's say the marketing group. They're going to look at that go, hey, that's an interesting way to work. I wonder how we could do that, right? And it's going look different for a marketing group than a tech team. the mindset is going to be the same. Principles will still be the same. And so when we get teams to do really well with this, other parts of the organization start to get interested. And then they stop being as much in our way. Brian Milner (32:20) Yeah. I know one of the most important aspects here and that we talk about is, is that you don't need to, to wait, right? If you're the team level, you don't have to just sit around and wait for the organization to make changes. you, you have opportunities to make changes as well. So how does that happen? How's the team change, you know, bring about those changes that, improve the agile process, the results. Mike (32:42) I think that's by being the example so that people see it. I think it's by having those conversations. You know, one of the things that we'll get is, you know, it's so common is the product owner that wants to change their mind all the time. I was reading something, I guess this is in our Agile mentors community, I think is where it was, but it was about the, you know, the product owner who said his favorite thing about Agile is that he can reprioritize every week. ⁓ And it's like, you can, you know. Brian Milner (33:05) Hmm. Yeah Mike (33:10) I'm not sure it's good. And I think about that, a team gets momentum, right? And you're working on a certain feature. Next sprint, it would be nice to work in that same area of this system, right? Your head's there. Just kind of keep going a little bit. And I've often described this as like, let's say you're working on three backlog items that are in a certain area of this system. Let's make it concrete. Let's say it's the spell checker in Microsoft Office, right? And you do three backlog items related to the spell checker this sprint. Next sprint, maybe your top priority is not more spell checker stuff, but maybe items, I don't know, 25, 26, and 27 on the backlog are still in the spell checker. You know what? It might be better to do those. There are probably two or three sprints away. Let's bring them into this sprint. Just get them done while my head's into spell checking. And so getting product owners or stakeholders to stop doing that, one of the ways that I like to talk about doing that is using an example of ordering a meal at a restaurant. I can order, let's say, the chicken entree. And then as the waiter is taking the orders around the table, I change from chicken, no, bring me the fish. Not a big deal. The waiter is going to cross off chicken and write down fish. If the waiter goes away, brings me back my salad, and I change my mind then, I say, hey, bring me the fish. Might not be a big deal. It's going to be a big deal if I've already taken three bites of the chicken. right? Or if he brings me the chicken. So yeah, we can change our mind, but there's a cost, right? And we want to educate stakeholders about that cost. They don't overdo it. Brian Milner (34:31) Yeah. Yeah. Well, speaking of the leaders and the organization, managers, leaders, do you think this course is appropriate for managers and leaders to attend as well? you feel like they might need to in order to really have this be an impact? Mike (34:55) Yeah, that's a good question. Is it appropriate? Yeah, I think it's appropriate. When we do this privately, we've had plenty of leaders and managers attend. I think it's great. I don't think that's required because they're not on the Scrum team. You said the name of the course is working on a Scrum team. And so they're not on the Scrum team. They benefit by knowing more how their Scrum team works. But I think what we found is that having just a key subset of people who hear the same message work through the training together, and then go back to the organization. That's enough to bring the passion, conviction, and skills that we want. So we don't truly need leaders. They're great. I would never talk a leader out of going, but I wouldn't. If I were a team and I could take the class this month or with my leader next month, I would just get the class done, right? And educate the leader afterwards. Brian Milner (35:41) Yeah. Yeah, yeah, I think that's a good plan. All right, well then we've made our way through the five pillars and for people who have come this far with us and are at this point, if they're listening and they're recognizing some of these problems we've been talking about, what would you recommend to them as next steps here? Mike (35:49) if Well, take a look at our website. If you go to mountaingoatsoftware.com. And then I think there's a courses link on the top. You can go up there and find the link to this course. It's an exciting one that we're doing. I've literally been teaching this, I think the first time I taught a class called Working on a Scrum Team was 2003 or 2004. it's a time tested course. You and I kind of redesigned it a couple of months ago to make it appropriate for public. or little better just in general and more appropriate for public. But it's a time-tested course that's now designed to be available for public settings instead of, you know, have to have 25 people or something. Brian Milner (36:36) Yeah, yeah, that's really exciting. I can't wait to see kind of how people are in, you know, react and interact in the course to some of these concepts and ideas. And we'll, we'll of course link to all these things that we've talked about in our show notes and make it easy for everyone to find the course listing and, and, you know, where the dates and everything that we're going to offer them. So make sure to check that out. Mike, thanks so much for coming on. This has been really enlightening and I appreciate you making time for it. Mike (37:01) Of course, thanks for having me, Brian. Always a pleasure.
Are you struggling to stay on top of your podcast guest appearances? Without a system, opportunities fall through the cracks, deadlines get missed, and follow-ups become overwhelming. In this episode, Candy Messer shares a simple but powerful way to track every step of the guesting process, from applications and scheduling to interviews and promotions. Get ready to streamline your workflow, stay organized, and make podcast hosts want to invite you back!MORE FROM THIS EPISODE: HTTPS://PODMATCH.COM/EP/335Chapters00:00 Introduction to Podcast Guest Management01:26 Project Management Systems for Podcasting06:00 Using Spreadsheets for Tracking Podcast Appearances08:47 Creating a Marketing Calendar for Promotions11:39 Conclusion and Key TakeawaysTakeawaysWithout a system, managing podcast appearances can feel overwhelming.A project management system helps track progress effectively.Using a checklist style is ideal for those who love organization.The Kanban board style is great for visual learners.Google Sheets can be a simple alternative for tracking.Color coding tasks can provide a quick visual reference.A marketing calendar is essential for planning promotions.Plan your promotions around your content schedule.Tagging hosts in promotions helps increase visibility.Finding the right system is key to managing podcast appearances.MORE FROM THIS EPISODE: HTTPS://PODMATCH.COM/EP/335
© 2020-2025 Ivy Podcast Discovery LLC
