The Founders Signatories of the Agile Manifesto
A Decade After Snowbird: The Rebirth of Engineering Discipline in Chicago
In February 2001, seventeen software practitioners met at the Lodge at Snowbird in Utah to forge the Agile Manifesto. A decade later, between 2012 and 2013, the software industry had reached a critical inflection point. "Agile" had conquered the enterprise, yet in its corporate commodification, the core engineering disciplines that birthed it—test-driven development, refactoring, pair programming, and clean architecture—were being routinely discarded. Recorded on-site at the Software Craftsmanship North America (SCNA) conferences in Chicago, these primary-source dialogues capture the original signatories reflecting on what succeeded, what went wrong, and why the discipline of software creation had to be reclaimed.
I. The Industry Context: When Agile Lost Its Code
By 2012, "Agile" was a billion-dollar industry of certifications, project management tools, and enterprise transformations. However, a growing rift had emerged between corporate management and technical practitioners. While organizations embraced 15-minute standups and Jira burn-down charts, they frequently abandoned the technical rigor that made Extreme Programming (XP) and early Agile effective: automated unit testing, continuous integration, pair programming, and relentless refactoring.
In response, a counter-revolution was born: Software Craftsmanship. Developers insisted that "working software" was an incomplete metric if the underlying codebase was an unmaintainable mess. Chicago became the national epicenter of this movement. Supported by local software consultancies like Obtiva and 8th Light, and user groups like Alt.NET Chicago, practitioners established the Software Craftsmanship North America (SCNA) conference. SCNA served as a venue where the original Agile signatories could return to their roots: focusing on the craft, ethics, and human mastery of software.
II. The Signatories & Their Unique Insights
Dave "PragDave" Thomas
Agile Manifesto Signatory / Co-author of "The Pragmatic Programmer"
The Historical Context: Recorded at SCNA 2013 in Chicago following his keynote "Unknown Knowns."
What He Came to Teach: Dave addressed how software developers move from novice rules to expert intuition. Inspired by Donald Rumsfeld's famous taxonomy, Dave highlighted the missing quadrant: unknown knowns—the deep, tacit knowledge buried below conscious thought.
Unique Insight & Primary Source Quote
Dave cautioned against romanticizing intuition as lazy shortcutting. True technical intuition is earned through rigorous, deliberate internalization:
"To do something proficiently, perhaps surprisingly, you have to do it without conscious intervention... But intuition isn't lazy. To get to the point where you can make intuitive decisions, you first have to go through the hard work of learning and internalizing everything you're deciding about."
Why it Matters: Dave identified Pair Programming and local user group teaching as essential tools to break experts out of routine "autopilot," forcing them to convert tacit habits back into conscious, shared knowledge.
Robert "Uncle Bob" Martin
Agile Manifesto Signatory / Author of "Clean Code"
The Historical Context: Recorded at SCNA 2012 in Chicago during the launch of The Clean Coders video series.
What He Came to Teach: Uncle Bob was a primary architect of the Craftsmanship movement, proposing the fifth value: "Craftsmanship over Execution." He came to rally developers toward professional ethics, self-regulation, and zero-defect discipline.
Unique Insight & Primary Source Quote
Uncle Bob realized that written articles and dry slides were insufficient to communicate the visceral discipline of clean code. He pioneered produced, scripted video as a high-bandwidth teaching medium:
"I fly all over the place and yell at people and encourage them to be professional... Video is a very wide-bandwidth communications medium. You get body language, emotion, facial expression, and tone. The more different ways you use to communicate ideas, the more the ideas get across."
Why it Matters: Uncle Bob framed code quality as a moral duty to society, warning that as software controls everything from medical devices to banking systems, unprincipled developers put human lives at risk.
Ron Jeffries & Chet Hendrickson
Agile Manifesto Signatory & XP Pioneers
The Historical Context: Recorded at SCNA 2013 in Chicago.
What They Came to Teach: As the original Extreme Programming (XP) coach and first hired developer on the historic Chrysler Comprehensive Compensation (C3) project, Ron and Chet came to demonstrate radical simplicity in communication and system design.
Unique Insight & Primary Source Quote
Eschewing corporate slides, Ron and Chet presented using hand-drawn sketches on an iPad using the Paper app, finishing each other's sentences in a seamless 15-year duo rhythm:
"Our main purpose in giving a talk is to illuminate the idea simply... If you do good it goes up, if you do bad it goes down. The idea is simple drawings so people listen to the words, catch the attention, and don't get bogged down in noise."
Why it Matters: They proved that XP's core tenet—Communication over Complexity—applies to human dialogue just as much as object-oriented design.
Brian Marick
Agile Manifesto Signatory / Testing Specialist
The Historical Context: Recorded at SCNA 2012 in Chicago.
What He Came to Teach: Brian brought a background in software testing, sociology, and philosophy to examine the missing, unwritten values of the Agile movement.
Unique Insight & Primary Source Quote
Brian highlighted the unwritten value of Ease—comparing a high-performing Agile team to an expert surgical team:
"I've done a series of talks hammering away at what values didn't get written down in the Agile Manifesto... One of them is 'Ease'—not making work easy, but doing work WITH ease. My wife was a surgeon. In a really good surgical team, you reach out your hand and the right instrument magically appears."
Why it Matters: Brian introduced the concept of "meme implantation"—using storytelling, humor, and visual symbols so that when developers face architectural stress under pressure, core values trigger automatically.
III. Historical Significance & Legacy
What was the true meaning of these interviews?
These interviews represent a primary-source oral record of a crucial transition in software history: the moment practitioners realized that business agility without technical craftsmanship leads to rapid debt accumulation and system failure.
Why is Chicago central to this story?
While the Agile Manifesto was signed in Utah, Chicago was the workshop where its principles were battle-tested. Through regional conferences (SCNA, Chicago Code Camp, Alt.NET) and local consultancies, Chicago developers created the apprenticeship models, TDD practices, and community infrastructure that sustained software craftsmanship globally.
Why do these insights matter in the era of AI-assisted engineering?
As AI code generation accelerates delivery volume, the lessons of Dave Thomas, Uncle Bob, Ron Jeffries, and Brian Marick become even more vital. Generative tools produce text quickly, but only human technical cartography, clean architecture, and explicit safety boundaries ensure long-term system durability.
Explore the full forensic archive of 183 technical conversations here.