Richards' Agile conference presentations represent the moment where the Boyd-to-business translation project made direct contact with the software development community. Presented at agile-alliance events and related venues during the agile-engagement-period, these talks made explicit what certain-to-win had implied: that Agile software development practices are not merely analogous to john-boyd's organizational climate prescriptions but are a concrete implementation of them in the knowledge-work domain.
The central argument
The presentations' governing claim is that Agile — specifically Scrum as articulated by jeff-sutherland — implements Boyd's organizational climate concepts at the team level. The three elements of Boyd's organizational climate that Richards had translated in Certain to Win (einheit-as-trust, fingerspitzengefuehl-as-expertise, schwerpunkt-as-focus) map onto Agile team dynamics with more than superficial resemblance:
The trust and cohesion of a high-performing Scrum team (cross-functional, self-organizing, with shared ownership of quality) instantiates einheit-as-trust — the mutual trust that enables implicit coordination without constant explicit direction. Team members who trust each other's judgment and share commitment to the sprint goal can make locally coherent decisions without escalating every issue to a product owner or scrum master.
The deep expertise of a software craftsperson — the developer who can read a codebase and see where problems will emerge, who knows the technology well enough to generate reliable intuitive judgment — is fingerspitzengefuehl-as-expertise in the software domain. This is not generic skill but orientation: accumulated experience structured as reliable implicit knowledge.
The sprint goal, the product vision, and the team's shared understanding of what success looks like constitute schwerpunkt-as-focus: the shared intent that allows decentralized execution. A team that knows what it is trying to accomplish can make local technical decisions consistently with that intent, enabling the autonomous action that sprint-based development depends on.
The Sutherland connection
A significant contribution of the presentations was documenting jeff-sutherland's explicit acknowledgment of Boyd as an intellectual influence on Scrum's development. Sutherland had cited Boyd in early Scrum papers, and Richards used the conference presentations to make this lineage explicit and examine it in detail — showing that Scrum's design choices (self-organizing teams, timeboxed iterations, empirical process control) have theoretical grounding in Boyd's organizational analysis that extends beyond the software-specific arguments Sutherland made.
This documentation matters for the intellectual history. The Boyd-to-Agile connection might otherwise appear as retrospective pattern-matching — someone noticing similarities after the fact. Richards' presentations establish that the connection was present in the founding documents of Scrum and that Sutherland himself understood what he was implementing.
The agile-as-maneuver-warfare frame
Beyond the specific Sutherland connection, the presentations develop what Richards calls agile-as-maneuver-warfare: the argument that Agile software development addresses the same fundamental problem that maneuver warfare addresses in military contexts. Both domains involve operating effectively under conditions of uncertainty, with incomplete information, in a changing environment where the situation at the start of an operation may bear little resemblance to the situation at the end.
Waterfall software development, in this frame, is attrition-style planning: detailed upfront specification, sequential execution, validation against original requirements. The problem is not that waterfall practitioners are incompetent but that they are applying attrition logic to a maneuver problem. Software development environments change too rapidly and are too uncertain for upfront planning to remain accurate through a long development cycle. Agile's short iterations, continuous feedback, and empirical process control are maneuver responses: act, observe results, reorient, act again.
Relationship to the Richards canon
The Agile presentations are, in a sense, the application layer for certain-to-win. The book develops the framework; the talks show how it applies to a specific community's specific practices. They are also the primary vehicle through which Richards became known in Agile circles — the boyd-and-beyond-conference and agile-alliance presentations gave him direct access to practitioners who would otherwise not have read a military strategy book.
The talks also contributed to the development of fast-transients-blog content — many blog posts after 2009 reflect the questions and discussions that arose in conference contexts. Together, they constitute the most significant single vector for Boyd's influence on the Agile and lean software movements.