AI Assisted Coding: Augmented AI Development - Software Engineering First, AI Second With Dawid Dahl

AI Assisted Coding: Augmented AI Development - Software Engineering First, AI Second With Dawid Dahl

BONUS: Augmented AI Development - Software Engineering First, AI Second

In this special episode, Dawid Dahl introduces Augmented AI Development (AAID)—a disciplined approach where professional developers augment their capabilities with AI while maintaining full architectural control. He explains why starting with software engineering fundamentals and adding AI where appropriate is the opposite of most frameworks, and why this approach produces production-grade software rather than technical debt.

The AAID Philosophy: Don't Abandon Your Brain

"Two of the fundamental developer principles for AAID are: first, don't abandon your brain. And the second is incremental steps."

Dawid's Augmented AI Development framework stands in stark contrast to "vibecoding"—which he defines strictly as not caring about code at all, only results on screen. AAID is explicitly designed for professional developers who maintain full understanding and control of their systems. The framework is positioned on the furthest end of the spectrum from vibe coding, requiring developers to know their craft deeply. The two core principles—don't abandon your brain, work incrementally—reflect a philosophy that AI is a powerful collaborator, not a replacement for thinking. This approach recognizes that while 96% of Dawid's code is now written by AI, he remains the architect, constantly steering and verifying every step.

In this segment we refer to Marcus Hammarberg's work and his book The Bungsu Story.

Software Engineering First, AI Second: A Hill to Die On

"You should start with software engineering wisdom, and then only add AI where it's actually appropriate. I think this is super, super important, and the entire foundation of this framework. This is a hill I will personally die on."

What makes AAID fundamentally different from other AI-assisted development frameworks is its starting point. Most frameworks start with AI capabilities and try to add structure and best practices afterward. Dawid argues this is completely backwards. AAID begins with 50-60 years of proven software engineering wisdom—test-driven development, behavior-driven development, continuous delivery—and only then adds AI where it enhances the process. This isn't a minor philosophical difference; it's the foundation of producing maintainable, production-grade software. Dawid admits he's sometimes "manipulating developers to start using good, normal software engineering practices, but in this shiny AI box that feels very exciting and new." If the AI wrapper helps developers finally adopt TDD and BDD, he's fine with that.

Why TDD is Non-Negotiable with AI

"Every time I prompt an AI and it writes code for me, there is often at least one or two or three mistakes that will cause catastrophic mistakes down the line and make the software impossible to change."

Test-driven development isn't just a nice-to-have in AAID—it's essential. Dawid has observed that AI consistently makes 2-3 mistakes per prompt that could have catastrophic consequences later. Without TDD's red-green-refactor cycle, these errors accumulate, making code increasingly difficult to change. TDD answers the question "Is my code technically correct?" while acceptance tests answer "Is the system releasable?" Both are needed for production-grade software. The refactor step is where 50-60 years of software engineering wisdom gets applied to make code maintainable. This matters because AAID isn't vibe coding—developers care deeply about code quality, not just visible results. Good software, as Dave Farley says, is software that's easy to change. Without TDD, AI-generated code becomes a maintenance nightmare.

The Problem with "Prompt and Pray" Autonomous Agents

"When I hear 'our AI can now code for over 30 hours straight without stopping,' I get very afraid. You fall asleep, and the next morning, the code is done. Maybe the tests are green. But what has it done in there? Imagine everything it does for 30 hours. This system will not work."

Dawid sees two diverging paths for AI-assisted development's future. The first—autonomous agents working for hours or days without supervision—terrifies him. The marketing pitch sounds appealing: prompt the AI, go to sleep, wake up to completed features. But the reality is technical debt accumulation at scale. Imagine all the decisions, all the architectural choices, all the mistakes an AI makes over 30 hours of autonomous work. Dawid advocates for the stark contrast: working in extremely small increments with constant human steering, always aligned to specifications. His vision of the future isn't AI working alone—it's voice-controlled confirmations where he says "Yes, yes, no, yes" as AI proposes each tiny change. This aligns with DORA metrics showing that high-performing teams work in small batches with fast feedback loops.

Prerequisites: Product Discovery Must Come First

"Without Dave Farley, this framework would be totally different. I think he does everything right, basically. With this framework, I want to stand on the shoulders of giants and work on top of what has already been done."

AAID explicitly requires product discovery and specification phases before AI-assisted coding begins. This is based on Dave Farley's product journey model, which shows how products move from idea to production. AAID starts at the "executable specifications" stage—it requires input specifications from prior discovery work. This separates specification creation (which Dawid is addressing in a separate "Dream Encoder" framework) from code execution. The prerequisite isn't arbitrary; it acknowledges that AI-assisted implementation works best when the problem is well-defined. This "standing on shoulders of giants" approach means AAID doesn't try to reinvent software engineering—it leverages decades of proven practices from TDD pioneers, BDD creators, and continuous delivery experts.

What's Wrong with Other AI Frameworks

"When the AI decides to check the box [in task lists], that means this is the definition of done. But how is the AI taking that decision? It's totally ad hoc. It's like going back to the 1980s: 'I wrote the code, I'm done.' But what does that mean? Nobody has any idea."

Dawid is critical of current AI frameworks like SpecKit, pointing out fundamental flaws. They start with AI first and try to add structure later (backwards approach). They use task lists with checkboxes where AI decides when something is "done"—but without clear criteria, this becomes ad hoc decision-making reminiscent of 1980s development practices. These frameworks "vibecode the specs," not realizing there's a structured taxonomy to specifications that BDD already solved. Most concerning, some have removed testing as a "feature," treating it as optional. Dawid sees these frameworks as over-engineered, process-centric rather than developer-centric, often created by people who may not develop software themselves. AAID, in contrast, is built by a practicing developer solving real problems daily.

Getting Started: Learn Fundamentals First

"The first thing developers should do is learn the fundamentals. They should skip AI altogether and learn about BDD and TDD, just best practices. But when you know that, then you can look into a framework, maybe like mine."

Dawid's advice for developers interested in AI-assisted coding might seem counterintuitive: start by learning fundamentals without AI. Master behavior-driven development, test-driven development, and software engineering best practices first. Only after understanding these foundations should developers explore frameworks like AAID. This isn't gatekeeping—it's recognizing that AI amplifies whatever approach developers bring. If they start with poor practices, AI will help them build unmaintainable systems faster. But if they start with solid fundamentals, AI becomes a powerful multiplier that lets them work at unprecedented speed while maintaining quality. AAID offers both a dense technical article on dev.to and a gentler game-like onboarding in the GitHub repo, meeting developers wherever they are in their journey.

About Dawid Dahl

Dawid is the creator of Augmented AI Development (AAID), a disciplined approach where developers augment their capabilities by integrating with AI, while maintaining full architectural control. Dawid is a software engineer at Umain, a product development agency.

You can link with Dawid Dahl on LinkedIn and find the AAID framework on GitHub.

Avsnitt(200)

When Stepping Back Becomes Stepping Away—A Leadership Failure Story | Bernard Agrest

When Stepping Back Becomes Stepping Away—A Leadership Failure Story | Bernard Agrest

Bernard Agrest: When Stepping Back Becomes Stepping Away—A Leadership Failure Story 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. Bernard shares a powerful story about a critical research project where his instinct to step back and empower his team ultimately led to project failure and personal burnout. When Bernard realized his team wasn't ready for the work ahead, he made the mistake of taking everything on himself rather than building proper feedback loops and ensuring true understanding. Working overtime and feeling guilty about not supporting his team properly, Bernard learned that empowerment isn't about stepping back—it's about creating space to work together. His key insight reveals that it's through doing the work that we discover what work actually needs to be done, and that having people say they "get" the plan doesn't mean they truly understand it. Self-reflection Question: How do you distinguish between genuine team empowerment and abandonment when stepping back from direct involvement in projects? [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 Bernard Agrest Bernard currently leads a major software implementation at University of Wisconsin—Madison Medical School, serving over 10,000 employees. Previously, he built a PMO and led Data and Learning at Teach For America. His journey began redesigning operations for a Veteran Service Organization, where he co-led national initiatives and launched a new alumni program. You can link with Bernard Agrest on LinkedIn.

30 Juni 15min

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 Juni 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 Juni 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 Juni 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 Juni 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 Juni 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 Juni 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 Juni 17min

Populärt inom Politik & nyheter

aftonbladet-krim
svenska-fall
motiv
p3-krim
flashback-forever
fordomspodden
rss-viva-fotboll
rss-krimstad
aftonbladet-daily
rss-sanning-konsekvens
rss-vad-fan-hande
spar
rss-krimreportrarna
rss-frandfors-horna
blenda-2
olyckan-inifran
dagens-eko
krimmagasinet
rss-flodet
rss-expressen-dok