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 Risk-Aware Scrum Master: Preventing Problems Before They Happen | Irene Castagnotto

The Risk-Aware Scrum Master: Preventing Problems Before They Happen | Irene Castagnotto

Irene Castagnotto: The Risk-Aware Scrum Master: Preventing Problems Before They Happen 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. Irene defines success for Scrum Masters as helping teams anticipate and manage risks before they become unexpected problems. She focuses on ensuring teams don't face surprise risks during sprints and don't start work with missing requirements. Her approach includes using user story mapping with Product Owners to visualize potential risks and maintaining team happiness as a key success indicator. For Irene, creating a positive team environment is a crucial deliverable that Scrum Masters must actively work on. She emphasizes the importance of listening to team feedback and regularly assessing whether the team feels supported and engaged. In this segment, we refer to W. Edwards Deming, and his famous quote "a bad system will beat a good person, every time!" Featured Retrospective Format for the Week: The Good/Bad/Risk Retrospective This retrospective format works particularly well with younger teams and uses humor to help teams discuss emotionally challenging topics. The format focuses on three key areas: what went well (Good), what didn't work (Bad), and what potential risks the team sees ahead (Risk). Irene recommends this approach because it helps teams surface risks that aren't visible to anyone else, creating opportunities to address potential problems proactively. By incorporating the language of risk into everyday conversations, teams become more aware of potential challenges and can plan accordingly. The humor element helps reduce the emotional intensity that often accompanies difficult discussions about team performance and challenges. In this segment, we refer to the book "How to Make Good Things Happen: Know Your Brain, Enhance Your Life" by Marian Rojas Estape. Self-reflection Question: How comfortable is your team with discussing risks openly, and what techniques could you use to make these conversations more approachable? [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 Irene Castagnotto Irene, a Gen Z Italian Scrum Master, began her Agile journey at a young age. With a positive and passionate approach, she aims to help her generation navigate the world of work with confidence and serenity, while supporting teams in unlocking their full potential. You can link with Irene Castagnotto on LinkedIn.

21 Elo 17min

Timing Is Everything - Learning When Agile Teams Are Ready for Change | Irene Castagnotto

Timing Is Everything - Learning When Agile Teams Are Ready for Change | Irene Castagnotto

Irene Castagnotto: Timing Is Everything - Learning When Agile Teams Are Ready for Change 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. Irene shares a powerful story about discovering team dependencies and proposing solutions that management initially rejected. When her team identified that Epics weren't organized to avoid dependencies between teams, they proposed using a single unified backlog to manage these challenges. Despite the logical solution, management wasn't ready to accept it. A month later, the same management team returned with the identical proposal. This experience taught Irene that timing is crucial in change management—you don't decide when the right time is; the people involved determine their own readiness. She emphasizes the importance of socializing changes early and often, collecting feedback before proposing major transformations, especially when those changes affect management structures. Self-reflection Question: How do you balance persistence with patience when you know a change is needed but the organization isn't ready to embrace it? [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 Irene Castagnotto Irene, a Gen Z Italian Scrum Master, began her Agile journey at a young age. With a positive and passionate approach, she aims to help her generation navigate the world of work with confidence and serenity, while supporting teams in unlocking their full potential. You can link with Irene Castagnotto on LinkedIn.

20 Elo 12min

Three Toxic Conditions That Destroy Agile Team Effectiveness | Irene Castagnotto

Three Toxic Conditions That Destroy Agile Team Effectiveness | Irene Castagnotto

Irene Castagnotto: Three Toxic Conditions That Destroy Agile Team Effectiveness 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. Irene encountered a team where everything appeared perfect on the surface, but underneath lay a complete lack of transparency. The team displayed negativity while their manager prevented them from taking responsibility, asking them to complete tasks without explaining the reasoning. These three toxic conditions—negativity, lack of transparency, and micromanagement—combined to destroy the team's effectiveness. Initially hesitant to speak up, Irene ultimately chose to leave. Reflecting on this experience, she emphasizes the importance of addressing problems directly with leadership rather than simply escaping the situation. In this segment, we refer to the 5 monkeys experiment, as comment on conditioning that happens in groups. Featured Book of the Week: Switch by the Heath Brothers Switch: How to Change Things When Change Is Hard by the Heath Brothers focuses on understanding change and why it's challenging for people. According to Irene, change isn't difficult because people resist it, but because it creates internal conflict within us. The Heath Brothers explain the three essential elements needed for successful change: the rational rider (logical thinking), the emotional elephant (feelings and motivation), and the path (the environment and systems). The book provides practical guidance on how to facilitate change and help people navigate transitions effectively, emphasizing the importance of celebrating achievements throughout the change process. Self-reflection Question: What internal conflicts might be preventing positive changes in your team, and how can you address both the rational and emotional aspects of resistance? [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 Irene Castagnotto Irene, a Gen Z Italian Scrum Master, began her Agile journey at a young age. With a positive and passionate approach, she aims to help her generation navigate the world of work with confidence and serenity, while supporting teams in unlocking their full potential. You can link with Irene Castagnotto on LinkedIn.

19 Elo 16min

When Proactive Help Backfires - A Gen Z Scrum Master's Learning Journey | Irene Castagnotto

When Proactive Help Backfires - A Gen Z Scrum Master's Learning Journey | Irene Castagnotto

Irene Castagnotto: When Proactive Help Backfires - A Gen Z Scrum Master's Learning Journey 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. Irene shares a valuable lesson about the pitfalls of being overly proactive without proper communication. As a new Scrum Master, she observed Product Owners struggling with role changes and took initiative to help them understand and implement changes. However, she discovered that her well-intentioned proposals weren't aligned with what the POs actually wanted. The key insight: when people don't speak up during your proposals, it often means they're not on board but are avoiding conflict. Irene learned that asking questions and letting others express what changes they're ready for is far more effective than assuming what help is needed. Self-reflection Question: How can you better gauge whether your team is genuinely on board with your suggestions, especially when they remain silent during discussions? [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 Irene Castagnotto Irene, a Gen Z Italian Scrum Master, began her Agile journey at a young age. With a positive and passionate approach, she aims to help her generation navigate the world of work with confidence and serenity, while supporting teams in unlocking their full potential. You can link with Irene Castagnotto on LinkedIn.

18 Elo 15min

BONUS The Management Revolution Transforming Company Culture and Employee Engagement | Rob Gallaher

BONUS The Management Revolution Transforming Company Culture and Employee Engagement | Rob Gallaher

BONUS: Rob Gallaher Reveals The Management Revolution Transforming Company Culture and Employee Engagement In this BONUS episode, we dive deep into the transformative power of profit sharing with Rob Gallaher, CEO of Gallaher Co. Rob shares his journey from an overworked entrepreneur sacrificing family time to building a thriving business model that aligns employee success with company growth. Through practical insights and hard-learned lessons, we explore how monthly profit sharing can revolutionize workplace dynamics and create genuine shared success. The Genesis of a Profit Sharing Revolution "I was an entrepreneur, working long hours and sacrificing family time. I realized my situation in life was not so good anymore, and even my health was suffering." Rob Gallaher's journey to profit sharing began with a personal crisis. As a successful entrepreneur, he found himself trapped in the classic founder's dilemma - working endless hours while his health and family relationships suffered. This realization prompted him to seek alternative business models from other successful owners. His discovery of profit sharing wasn't immediate magic, but rather a methodical approach to solving the fundamental disconnect between business success and employee engagement. Since implementing it in 2015, Rob has refined his approach through real-world application, leading him to document his learnings in his book after others began noticing the remarkable success of his companies. Defining True Profit Sharing "Take the company's financial success and share it with individuals that make it happen. The main thing: it must be monthly." Rob's definition of profit sharing goes beyond traditional annual bonuses or stock options. His approach centers on taking actual company profits and distributing them to the people who directly contribute to generating those profits. The cornerstone of his system is monthly distribution, recognizing that people manage their personal finances on a monthly basis, not quarterly or annually. This frequency ensures that profit sharing becomes integrated into employees' monthly budgets and thinking patterns, creating immediate behavioral impact rather than distant, abstract benefits. The Power of Immediate Impact "No one manages quarterly their personal life. The profit sharing needs to adapt to that monthly reality. If we don't affect people's monthly budget we don't affect how they think." The monthly frequency of Rob's profit sharing system creates tangible, immediate impact on employees' financial lives. Unlike equity or long-term bonuses that feel distant and uncertain, monthly profit sharing becomes part of employees' regular financial planning. This immediacy changes how people approach their work, leading them to ask "what can I do to get it" and investing more personally in company success. Rob emphasizes making the amounts substantial - recommending four-digit numbers that genuinely affect people's monthly reality rather than token gestures that get lost in regular paychecks. Rethinking Performance Management "I don't like the word 'review'. I prefer the word 'reflection', we do it every 6 months. I wanted to change the tone and what was happening in those meetings." Traditional performance reviews create antagonistic dynamics where employees feel anxious and stressed, often leading to negotiations that feel like battles. Rob has completely reimagined this process by separating profit sharing from performance evaluations and changing the language from "reviews" to "reflections." This shift eliminates the transactional nature of traditional reviews where employees feel they must fight for raises and promotions. Instead, profit sharing operates independently of individual performance metrics, creating a more collaborative and less stressful environment for genuine performance discussions. Strategic Implementation Framework "You need a business that makes a profit, you need to have accurate accounting, and you need to be a leader - you need to have the respect and trust of your leadership." Rob outlines three fundamental prerequisites for successful profit sharing implementation. First, the business must be genuinely profitable - you cannot share what doesn't exist. Second, accurate accounting systems are essential to track and calculate profits transparently. Third, leadership credibility is crucial because profit sharing requires employees to trust that leaders will follow through on commitments. Rob recommends starting with a flat rate and minimum amount, such as $1,000, and focusing on decision-makers who directly affect company profitability rather than attempting to include every employee from the start. Targeting Decision Makers "Who are the people who make decisions that affect the profit of your business? Share the profit with the decision makers that affect profit." Rather than implementing company-wide profit sharing immediately, Rob advocates for a targeted approach focusing on employees who make decisions directly impacting profitability. This strategic selection ensures that profit sharing reaches the people whose daily choices most influence company success. By identifying and rewarding these key decision-makers first, companies can create a focused impact that generates measurable results before expanding the program to additional team members. Getting Started: First Steps for Implementation "Figure out your average profit." For companies interested in profit sharing but unsure where to begin, Rob recommends starting with fundamental financial analysis. Understanding average monthly profits provides the baseline for determining sustainable sharing amounts. This analysis helps leaders set realistic expectations and design a program that won't compromise business stability while still providing meaningful benefits to employees. The key is ensuring that profit sharing enhances rather than threatens the company's financial foundation. About Rob Gallaher Rob Gallaher, CEO of Gallaher Co., leads five companies across industries. Since founding his construction firm in 2010, he's championed profit sharing as a catalyst for growth. His book, Profit Sharing: The Power of Shared Success, and upcoming course reflect his passion for aligning employee and company success. You can also learn more about Rob's Profit Sharing strategy with his online course at Profitx.co. You can link with Rob Gallaher on LinkedIn, and connect with Rob Gallaher on facebook.

16 Elo 45min

When Technical Expertise Becomes Product Owner Micro-Managements | Somya Mehra

When Technical Expertise Becomes Product Owner Micro-Managements | Somya Mehra

Somya Mehra: When Technical Expertise Becomes Product Owner Micro-Management 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 Clear Communicator and Dependency Master Somya worked with an exceptional Product Owner on a project with multiple team dependencies. This PO excelled at clear, direct communication with both stakeholders and the team. They were proactive in stakeholder communication and maintained strong focus on what was needed and why. Their backlog management was exemplary, creating proper epics with comprehensive information including dependencies, enabling the team to easily know who to contact. This approach led to a much more motivated team. The Bad Product Owner: The Technical Micro-Manager Somya encountered a technically strong Product Owner whose knowledge became a liability. While technical strength can be beneficial, this PO used their expertise to control the team, telling developers exactly what solutions to implement. Initially, developers accepted this direction, but it escalated to every feature and task. The developers became uncomfortable voicing their perspectives, creating an unhealthy dynamic where the PO's technical knowledge stifled team autonomy and creativity. Self-reflection Question: How do you help Product Owners leverage their technical knowledge without falling into micro-management patterns? [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 Somya Mehra Somya is a Scrum Master at u-blox with nearly 7 years of IT experience across India and Finland. With experience in Waterfall and Agile models, she leads with empathy and a people-first approach. Somya is deeply interested in human behavior and understanding the motivations behind people's actions. You can link with Somya Mehra on LinkedIn.

15 Elo 16min

Why Collaboration Should Be Your Team's Primary Goal | Somya Mehra

Why Collaboration Should Be Your Team's Primary Goal | Somya Mehra

Somya Mehra: Why Collaboration Should Be Your Team's Primary Goal 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. Unlike technical roles where success is tangible, Scrum Master success can be harder to measure, especially for those transitioning from tech roles. Somya defines successful Scrum Master performance through team behaviors: when teams trust and respect each other, and when collaboration becomes their goal. She emphasizes the importance of observing behaviors and discussing them with team members early enough to foster the right behaviors within the team. Featured Retrospective Format for the Week: The 2 Pillars Retrospective Somya recommends the 2 Pillars retrospective format, which she intentionally varies to keep teams engaged and curious. Her core structure focuses on two essential questions: "What went well?" and "How can we improve?" She notices that using the same retrospective format repeatedly leads to team boredom, so she adds variety while maintaining these fundamental pillars. In specific cases, she includes a gratitude section to ensure team members feel appreciated. Self-reflection Question: How do you measure your success as a Scrum Master when the results aren't as tangible as in technical roles? [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 Somya Mehra Somya is a Scrum Master at u-blox with nearly 7 years of IT experience across India and Finland. With experience in Waterfall and Agile models, she leads with empathy and a people-first approach. Somya is deeply interested in human behavior and understanding the motivations behind people's actions. You can link with Somya Mehra on LinkedIn.

14 Elo 13min

From Top-Down to Collaborative—Reimagining Organizational Restructuring | Somya Mehra

From Top-Down to Collaborative—Reimagining Organizational Restructuring | Somya Mehra

Somya Mehra: From Top-Down to Collaborative—Reimagining Organizational Restructuring 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 business unit split and reorganization focused on creating smaller teams, Somya and her fellow Scrum Masters were invited to create the new structure process. After hearing feedback that teams felt excluded from previous changes, they decided to include teams in the reorganization process to give them a sense of control. They started by asking top management for constraints, then applied them to see what was possible. They facilitated workshops with Product Owners to divide the product portfolio and determine team assignments, ensuring people felt involved in the change process. Self-reflection Question: When leading organizational change, how do you balance the need for structure with giving teams meaningful input into decisions that affect them? [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 Somya Mehra Somya is a Scrum Master at u-blox with nearly 7 years of IT experience across India and Finland. With experience in Waterfall and Agile models, she leads with empathy and a people-first approach. Somya is deeply interested in human behavior and understanding the motivations behind people's actions. You can link with Somya Mehra on LinkedIn.

13 Elo 13min

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