AI Assisted Coding: Transactional AI Development - Commit, Validate, and Rollback With Sergey Sergyenko

AI Assisted Coding: Transactional AI Development - Commit, Validate, and Rollback With Sergey Sergyenko

AI Assisted Coding: Treating AI Like a Junior Engineer - Onboarding Practices for AI Collaboration

In this special episode, Sergey Sergyenko, CEO of Cybergizer, shares his practical framework for AI-assisted development built on transactional models, Git workflows, and architectural conventions. He explains why treating AI like a junior engineer, keeping commits atomic, and maintaining rollback strategies creates production-ready code rather than just prototypes.

Vibecoding: An Automation Design Instrument

"I would define Vibecoding as an automation design instrument. It's not a tool that can deliver end-to-end solution, but it's like a perfect set of helping hands for a person who knows what they need to do."

Sergey positions vibecoding clearly: it's not magic, it's an automation design tool. The person using it must know what they need to accomplish—AI provides the helping hands to execute that vision faster. This framing sets expectations appropriately: AI speeds up development significantly, but it's not a silver bullet that works without guidance. The more you practice vibecoding, the better you understand its boundaries. Sergey's definition places vibecoding in the evolution of development tools: from scaffolding to co-pilots to agentic coding to vibecoding. Each step increases automation, but the human architect remains essential for providing direction, context, and validation.

Pair Programming with the Machine

"If you treat AI as a junior engineer, it's very easy to adopt it. Ah, okay, maybe we just use the old traditions, how we onboard juniors to the team, and let AI follow this step."

One of Sergey's most practical insights is treating AI like a junior engineer joining your team. This mental model immediately clarifies roles and expectations. You wouldn't let a junior architect your system or write all your tests—so why let AI? Instead, apply existing onboarding practices: pair programming, code reviews, test-driven development, architectural guidance. This approach leverages Extreme Programming practices that have worked for decades. The junior engineer analogy helps teams understand that AI needs mentorship, clear requirements, and frequent validation. Just as you'd provide a junior with frameworks and conventions to follow, you constrain AI with established architectural patterns and framework conventions like Ruby on Rails.

The Transactional Model: Atomic Commits and Rollback

"When you're working with AI, the more atomic commits it delivers, more easy for you to kind of guide and navigate it through the process of development."

Sergey's transactional approach transforms how developers work with AI. Instead of iterating endlessly when something goes wrong, commit frequently with atomic changes, then rollback and restart if validation fails. Each commit should be small, independent, and complete—like a feature flag you can toggle. The commit message includes the prompt sequence used to generate the code and rollback instructions.

This approach makes the Git repository the context manager, not just the AI's memory. When you need to guide AI, you can reference specific commits and their context. This mirrors trunk-based development practices where teams commit directly to master with small, verified changes. The cost of rollback stays minimal because changes are atomic, making this strategy far more efficient than trying to fix broken implementations through iteration.

Context Management: The Weak Point and the Solution

"Managing context and keeping context is one of the weak points of today's coding agents, therefore we need to be very mindful in how we manage that context for the agent."

Context management challenges current AI coding tools—they forget, lose thread, or misinterpret requirements over long sessions. Sergey's solution is embedding context within the commit history itself. Each commit links back to the specific reasoning behind that code: why it was accepted, what iterations it took, and how to undo it if needed. This creates a persistent context trail that survives beyond individual AI sessions. When starting new features, developers can reference previous commits and their context to guide the AI. The transactional model doesn't just provide rollback capability—it creates institutional memory that makes AI progressively more effective as the codebase grows.

TDD 2.0: Humans Write Tests, AI Writes Code

"I would never allow AI to write the test. I would do it by myself. Still, it can write the code."

Sergey is adamant about roles: humans write tests, AI writes implementation code. This inverts traditional TDD slightly—instead of developers writing tests then code, they write tests and AI writes the code to pass them. Tests become executable requirements and prompts. This provides essential guardrails: AI can iterate on implementation until tests pass, but it can't redefine what "passing" means. The tests represent domain knowledge, business requirements, and validation criteria that only humans should control. Sergey envisions multi-agent systems where one agent writes code while another validates with tests, but critically, humans author the original test suite. This TDD 2.0 framework (a talk Sergey gave at the Global Agile Summit) creates a verification mechanism that prevents the biggest anti-pattern: coding without proper validation.

The Two Cardinal Rules: Architecture and Verification

"I would never allow AI to invent architecture. Writing AI agentic coding, Vibecoding, whatever coding—without proper verification and properly setting expectations of what you want to get as a result—that's the main mistake."

Sergey identifies two non-negotiables. First, never let AI invent architecture. Use framework conventions (Rails, etc.) to constrain AI's choices. Leverage existing code generators and scaffolding. Provide explicit architectural guidelines in planning steps. Store iteration-specific instructions where AI can reference them. The framework becomes the guardrails that prevent AI from making structural decisions it's not equipped to make. Second, always verify AI output. Even if you don't want to look at code, you must validate that it meets requirements. This might be through tests, manual review, or automated checks—but skipping verification is the fundamental mistake. These two rules—human-defined architecture and mandatory verification—separate successful AI-assisted development from technical debt generation.

Prototype vs. Production: Two Different Workflows

"When you pair as an architect or a really senior engineer who can implement it by himself, but just wants to save time, you do the pair programming with AI, and the AI kind of ships a draft, and rapid prototype."

Sergey distinguishes clearly between prototype and production development. For MVPs and rapid prototypes, a senior architect pairs with AI to create drafts quickly—this is where speed matters most. For production code, teams add more iterative testing and polishing after AI generates initial implementation. The key is being explicit about which mode you're in. The biggest anti-pattern is treating prototype code as production-ready without the necessary validation and hardening steps. When building production systems, Sergey applies the full transactional model: atomic commits, comprehensive tests, architectural constraints, and rollback strategies. For prototypes, speed takes priority, but the architectural knowledge still comes from humans, not AI.

The Future: AI Literacy as Mandatory

"Being a software engineer and trying to get a new job, it's gonna be a mandatory requirement for you to understand how to use AI for coding. So it's not enough to just be a good engineer."

Sergey sees AI-assisted coding literacy becoming as fundamental as Git proficiency. Future engineering jobs will require demonstrating effective AI collaboration, not just traditional coding skills. We're reaching good performance levels with AI models—now the challenge is learning to use them efficiently. This means frameworks and standardized patterns for AI-assisted development will emerge and consolidate. Approaches like AAID, SpecKit, and others represent early attempts to create these patterns. Sergey expects architectural patterns for AI-assisted development to standardize, similar to how design patterns emerged in object-oriented programming. The human remains the bottleneck—for domain knowledge, business requirements, and architectural guidance—but the implementation mechanics shift heavily toward AI collaboration.

Resources for Practitioners

"We are reaching a good performance level of AI models, and now we need to guide it to make it impactful. It's a great tool, now we need to understand how to make it impactful."

Sergey recommends Obie Fernandez's work on "Patterns of Application Development Using AI," particularly valuable for Ruby and Rails developers but applicable broadly. He references Andrey Karpathy's original vibecoding post and emphasizes Extreme Programming practices as foundational. The tools he uses—Cursor and Claude Code—support custom planning steps and context management. But more important than tools is the mindset: we have powerful AI capabilities now, and the focus must shift to efficient usage patterns. This means experimenting with workflows, documenting what works, and sharing patterns with the community. Sergey himself shares case studies on LinkedIn and travels extensively speaking about these approaches, contributing to the collective learning happening in real-time.

About Sergey Sergyenko

Sergey is the CEO of Cybergizer, a dynamic software development agency with offices in Vilnius, Lithuania. Specializing in MVPs with zero cash requirements, Cybergizer offers top-tier CTO services and startup teams. Their tech stack includes Ruby, Rails, Elixir, and ReactJS.

Sergey was also a featured speaker at the Global Agile Summit, and you can find his talk available in your membership area. If you are not a member don't worry, you can get the 1-month trial and watch the whole conference. You can cancel at any time.

You can link with Sergey Sergyenko on LinkedIn.

Avsnitt(200)

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

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

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

27 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

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

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

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

19 Juni 18min

Populärt inom Politik & nyheter

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