AI Assisted Coding: Swimming in AI - Managing Tech Debt in the Age of AI-Assisted Coding | Lou Franco

AI Assisted Coding: Swimming in AI - Managing Tech Debt in the Age of AI-Assisted Coding | Lou Franco

AI Assisted Coding: Swimming in AI - Managing Tech Debt in the Age of AI-Assisted Coding

In this special episode, Lou Franco, veteran software engineer and author of "Swimming in Tech Debt," shares his practical approach to AI-assisted coding that produces the same amount of tech debt as traditional development—by reading every line of code. He explains the critical difference between vibecoding and AI-assisted coding, why commit-by-commit thinking matters, and how to reinvest productivity gains into code quality.

Vibecoding vs. AI-Assisted Coding: Reading Code Matters

"I read all the code that it outputs, so I need smaller steps of changes."

Lou draws a clear distinction between vibecoding and his approach to AI-assisted coding. Vibecoding, in his definition, means not reading the code at all—just prompting, checking outputs, and prompting again. His method is fundamentally different: he reads every line of generated code before committing it. This isn't just about catching bugs; it's about maintaining architectural control and accountability. As Lou emphasizes, "A computer can't be held accountable, so a computer can never make decisions. A human always has to make decisions." This philosophy shapes his entire workflow—AI generates code quickly, but humans make the final call on what enters the repository. The distinction matters because it determines whether you're managing tech debt proactively or discovering it later when changes become difficult.

The Moment of Shift: Staying in the Zone

"It kept me in the zone. It saved so much time! Never having to look up what a function's arguments were... it just saved so much time."

Lou's AI coding journey began in late 2022 with GitHub Copilot's free trial. He bought a subscription immediately after the trial ended because of one transformative benefit: staying in the flow state. The autocomplete functionality eliminated constant context switching to documentation, Stack Overflow searches, and function signature lookups. This wasn't about replacing thinking—it was about removing friction from implementation. Lou could maintain focus on the problem he was solving rather than getting derailed by syntax details. This experience shaped his understanding that AI's value lies in removing obstacles to productivity, not in replacing the developer's judgment about architecture and design.

Thinking in Commits: The Right Size for AI Work

"I think of prompts commit-by-commit. That's the size of the work I'm trying to do in a prompt."

Lou's workflow centers on a simple principle: size your prompts to match what should be a single commit. This constraint provides multiple benefits. First, it keeps changes small enough to review thoroughly—if a commit is too big to review properly, the prompt was too ambitious. Second, it creates a clear commit history that tells a story about how the code evolved. Third, it enables easy rollback if something goes wrong. This commit-sized thinking mirrors good development practices that existed long before AI—small, focused changes that each accomplish one clear purpose. Lou uses inline prompting in Cursor (Command-K) for these localized changes because it keeps context tight: "Right here, don't go look at the rest of my files... Everything you need is right here. The context is right here... And it's fast."

The Tech Debt Question: Same Code, Same Debt

"Based on the way I've defined how I did it, it's exactly the same amount of tech debt that I would have done on my own... I'm faster and can make more code, but I invest some of that savings back into cleaning things up."

As the author of "Swimming in Tech Debt," Lou brings unique perspective to whether AI coding creates more technical debt. His answer: not if you're reading and reviewing everything. When you maintain the same quality standards—code review, architectural oversight, refactoring—you generate the same amount of debt as manual coding. The difference is speed. Lou gets productivity gains from AI, and he consciously reinvests a portion of those gains back into code quality through refactoring. This creates a virtuous cycle: faster development enables more time for cleanup, which maintains a codebase that's easier for both humans and AI to work with. The key insight is that tech debt isn't caused by AI—it's caused by skipping quality practices regardless of how code is generated.

When Vibecoding Creates Debt: AI Resistance as a Symptom

"When you start asking the AI to do things, and it can't do them, or it undoes other things while it's doing them... you're experiencing the tech debt a different way. You're trying to make changes that are on your roadmap, and you're getting resistance from making those changes."

Lou identifies a fascinating pattern: tech debt from vibecoding (without code review) manifests as "AI resistance"—difficulty getting AI to make the changes you want. Instead of compile errors or brittle tests signaling problems, you experience AI struggling to understand your codebase, undoing changes while making new ones, or producing code with repetition and tight coupling. These are classic tech debt symptoms, just detected differently. The debt accumulates through architecture violations, lack of separation of concerns, and code that's hard to modify. Lou's point is profound: whether you notice debt through test failures or through AI confusion, the underlying problem is the same—code that's difficult to change. The solution remains consistent: maintain quality practices including code review, even when AI makes generation fast.

Can AI Fix Tech Debt? Yes, With Guidance

"You should have some acceptance criteria on the code... guide the LLM as to the level of code quality you want."

Lou is optimistic but realistic about AI's ability to address existing tech debt. AI can definitely help with refactoring and adding tests—but only with human guidance on quality standards. You must specify what "good code" looks like: acceptance criteria, architectural patterns, quality thresholds. Sometimes copy/paste is faster than having AI regenerate code. Very convoluted codebases challenge both humans and AI, so some remediation should happen before bringing AI into the picture. The key is recognizing that AI amplifies your approach—if you have strong quality standards and communicate them clearly, AI accelerates improvement. If you lack quality standards, AI will generate code just as problematic as what already exists.

Reinvesting Productivity Gains in Quality

"I'm getting so much productivity out of it, that investing a little bit of that productivity back into refactoring is extremely good for another kind of productivity."

Lou describes a critical strategy: don't consume all productivity gains as increased feature velocity. Reinvest some acceleration back into code quality through refactoring. This mirrors the refactor step in test-driven development—after getting code working, clean it up before moving on. AI makes this more attractive because the productivity gains are substantial. If AI makes you 30% faster at implementation, using 10% of that gain on refactoring still leaves you 20% ahead while maintaining quality. Lou explicitly budgets this reinvestment, treating quality maintenance as a first-class activity rather than something that happens "when there's time." This discipline prevents the debt accumulation that makes future work progressively harder.

The 100x Code Concern: Accountability Remains Human

"Directionally, I think you're probably right... this thing is moving fast, we don't know. But I'm gonna always want to read it and approve it."

When discussing concerns about AI generating 100x more code (and potentially 100x more tech debt), Lou acknowledges the risk while maintaining his position: he'll always read and approve code before it enters the repository. This isn't about slowing down unnecessarily—it's about maintaining accountability. Humans must make the decisions because only humans can be held accountable for those decisions. Lou sees potential for AI to improve by training on repository evolution rather than just end-state code, learning from commit history how codebases develop. But regardless of AI improvements, the human review step remains essential. The goal isn't to eliminate human involvement; it's to shift human focus from typing to thinking, reviewing, and making architectural decisions.

Practical Workflow: Inline Prompting and Small Changes

"Right here, don't go look at the rest of my files... Everything you need is right here. The context is right here... And it's fast."

Lou's preferred tool is Cursor with inline prompting (Command-K), which allows him to work on specific code sections with tight context. This approach is fast because it limits what AI considers, reducing both latency and irrelevant changes. The workflow resembles pair programming: Lou knows what he wants, points AI at the specific location, AI generates the implementation, and Lou reviews before accepting. He also uses Claude Code for full codebase awareness when needed, but the inline approach dominates his daily work. The key principle is matching tool choice to context needs—use inline prompting for localized changes, full codebase tools when you need broader understanding. This thoughtful tool selection keeps development efficient while maintaining control.

Resources and Community

Lou recommends Steve Yegge's upcoming book on vibecoding. His website, LouFranco.com, provides additional resources.

About Lou Franco

Lou Franco is a veteran software engineer and author of Swimming in Tech Debt. With decades of experience at startups, as well as Trello, and Atlassian, he's seen both sides of debt—as coder and leader. Today, he advises teams on engineering practices, helping them turn messy codebases into momentum.

You can link with Lou Franco on LinkedIn and visit his website at LouFranco.com.

Jaksot(200)

Business Case Ownership—The Product Owner's Core Duty | Lilia Pulova

Business Case Ownership—The Product Owner's Core Duty | Lilia Pulova

Lilia Pulova: Business Case Ownership—The Product Owner's Core Duty 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 Great Product Owner: Always Present and Inspirational Lilia describes an exceptional Product Owner whose defining characteristic was consistent presence with the team. This presence went beyond just showing up - it was inspirational and made team members genuinely care about their delivery and the product they were building. The Product Owner served as the vital connection between the team and the organization's wider mission, helping everyone understand how their work contributed to the bigger picture. This constant engagement and visibility created a motivated team that took pride in their product development efforts. The Bad Product Owner: Unprepared and Responsibility-Shifting Lilia encountered a Product Owner who exemplified poor practices by consistently arriving at backlog refinement meetings without any preparation, expecting developers to provide business context instead. This approach was fundamentally wrong because developers aren't equipped to discuss business expectations or product direction - that's the Product Owner's responsibility. This individual habitually said "yes" to all tickets without consideration, shifted decision-making responsibility to the team, and relied on architects to manage the product and determine sprint priorities. Product Owners must own the business case rather than delegate it, and keep the business rationale constantly visible to the team. Self-reflection Question: How do you ensure your Product Owner maintains proper preparation and ownership of business decisions rather than shifting these responsibilities to the development team? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Lilia Pulova Lilia Pulova, a former Business Intelligence Analyst, discovered her passion as a Scrum Master by chance. A natural communicator with a love for languages, she now bridges the gap between business and tech, translating complex needs into streamlined processes that boost productivity and keep teams aligned and focused. You can link with Lilia Pulova on LinkedIn.

27 Kesä 12min

Building Self-Sufficient Teams Through Emotional Intelligence | Lilia Pulova

Building Self-Sufficient Teams Through Emotional Intelligence | Lilia Pulova

Lilia Pulova: Building Self-Sufficient Teams Through Emotional Intelligence 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. Lilia defines success for Scrum Masters by asking a simple but powerful question: "Do people feel supported?" Her approach focuses on training teams to take on her responsibilities and make their own decisions. Rather than dictating solutions, she presents options and allows teams to choose their path. Over time, teams learn these options and develop independence in decision-making. She maintains awareness by monitoring delivery metrics, watching for tickets that take too long, and staying attentive during daily stand-ups. With her primarily remote team keeping cameras open, Lilia reads emotions and body language to identify potential issues early, preventing small conflicts from escalating into major problems. Self-reflection Question: How well do you read the emotional state of your team members, and what early warning signs might you be overlooking? Featured Retrospective Format for the Week: 1-on-1 Retrospective Lilia advocates for the 1-on-1 retrospective as her most effective format, explaining that people open up more in private conversations than in group settings. While group retrospectives can work well with smooth conversation flow, she finds that structured formats don't always suit every team - sometimes the "lack of format" creates better outcomes. The key to successful 1-on-1 retrospectives is building strong relationships and establishing trust, which she considers the most important foundation for effective retrospectives. [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Lilia Pulova Lilia Pulova, a former Business Intelligence Analyst, discovered her passion as a Scrum Master by chance. A natural communicator with a love for languages, she now bridges the gap between business and tech, translating complex needs into streamlined processes that boost productivity and keep teams aligned and focused. You can link with Lilia Pulova on LinkedIn.

26 Kesä 13min

Leading Transformation: Leading an Agile Transformation—The Power of Patience and Small Winss | Lilia Pulova

Leading Transformation: Leading an Agile Transformation—The Power of Patience and Small Winss | Lilia Pulova

Lilia Pulova: Leading an Agile Transformation—The Power of Patience and Small Wins 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. Lilia shares her experience leading a genuine Agile transformation in an organization just beginning their journey. Faced with widespread skepticism and resistance, she encountered impatient stakeholders demanding immediate results during the challenging first 2-3 months. The breakthrough came after two months when stakeholders finally witnessed tangible improvements in the application and faster release cycles. Patience emerged as the critical skill that carried the transformation through its most difficult phase. Lilia emphasizes the importance of conducting numerous one-on-one conversations and consistently praising teams while celebrating small wins to maintain motivation throughout the change process. Self-reflection Question: How do you maintain team morale and stakeholder confidence during the uncertain early phases of organizational change? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Lilia Pulova Lilia Pulova, a former Business Intelligence Analyst, discovered her passion as a Scrum Master by chance. A natural communicator with a love for languages, she now bridges the gap between business and tech, translating complex needs into streamlined processes that boost productivity and keep teams aligned and focused. You can link with Lilia Pulova on LinkedIn.

25 Kesä 11min

Leadership Red Flag—When Managers Care More About Career Than Team Success | Lilia Pulova

Leadership Red Flag—When Managers Care More About Career Than Team Success | Lilia Pulova

Lilia Pulova: Leadership Red Flag—When Managers Care More About Career Than Team Success 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. Lilia shares the story of when she worked with a troubled team where all projects were running late. As a junior Scrum Master, she struggled to identify that the root cause was a manager more focused on career advancement than team success. This manager only paid attention to team members who could provide exposure to higher management, dismissing other requests with "let's solve that later." Integration problems mounted, key people were absent, and when COVID arrived, the team was ultimately disbanded. This experience taught Lilia crucial lessons about taking ownership of team success and viewing the Scrum Master role as a continuous learning journey in leadership. Self-reflection Question: How well do you understand the human dynamics within your team, and what signals might you be missing about individual motivations? Featured Book of the Week: 48 Laws of Power by Robert Greene Lilia recommends "48 Laws of Power" by Robert Greene for its insights into human behavior and understanding the consequences of our actions when working with others. As Scrum Masters who interact with humans daily, this book helps develop awareness of interpersonal dynamics. One key principle Lilia applies is "always say less than necessary" - helping teams make decisions rather than overwhelming them with too much information or direction. [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Lilia Pulova Lilia Pulova, a former Business Intelligence Analyst, discovered her passion as a Scrum Master by chance. A natural communicator with a love for languages, she now bridges the gap between business and tech, translating complex needs into streamlined processes that boost productivity and keep teams aligned and focused. You can link with Lilia Pulova on LinkedIn.

24 Kesä 14min

When Architects Push Solutions—Learning to Disagree but Commit in Agile Teams | Lilia Pulova

When Architects Push Solutions—Learning to Disagree but Commit in Agile Teams | Lilia Pulova

Lilia Pulova: When Architects Push Solutions—Learning to Disagree but Commit in Agile Teams 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. Lilia shares a challenging situation where an architect pushed a complex solution that she felt might be too difficult for her less-experienced team. Despite having two alternative solutions that better suited the team's capabilities, she chose to let go of her concerns and try the architect's approach. This decision required significant adaptation and ongoing conversations with her frustrated team members. By informing her manager about the team's frustration level and working closely with the team to adapt the solution to their context, Lilia demonstrates the valuable principle of "disagree but commit" - sometimes you need to let go of your preferred approach and learn from trying something different. Self-reflection Question: When have you had to set aside your preferred solution to support a team decision, and what did you learn from that experience? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Lilia Pulova Lilia Pulova, a former Business Intelligence Analyst, discovered her passion as a Scrum Master by chance. A natural communicator with a love for languages, she now bridges the gap between business and tech, translating complex needs into streamlined processes that boost productivity and keep teams aligned and focused. You can link with Lilia Pulova on LinkedIn.

23 Kesä 13min

BONUS: Never Stop Experimenting—Building a Culture of Continuous Discovery | Stavros Stavru

BONUS: Never Stop Experimenting—Building a Culture of Continuous Discovery | Stavros Stavru

BONUS: Never Stop Experimenting—Building a Culture of Continuous Discovery with Stavros Stavru In this BONUS episode, we dive deep into the world of continuous experimentation with Stavros Stavru, Ph.D. in Organizational Transformations and founder of EdTech ventures AhaPlay and The Caringers. Stavros shares insights from his latest book "Never Stop Experimenting" and reveals how teams can maintain their discovery mindset while balancing the pressures of delivery. The Exploration-Exploitation Dilemma "What would we choose? What we know, and try to exploit? Or go for something new, and better than we currently have?" Stavros introduces us to one of the fundamental challenges facing modern teams: the tension between exploration and exploitation. He explains how teams often start with an exploration mindset, focused on solving real problems through discovery. However, over time, there's a natural shift from discovery to delivery, and teams forget the importance of continued exploration. The title "Never Stop Experimenting" serves as an anchor for teams to remember the value of maintaining their experimental approach even when delivery pressures mount. Born from a Decade of Practice "All the techniques that I describe in the book were born during 10 years of practice." The book isn't theoretical - it's grounded in real-world application. Stavros shares how every technique and framework in "Never Stop Experimenting" emerged from his extensive hands-on experience working with teams over a decade. This practical foundation ensures that readers get battle-tested approaches rather than untested concepts. Software Development as Incremental Experiments "Experimentation requires a creative process." Stavros addresses a common challenge: while teams understand the benefits of experimentation and want to experiment, they often face management resistance that ultimately demotivates the team. He emphasizes that viewing software development as a series of incremental experiments isn't just beneficial - it's absolutely necessary for teams to remain innovative and responsive to changing needs. The Fatware Matrix: Putting Products on a Diet "The challenge: how do you convince the business that you need to spend some time removing features?" One of the book's standout concepts is "The Fatware Matrix," which helps Product Managers recognize when their product is becoming bloated. Stavros introduces a practical tool combining the Kano framework with maintenance cost analysis to illustrate the true cost and impact of maintaining old features. This approach helped one team successfully remove features from their software, with stakeholders later commenting, "Now this is more transparent for us." The key is managing feature creep and software bloat before they become overwhelming. The NSE Ratio: Optimizing Experimentation Rhythm "It's when we try something new that we learn what works. We need to change something on a regular basis." The NSE (Never Stop Experimenting) Ratio measures how long teams wait before introducing new approaches or experimenting with their processes. Stavros explains how teams should define their NSE ratio as part of their team agreements, establishing a regular cadence for trying new things. This systematic approach ensures that learning and adaptation become embedded in the team's rhythm rather than happening sporadically. Building a Safe-to-Fail Culture "Speak of your own failures. When we show our failures as leaders, we show the team that they can run their own experiments." Creating a truly safe-to-fail environment requires leaders to model vulnerability and transparency about their own mistakes. Stavros emphasizes that leaders must give the example by sharing their failures openly, which gives permission for the rest of the organization to take risks and learn from their own experiments. This leadership modeling is crucial for establishing psychological safety around experimentation. About Stavros Stavru Stavros is a Ph.D. in Organizational Transformations and a leading voice in Agile coaching, leadership, and soft skills. Founder of EdTech ventures AhaPlay and The Caringers, he has delivered over 800 trainings and authored Never Stop Experimenting, a powerful toolkit for continuous improvement across teams and organizations. You can connect with Stavros Stavru on LinkedIn, and check his book site at Neverstopexperimenting.com.

21 Kesä 31min

The Product Owner Mindset in Construction | Luca Cotta Ramusino

The Product Owner Mindset in Construction | Luca Cotta Ramusino

Agile in Construction: Why Construction Teams Need Product Owner Thinking with Luca Cotta Ramusino 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 Great Product Owner: The Customer Value Detective Luca discovered that applying the Product Owner role in construction requires thinking like a customer and understanding that "it's the customer that defines what value is." The great Product Owner in construction acts as a customer value detective, constantly asking "which task out of these is going to move the yardstick?" They ensure that work always serves a customer—if you can't identify your customer, you should stop and find one. This mindset transforms how construction teams approach their daily huddles and project planning, viewing everything through the lens of customer value rather than just task completion. The Bad Product Owner: The Waste Accumulator The bad Product Owner in construction fails to eliminate waste from processes, allowing non-value-adding activities to persist simply because "that's how we've always done it." They struggle to have candid conversations with customers and fail to tease out real requirements. Instead of transforming language into customer reality, they ask customers directly "what they want" without understanding that customers are better at identifying what they don't want than articulating what they need. This approach leads to projects that complete tasks without delivering real value. In this segment, refer to The Last Planner Method. Self-reflection Question: Can you clearly identify the customer for every piece of work your team performs, and how do you ensure that work truly moves the project toward completion? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Luca Cotta Ramusino Luca is a passionate Lean advocate with roots in the construction industry, now guiding teams through agile transformation. He thrives on exploring uncharted territory, then helping clients navigate it with confidence. Ask him how Lean and agile methods can unlock your team's potential in today's fast-paced, ever-evolving work environment. You can link with Luca Cotta Ramusino on LinkedIn.

20 Kesä 17min

Managing The Network of Promises in Lean Construction | Luca Cotta Ramusino

Managing The Network of Promises in Lean Construction | Luca Cotta Ramusino

Agile in Construction: Managing The Network of Promises in Lean Construction, with Luca Cotta Ramusino 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. Luca defines success in Lean construction through two critical metrics from the Last Planner Method: PPC (Percentage of Plan Complete) and RNC (Reasons for Not Completing). Success means creating reliable promises in what he describes as construction's "network of promises." The Last Planner Method removes layers of management by having those closest to the work do the planning themselves. PPC measures how reliable your promises are—similar to Scrum's definition of "done"—while RNC identifies where problems concentrate, typically in 2-3 areas. Both the work provider and receiver must agree on what "complete" means for these metrics to be meaningful. Featured Retrospective Format for the Week: Reflect and Disinfect Luca developed this daily retrospective practice where people share what was interesting about their work day without formal meetings. Inspired by both Scrum retrospectives and Toyota's focus on reflection and introspection, this 15-minute format answers three questions: what should we continue doing, what should we stop doing, and what should we start doing? The practice emphasizes that teams need moments to stop and think back in order to improve how they work. The informal nature makes it accessible to construction crews who might resist traditional meeting formats. Self-reflection Question: How reliable are the promises your team makes, and what patterns do you see in the reasons they're not kept? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Luca Cotta Ramusino Luca is a passionate Lean advocate with roots in the construction industry, now guiding teams through agile transformation. He thrives on exploring uncharted territory, then helping clients navigate it with confidence. Ask him how Lean and agile methods can unlock your team's potential in today's fast-paced, ever-evolving work environment. You can link with Luca Cotta Ramusino on LinkedIn.

19 Kesä 18min

Suosittua kategoriassa Politiikka ja uutiset

rss-ootsa-kuullut-tasta
aikalisa
tervo-halme
ootsa-kuullut-tasta-2
politiikan-puskaradio
viisupodi
rss-podme-livebox
et-sa-noin-voi-sanoo-esittaa
otetaan-yhdet
rss-vaalirankkurit-podcast
aihe
the-ulkopolitist
rss-polikulaari-humanisti-vastaa-ja-muut-ts-podcastit
rss-hyvaa-huomenta-bryssel
rss-kuka-mina-olen
politbyroo
linda-maria
rss-lets-talk-about-hair
rss-50100-podcast
rss-tekoalyfoorumi