Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches
Episode: BONUS Tom Gilb: Building True Engineering Culture and Delivering Value Through Evolutionary Methods
Host: Vasco Duarte
Release Date: May 27, 2025

Introduction

In this special bonus episode of the Scrum Master Toolbox Podcast, host Vasco Duarte engages in an enlightening conversation with Tom Gilb, a pioneering figure in the Agile movement. Gilb, an independent teacher, consultant, and prolific writer, delves deep into building a true engineering culture and delivering value through his evolutionary (EVO) methods.

Guest Background

Vasco introduces Tom Gilb as a veteran of Agile methodologies, noting his early contributions to the field even before the term "Agile" was coined. Gilb's seminal work includes the introduction of the term "evolutionary" in his 1976 book, Software Metrics. Over the decades, he has authored numerous books, with an impressive tally of ten published in the past year alone. Despite his semi-retired status, Gilb continues to influence the Agile community through his writings and consultations.

Defining Success in Projects

Tom Gilb emphasizes the importance of defining what success means in the context of project management. He critiques the prevalent focus on Agile practices themselves—like stand-up meetings and certifications—arguing that these do not inherently ensure project success. Instead, Gilb posits that success should be measured by the achievement of clear, multi-dimensional goals that deliver tangible value within budget and time constraints.

"Who cares if you're agile or not if your project is failing." – Tom Gilb [03:13]

Measuring Value and Multi-dimensional Objectives

Gilb introduces the concept of Quantified Multidimensional Objectives, which involves setting clear, measurable goals across various dimensions such as security, usability, and reliability—not just financial metrics. He argues that without quantifying these critical qualities, organizations cannot effectively assess or deliver value.

"Value can be profit and sales and market share. But for many stakeholders, like the user, it's the usability, it's the security." – Tom Gilb [05:38]

Critique of Current Agile Practices

The conversation highlights a significant gap in the current Agile practices: the lack of engineering discipline. Gilb criticizes the assumption that design and architecture can "magically emerge" within Agile frameworks like Scrum. He contends that without deliberate engineering and architectural planning, especially in large and complex projects, Agile methodologies are likely to fail.

"People don't get demanding state of the art qualities by accident. They have to fight hard and have knowledgeable designers and architects to get there." – Tom Gilb [08:23]

The EVO Method: Stakeholder Analysis and Requirements

Central to Gilb's approach is the EVO Method, which begins with a comprehensive stakeholder analysis. Unlike the conventional narrow view of stakeholders (e.g., only bosses or direct customers), Gilb expands this to include laws, regulations, contracts, and other non-human entities that impact project requirements.

"Stakeholders hold a stake. That means they have a requirement whether we like it or not, whether we know it or not." – Tom Gilb [21:25]

He underscores the necessity of quantifying stakeholder requirements to align project outcomes with actual value delivery, moving beyond vague promises to precise, measurable targets.

Design and Decomposition

After establishing stakeholder requirements, Gilb discusses the importance of robust design and the process of Decomposition. He advocates for breaking down large design goals into smaller, manageable increments that deliver immediate value. This approach not only facilitates early value delivery but also promotes continuous learning and adaptation.

"Can I deliver this design to my existing system to make it better no matter how bad the old existing system is? Can I do this next week?" – Tom Gilb [28:56]

Prioritization and Impact Estimation

Gilb introduces the concept of Prioritization through an Impact Estimation Table, which helps teams determine which tasks to tackle first based on their value-to-cost ratio. This method ensures that the most efficient designs—those offering the highest value at the lowest cost—are implemented first.

"The most important thing about that cycle is not merely that value is delivered early, frequently and measurably, it is that you learn early." – Tom Gilb [26:56]

Learning and Continuous Improvement

A critical aspect of Gilb's methodology is the emphasis on learning from each increment. By measuring the actual value delivered against expectations, teams can identify discrepancies and refine their approaches in real-time, fostering a culture of continuous improvement.

"The best competitors will be the ones that learn the fastest through this cycle." – Tom Gilb [36:48]

Integrating Lean Startup Principles

Gilb's EVO cycle mirrors the Build-Measure-Learn feedback loop advocated by Lean Startup. This alignment underscores the universality of iterative learning and value-driven development across different Agile frameworks.

"Tom, I really love how you built also the Lean Startup cycle into your EVO cycle. Because of course build, measure, learn is exactly the cycle that Lean Startup argues for." – Vasco Duarte [37:27]

Resources and Further Reading

Tom Gilb recommends his recent EVO book as a foundational resource, which includes extensive references and links to additional Agile literature. He also encourages listeners to explore his free materials available on platforms like LinkedIn and his personal website, tomgilb.com, for deeper insights.

Conclusion

The episode wraps up with Gilb sharing his enthusiasm for spreading his engineering-focused Agile methodologies. He highlights the importance of both technical and management leaders embracing engineering disciplines to ensure project success. Vasco reinforces the value of Gilb's insights, encouraging listeners to integrate these principles to build a true engineering culture within their organizations.

Key Takeaways:

1. Define Success Clearly: Success should be measured by achieving multi-dimensional, quantifiable goals that deliver real value.
2. Embrace Engineering Discipline: Robust design and architecture are essential, especially for large and complex projects.
3. Stakeholder-Centric Approach: Comprehensive stakeholder analysis ensures that all requirements, including non-human ones, are addressed.
4. Iterative Value Delivery: Breaking down projects into small, value-delivering increments fosters early success and continuous learning.
5. Prioritize Effectively: Use impact estimation to focus on the highest value tasks first.
6. Continuous Learning: Measure and learn from each increment to refine processes and improve outcomes.
7. Leverage AI and Modern Tools: Utilize AI for tasks like stakeholder analysis and decomposition to enhance efficiency and accuracy.

For those interested in delving deeper into Tom Gilb's methodologies, his EVO book and accompanying resources provide extensive guidance and practical examples.