Agile Meets AI—How to Code Fast Without Breaking Things | Llewellyn Falco

Agile Meets AI—How to Code Fast Without Breaking Things | Llewellyn Falco

AI Assisted Coding: Agile Meets AI—How to Code Fast Without Breaking Things, With Llewellyn Falco

In this BONUS episode we explore the practice of coding with AI—not just the buzzwords, but the real-world experience. Our guest, Llewellyn Falco, has been learning by doing, exploring the space of AI-assisted coding from the experimental and intuitive—what some call vibecoding—to the more structured world of professional, world-class software engineering. This is a conversation for practitioners who want to understand what's actually happening on the ground when we code with AI.

Understanding Vibecoding

"You can now program without looking at code. When you're in that space, vibecoding is the word we're using to say, we are programming in a way that does not relate to programming last year."

The software development landscape shifted dramatically in early 2025. Vibecoding represents a fundamental change in how we create software—programming without constantly looking at the code itself. This approach removes many traditional limitations around technology, language, and device constraints, allowing developers to move seamlessly between different contexts. However, this power comes with responsibility, as developers can now move so fast that traditional safety practices become even more critical.

From Concept to Working App in 15 Minutes

"We wrote just a markdown page of 'here's what we want this to look like'. And then we fed that to Claude Code. And 15 minutes later we had a working app on the phone."

At the Agile 2025 conference in Denver, Llewellyn participated in a hackathon focused on helping psychologists prevent child abuse. Working with customer Amanda, a psychologist, and data scientist Rachel, the team identified a critical problem: clinicians weren't using the most effective parenting intervention technique because recording 60 micro-interactions in 5 minutes was too difficult and time-consuming.

The team's approach embodied lean startup principles turned up to eleven. After understanding the customer's needs through exposition and conversation, they created a simple markdown specification and used Claude Code to generate a working mobile app in just 15 minutes. When Amanda tested it, she was moved to tears—after 20 years of trying to make progress on this problem, she finally had hope. Over three days, the team released 61 iterations, constantly getting feedback and refining the solution.

Iterative Development Still Matters When Coding With AI

"We need to see things working to know what to deliver next. That's never going to change. Unless you're building something that's already there."

The team's success wasn't about writing a complete requirements document upfront. Instead, they delivered a minimal viable product quickly, tested it with real users, and iterated based on feedback. This agile approach proved essential even—or especially—when working with AI.

One breakthrough came when Amanda used the number keypad instead of looking at her phone screen. With her full attention on the training video she'd watched hundreds of times, she noticed an interaction she had missed before. At that moment, the team knew they had created real value, regardless of what additional features they might build.

Good Engineering Practices Without Looking at Code

"We asked it to do good engineering practices, even though we didn't really understand what it was doing. We just sort of say, okay, yeah, that seems sensible."

A critical moment came when the code had grown large and complex. Rather than diving into the code themselves, Llewellyn and his partner Lotta asked the AI to refactor the code to make a panel easy to switch before actually making the change. They verified functionality worked through manual testing but never looked at how the refactoring was implemented. This demonstrates that developers can maintain good practices like refactoring and clean architecture even when working at a higher level of abstraction.

Key practices for AI-assisted development include:

  • Don't accept AI's default settings—they're based on popularity, not best practices

  • Prime the AI with the practices you want it to use through configuration files

  • Tell AI to be honest and help you avoid mistakes, not just be agreeable

  • Ask for explanations of architecture and evaluate whether approaches make sense

  • Keep important decisions documented in markdown files that can be referenced later

"The documentation is now executable. I can turn it into code"

"The documentation is now executable. I can turn it into code. If I had to choose between losing my documentation or losing my code, I would keep the docs. I think I could regenerate the code pretty easily."

In this new paradigm, documentation takes on new importance—it becomes the specification from which code can be regenerated. The team created and continuously updated markdown files for project context, architecture, and individual features. This practice allowed them to reset AI context when needed while maintaining continuity of their work.

The workflow was bidirectional: sometimes they'd write documentation first and have AI generate code; other times they'd build features iteratively and have AI update the documentation. This approach using tools like Super Whisper for voice-to-text made creating and maintaining documentation effortless.

Remove Deterministic Tasks from AI

"AI is sloppy. It's inconsistent. Everything that can be deterministic—take it out. AI can write that code. But don't make AI do repetitive tasks."

A crucial principle emerged: anything that needs to be consistently and repeatedly correct should be automated with traditional code, not left to AI. The team wrote shell scripts for tasks like auto-incrementing version numbers and created git hooks to ensure these scripts ran automatically. They also automated file creation with dates at the top, removing the need for AI to track temporal information.

This principle works both ways—deterministic logic should be removed from underneath AI (via scripts and hooks) and from above AI (via orchestration scripts that call AI in loops with verification steps in between).

Anti-Patterns to Avoid

"The biggest anti-pattern is you're not committing frequently. I really want the ability to drop my context and revert my changes at a moment's notice."

The primary anti-pattern when coding with AI is failing to commit frequently to version control. The ability to quickly drop context, revert changes, and start fresh becomes essential when working at this pace. Getting important decisions into documentation files and code into version control enables rapid experimentation without fear of losing work.

Other challenges include knowing when to focus on the right risks. The team had to navigate competing priorities—customers wanted certain UX features, but the team identified data collection and storage as the critical unknown risk that needed solving first. This required diplomatic firmness in prioritizing work based on technical risk assessment rather than just user requests.

Essential Tools for AI-Assisted Development

"If you are using AI by going to a website, that is not what we are talking about here."

To work effectively with AI, developers need agentic tools that can interact with files and run programs, not just chat interfaces. Recommended tools include:

Most developers working at this level have disabled safety guards, allowing AI to run programs without asking permission each time. While this carries risks, committing frequently to version control provides the safety net needed for rapid experimentation.

The Power of Voice Interaction

"Most of the time coding now looks like I'm talking. It's almost like Star Trek—you're talking to the computer and then code shows up."

Using voice transcription tools like Super Whisper transformed the development experience. Speaking instead of typing not only increased speed but also changed the nature of communication with AI. When speaking, developers naturally provide more context and explanation than when typing, leading to better results from AI systems.

This proved especially valuable in a crowded conference room where Super Whisper could filter out background noise and accurately transcribe the speakers' voices. The tool enabled natural, conversational interaction with development tools.

Balancing Speed with Safety

Over three days, the team released 61 times without comprehensive automated testing, focusing instead on validating user value through manual testing with the actual customer. However, after the hackathon, Llewellyn added automated testing by creating a test plan document through voice dictation, having AI clean it up and expand it, then generating Puppeteer tests and shell scripts to run them—all in about 40 minutes.

This demonstrates a pragmatic approach: when exploring and validating with users, manual testing may suffice; but for ongoing maintenance and confidence, automated tests remain valuable and can be generated efficiently with AI assistance.

The Future of Software Development

"If you want to make something, there could not be a better time than now."

The skills required for effective software development are shifting. Understanding how to assess risk, knowing when to commit code, maintaining good engineering practices, and finding creative solutions within system constraints remain critical. What's changing is that these skills are now applied at a higher level of abstraction, with AI handling much of the detailed implementation.

The space is evolving rapidly—practices that work today may need adjustment in months. Developers need to continuously experiment, stay current with new tools and models, and develop instincts for working effectively with AI systems. The fundamentals of agile development—rapid iteration, customer feedback, risk assessment, and incremental delivery—matter more than ever.

About Llewellyn Falco

Llewellyn is an Agile and XP (Extreme Programming) expert with over two decades of experience in Java, OO design, and technical practices like TDD, refactoring, and continuous delivery. He specializes in coaching, teaching, and transforming legacy code through clean code, pair programming, and mob programming.

You can link with Llewellyn Falco on LinkedIn.

Jaksot(200)

The Triangulation Technique—Coaching Agile Teams Through Challenges | Bernie Maloney

The Triangulation Technique—Coaching Agile Teams Through Challenges | Bernie Maloney

Bernie Maloney: The Triangulation Technique—Coaching Agile Teams Through Challenges 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. Bernie identifies critical patterns that cause teams to self-destruct, with lack of clarity about intention being the most common culprit. When teams are treated as mere "task workers" without clear vision, strategy, or goals, they become depressed and directionless. Some teams seek forgiveness after failed experiments, while others get stuck seeking permission without taking enough self-leadership. Bernie emphasizes that waiting for direction is fundamentally self-destructive behavior, and Scrum Masters must create safety for teams to reach high performance. He introduces the coaching technique of triangulation, where problems become a third point that coach and coachee examine together, side by side, rather than facing each other in opposition. In this segment, we talk about "What the Duck", a Lego Serious Play workshop. Featured Book of the Week: Start with Why by Simon Sinek Bernie champions "Start with Why" by Simon Sinek as essential reading for Scrum Masters working to transform team culture. He explains that compelling stories are how leaders truly influence others, following the sequence of Attention-Emotion-Reason. This book helps Scrum Masters understand that their job fundamentally involves changing culture, and leaders must demonstrate the change they want to see. Bernie connects this to the broader leadership challenge of developing coaching and mentoring skills within organizational structures. During this segment, we also refer to the following books: Drive, By Dan Pink Change the Culture, Change the Game, by Connors et al. The Secret Language of Leadership, by Denning Too Many Bosses, Too Few Leaders, by Peshawaria The Geek Way, by McAfee Right Kind of Wrong, by Edmondson Self-reflection Question: What patterns of self-destructive behavior might your teams be exhibiting, and how could you help them move from seeking permission to taking ownership? [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 Bernie Maloney Bernie Maloney has helped teams grow businesses to beyond $4B / year, delivering products from consumer electronics to network infrastructure to services & payments. He helps clients achieve performance breakthroughs with their teams, organizations and themselves, and believes that leads both to outrageous effectiveness, and a whole lot more fun. You can link with Bernie Maloney on LinkedIn, and visit Bernie's website and YouTube Channel.

9 Syys 16min

The Power of Psychological Safety in Agile Teams | Bernie Maloney

The Power of Psychological Safety in Agile Teams | Bernie Maloney

Bernie Maloney: The Power of Psychological Safety 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. Bernie shares a powerful story about learning what psychological safety truly means through both success and failure. Working in a high-pressure division with tight timelines and margins, Bernie discovered the transformative power of the mantra "always make a new mistake." When he made a significant error and was met with understanding rather than punishment, he experienced firsthand how psychological safety enables teams to thrive. Later, facing a different challenge where mistrust existed between management and teams, Bernie had to navigate the delicate balance of maintaining psychological safety while addressing management's desire for transparency. His solution was innovative: conduct retrospectives with the team first, then invite managers in at the end with anonymized contributions. Bernie's approach of framing changes as experiments helped people embrace newness, knowing it would be time-bound and reversible. In this episode we refer to Neuro-linguistic Programming (NLP). Self-reflection Question: How might your current approach to mistakes and experimentation be either fostering or undermining psychological safety within your 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 Bernie Maloney Bernie Maloney has helped teams grow businesses to beyond $4B / year, delivering products from consumer electronics to network infrastructure to services & payments. He helps clients achieve performance breakthroughs with their teams, organizations and themselves, and believes that leads both to outrageous effectiveness, and a whole lot more fun. You can link with Bernie Maloney on LinkedIn, and visit Bernie's website and YouTube Channel.

8 Syys 16min

CTO Series: Scaling Engineering Teams and Aligning Tech with Business Goals With Toni Sallanmaa

CTO Series: Scaling Engineering Teams and Aligning Tech with Business Goals With Toni Sallanmaa

CTO Series: Toni Sallanmaa on Scaling Engineering Teams and Aligning Tech with Business Goals In this BONUS episode, we explore the journey of scaling technology teams and maintaining alignment between engineering and business objectives with Toni Sallanmaa, CTO at Funidata. Toni shares invaluable insights from leading the development of Sisu, a cutting-edge student information system serving over 100,000 Finnish university users, and discusses practical strategies for growing engineering organizations while preserving company culture. The Genesis of Leadership in Technology "I understood what I was really responsible for. I'm interested in the business we are running—the business adds meaning to the work." Toni's approach to technology leadership was fundamentally shaped by a pivotal moment early in his career when he first gained influence over system development and technology choices. After working with large-scale systems for 20 years, this moment of responsibility revelation transformed his perspective from purely technical to business-focused. He emphasizes that infinite curiosity drives success in tech businesses, and understanding the business context gives meaningful purpose to technical work. Bridging the Gap Between Tech and Product "Don't separate Tech from Product. We established a common language between product and technology people." One of Toni's most significant insights centers on eliminating the traditional divide between technology and product teams. As Funidata grew from a small startup to a 70-person organization, the challenges of maintaining alignment became apparent. Their solution involved several key practices: Teaching developers the language of the product domain Banning confusing technical terms that create communication barriers Workshopping product language to ensure clarity Keeping entity names deliberately vague until true understanding emerges This approach draws heavily from Domain Driven Design principles, creating a unified vocabulary that enables seamless collaboration. Collaborative Planning and Transparency "We use transparency as a collaboration technique. Every team sees what's being proposed as a goal for the next quarter." Funidata implements a unique "marketplace of goals" approach during their quarterly big room planning sessions. Rather than using scaled agile frameworks, they focus on transparency and collaborative goal-setting. Teams present their high-level quarterly plans to each other, creating visibility across the organization. Product owners are embedded within teams, keeping communication distances short and ensuring alignment between technical execution and business objectives. Future-Forward Roadmapping "We talk about the higher level ideas regularly, but let them bubble up from the community. We hold internal hackathons." Toni's approach to roadmapping balances strategic vision with grassroots innovation. They maintain an internal technology roadmap that addresses emerging trends like AI, while allowing ideas to organically emerge from the engineering community. Internal hackathons serve as catalysts for innovation, providing structured opportunities for teams to explore new technologies and approaches that might inform future roadmap decisions. Scaling Challenges and Cultural Preservation "The biggest challenge is not technology, it was the rapid scaling of technology teams. When you scale up, keep the culture in mind." The most significant challenge Toni faced wasn't technical but organizational—rapidly scaling teams while preserving company culture. Growing from 10 to 50 people required evolving processes, from establishing internal forums for architectural discussions to implementing continuous integration flows. The key was identifying pain points proactively and maintaining open discussions with team members throughout the scaling process. Strengthening company culture became essential to successful growth. AI's Impact on Software Development "Productivity is on the rise. We see opportunities like generating test data, but we have strict requirements for cybersecurity, which puts pressure on code quality." Toni views AI's impact on software development with cautious optimism. While productivity gains are evident, particularly in areas like test data generation, the stringent cybersecurity requirements in their domain mean that AI hasn't yet significantly improved code quality where it matters most. The technology shows promise, but implementation must be carefully considered within the context of security and quality requirements. Measuring Engineering Success "We use DORA and SPACE framework. We measure how much of our work is KTLO (Keep The Lights On) and how much is elective development." Funidata employs both DORA and SPACE frameworks to measure engineering organization success. From SPACE, they particularly focus on measuring software team wellbeing, while also tracking the balance between "Keep The Lights On" (KTLO) work and elective development. Using JIRA connected to a data warehouse, they mine extensive data that serves both leadership decision-making and team improvement efforts, ensuring metrics benefit everyone in the organization. Influential Leadership Resources "The organizational books have been more influential to me than purely technical ones." Toni emphasizes that organizational leadership books have shaped his CTO approach more than technical resources. Two key influences stand out: "Team Topologies" for understanding how to structure and scale engineering teams effectively, and "Radical Candor" for building authentic, productive relationships within the organization. You can find a BONUS episode on Team Topologies with the authors Matthew Skeltton and Manuel Pais. About Toni Sallanmaa Toni leads technology and engineering at Funidata, developing Sisu—a cutting-edge student information system serving over 100,000 Finnish university users. Passionate about agile methodologies, system architecture, and software engineering, Toni specializes in technology management, software lifecycle, OOP, and relational databases to deliver innovative, scalable solutions in higher education tech. You can connect with Toni Sallanmaa on LinkedIn.

6 Syys 40min

The Visionary vs The Micromanager - Two Product Owner Extremes | Mariano

The Visionary vs The Micromanager - Two Product Owner Extremes | Mariano

Mariano Gontchar: The Micromanagement Trap—When PO's Good Intentions Harm Agile Team Performance 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 Visionary Leader During an agile transformation project modernizing a build system with multiple stakeholders, Mariano worked with an exceptional Product Owner who demonstrated the power of clear vision and well-defined roadmaps. This visionary Product Owner successfully navigated complex stakeholder relationships by maintaining focus on the product vision while providing clear direction through structured roadmap planning, enabling the team to deliver meaningful results in a challenging environment. The Bad Product Owner: The Task-Manager Micromanager Mariano encountered a well-intentioned Product Owner who fell into the task-manager anti-pattern, becoming overly detail-oriented and controlling. This Product Owner provided extremely detailed story descriptions and even specified who should do what tasks instead of explaining why work was needed. This approach turned the team into mere task-handlers with no space to contribute their expertise, ultimately reducing both engagement and effectiveness despite the Product Owner's good intentions. Self-reflection Question: Are you empowering your team to contribute their expertise, or are you inadvertently turning them into task-handlers through over-specification? [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 Mariano Gontchar Mariano is a Madrid-based Scrum Master with a unique multi-perspective journey through Agile roles. Having evolved from developer to Product Owner, Project Manager, and now Scrum Master, he brings comprehensive insights to team facilitation and backlog management. Mariano specializes in practical Agile adoption strategies that work in real-world environments. You can link with Mariano Gontchar on LinkedIn.

5 Syys 14min

Fear-Free Teams—Creating Psychological Safety for High Performance | Mariano Gontcher

Fear-Free Teams—Creating Psychological Safety for High Performance | Mariano Gontcher

Mariano Gontchar: Fear-Free Teams—Creating Psychological Safety for High Performance 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. Mariano's definition of Scrum Master success has evolved dramatically from his early days of focusing on "deliver on time and budget" to a more sophisticated understanding centered on team independence and psychological safety. Today, he measures success by whether teams can self-manage, communicate effectively with stakeholders, and operate without fear of criticism. This shift represents a fundamental change from output-focused metrics to outcome-focused team health indicators that create sustainable high performance. Self-reflection Question: How has your definition of success evolved in your current role, and what would change if you focused on team independence rather than traditional delivery metrics? Featured Retrospective Format for the Week: Frustration-Based Retrospective Mariano's retrospective approach focuses on asking team members about their biggest frustrations from the last sprint. This format helps team members realize their frustrations aren't unique and creates psychological safety for sharing challenges. The key is always asking the team to propose solutions themselves rather than imposing fixes, making retrospectives about genuine continuous improvement rather than just complaining sessions. [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 Mariano Gontchar Mariano is a Madrid-based Scrum Master with a unique multi-perspective journey through Agile roles. Having evolved from developer to Product Owner, Project Manager, and now Scrum Master, he brings comprehensive insights to team facilitation and backlog management. Mariano specializes in practical Agile adoption strategies that work in real-world environments. You can link with Mariano Gontchar on LinkedIn.

4 Syys 14min

From Evangelist to Facilitator—How To Lead A Successful Company Merger | Mariano Gontchar

From Evangelist to Facilitator—How To Lead A Successful Company Merger | Mariano Gontchar

Mariano Gontchar: From Evangelist to Facilitator—How To Lead A Successful Company Merger 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. During a complex merger between two telecom companies, Mariano faced the challenge of uniting team members with different cultures, practices, and tools. His initial approach of selling Agile theory instead of focusing on benefits failed because he forgot about the "why" of change. The breakthrough came when he shifted from being an Agile evangelist to becoming a facilitator who listened to managers' real challenges. By connecting people and letting the team present their own solutions to leadership, Mariano successfully created unity between the formerly divided groups. Self-reflection Question: Are you trying to sell your methodology or solve real problems, and what would happen if you focused on understanding challenges before proposing solutions? [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 Mariano Gontchar Mariano is a Madrid-based Scrum Master with a unique multi-perspective journey through Agile roles. Having evolved from developer to Product Owner, Project Manager, and now Scrum Master, he brings comprehensive insights to team facilitation and backlog management. Mariano specializes in practical Agile adoption strategies that work in real-world environments. You can link with Mariano Gontchar on LinkedIn.

3 Syys 12min

Breaking Down The Clan Mentality In Agile Teams | Mariano Gontchar

Breaking Down The Clan Mentality In Agile Teams | Mariano Gontchar

Mariano Gontchar: Breaking Down The Clan Mentality 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. Mariano encountered a competent team that was sabotaging itself through internal divisions and lack of trust. The team had formed clans that didn't trust each other, creating blind spots even during retrospectives. Rather than simply telling the team what was wrong, Mariano created an anonymous fear-based retrospective that revealed the root cause: a Product Owner who behaved like a boss and evaluated team members, creating a culture of fear. His approach demonstrates the power of empowering teams to discover and solve their own problems rather than imposing solutions from above. Self-reflection Question: What fears might be hiding beneath the surface of your team's dynamics, and how could you create a safe space for them to emerge? Featured Book of the Week: Turn the Ship Around! by David Marquet Mariano recommends "Turn the Ship Around!" by David Marquet (we have an episode with David Marquet talking about this book, check it here). Mariano highlights the fascinating story and introduction to the leader-leader model, which differs significantly from the traditional leader-follower approach. This book resonates with Mariano's journey from directive leadership to facilitative leadership, showing how empowering others rather than commanding them creates more effective and engaged teams. [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 Mariano Gontchar Mariano is a Madrid-based Scrum Master with a unique multi-perspective journey through Agile roles. Having evolved from developer to Product Owner, Project Manager, and now Scrum Master, he brings comprehensive insights to team facilitation and backlog management. Mariano specializes in practical Agile adoption strategies that work in real-world environments. You can link with Mariano Gontchar on LinkedIn.

2 Syys 17min

From Boss to Facilitator—The Critical Role of Empathy in Scrum Mastery | Mariano Gontchar

From Boss to Facilitator—The Critical Role of Empathy in Scrum Mastery | Mariano Gontchar

Mariano Gontchar: From Boss to Facilitator—The Critical Role of Empathy in Scrum Mastery 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. Mariano shares his transformation from viewing himself as a boss in his project manager role to embracing the facilitator mindset essential for Scrum Masters. His journey reveals a crucial insight: you cannot implement Scrum with a "big bang" approach. Instead, success comes through empathy and understanding your team's needs. Mariano emphasizes that working with Agile requires constant practice and learning, but the key lesson that changed everything for him was learning to empathize with his team members rather than directing them from above. Self-reflection Question: How might your current leadership style be limiting your team's potential, and what would change if you shifted from directing to facilitating? [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 Mariano Gontchar Mariano is a Madrid-based Scrum Master with a unique multi-perspective journey through Agile roles. Having evolved from developer to Product Owner, Project Manager, and now Scrum Master, he brings comprehensive insights to team facilitation and backlog management. Mariano specializes in practical Agile adoption strategies that work in real-world environments. You can link with Mariano Gontchar on LinkedIn.

1 Syys 14min

Suosittua kategoriassa Politiikka ja uutiset

rss-ootsa-kuullut-tasta
aikalisa
tervo-halme
ootsa-kuullut-tasta-2
politiikan-puskaradio
viisupodi
et-sa-noin-voi-sanoo-esittaa
rss-vaalirankkurit-podcast
rss-podme-livebox
aihe
otetaan-yhdet
linda-maria
rss-polikulaari-humanisti-vastaa-ja-muut-ts-podcastit
rss-hyvaa-huomenta-bryssel
the-ulkopolitist
radio-antro
rss-valiokunta
rss-kaikki-paskaksi-ystavat
rss-terevisio
rss-tasta-on-kyse-ivan-puopolo-verkkouutiset