What lessons can the agile community learn from a maverick fighter pilot?

  title={What lessons can the agile community learn from a maverick fighter pilot?},
  author={Steve Adolph},
  journal={AGILE 2006 (AGILE'06)},
  pages={6 pp.-99}
  • Steve Adolph
  • Published 23 July 2006
  • Computer Science
  • AGILE 2006 (AGILE'06)
For the agile software development community, agility is defined by the values expressed in the agile manifesto. But in concrete terms, what does it mean for a software project to be agile? US Air Force Colonel John Boyd defined agility as the ability to operate the observation-orientation-decision-action (OODA) loop faster than an adversary. Agility therefore depends on the tempo at which we can exploit the OODA loop, and it is culture, not methodologies or tools that determine our OODA loop… 

Figures from this paper

Reconciling agility and architecture: a theory of agile architecture
The thesis presents a theory that describes how agile software teams design an agile architecture with reduced up-front design and which is able to respond to change, helping teams find a balance between architecture and agility.
How Much Up-Front? A Grounded theory of Agile Architecture
A grounded theory of agile architecture is presented that describes how agile software teams answer the question of how much upfront architecture design effort is enough to help them determine how much effort they should put into up-front design.
Towards the End of Agile: Owing to Common Misconceptions in the Minds of Agile Creators
Owing to the “sold practices” of the market and misleading misconceptions in the minds of Agile creators, there are issues in Agile like regarding it as a “holy” product and everything, binary thinking, trade-offs, and determinism that do not support agility in an absolute sense and even inhibit it, which ultimately lead to the end ofAgileTM.
Contextualizing agile software development
A contextual model for software‐intensive systems development to guide the adoption and adaptation of agile software development practices was found especially useful when the project context departs significantly from the “agile sweet spot”.
Towards Pertinent Characteristics of Agility and Agile Practices for Software Processes
It would be interesting to replicate the study in other contexts, with different subjects, and compare them, to increase the generalization of their results.
Contextualizing agile systems engineering
Several agile methods were proposed that should provide more agility for Systems Engineering. But there was little discussion about the right context for Agile Systems Engineering. This paper shows
To address limitations of Lean in construction, new paradigms linked to Agile management methods are receiving increased attention. Agile approaches to management in manufacturing and information
Agility in information systems development : characterisation , motivation and conceptualisation
While a malleable and simple IT infrastructure may support an organisation in its attempts to reconfigure its capabilities and business processes in order to take advantage of expected and unexpected turbulences, a rigid and complex IT infrastructure might hinder those efforts.
Agile Development in Data Warehousing
The agile development methodologies in data warehousing and business intelligence, implications of the agile methodology, managing changes in data warehouses given frequent change in business intelligence requirements, and the impact of agility on the business are discussed.
The frog and the octopus: a conceptual model of software development
It is shown how the model can be used as an explanatory theory of software development, as a tool for analysis of practices, techniques, processes, as the basis for curriculum design or for software process adoption and improvement, and to support empirical research on software development methods.


Are we ready to be unleashed? A comparative analysis between agile software development and war fighting
  • Steve Adolph
  • Business
    Agile Development Conference (ADC'05)
  • 2005
There are sufficient similarities between the nature of war fighting and the natureof software development to warrant a comparison between military war fighting philosophy and the principles of agile software development.
Agility with the RUP
What characterizes an agile software development process? Is agility about being fast to deliver? "Faster, better, cheaper" is a laudable goal, but faster in itself is not necessarily the right thing
Agile Software Development with SCRUM
This book describes building systems using the deceptively simple process, Scrum, a new approach to systems development projects that cuts through the ocmplexity and ambiguity of complex, emergent requiremetns and unstable technology to iteratively and quickly produce quality software.
Making RUP agile
What it takes to make RUP agile,How it was applied in the two projects, and how it was configured are gone into.
Extreme Programming Explained
Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new
Sources of Power: How People Make Decisions
Anyone who watches the television news has seen images of firefighters rescuing people from burning buildings and paramedics treating bombing victims. How do these individuals make the split-second
Boyd: The Fighter Pilot Who Changed the Art of War
A detailed portrait of American fighter pilot John Boyd examines his distinguished military career during the Korean War and his postwar efforts as a military theorist who took on the entrenched
Cockpit resource management.
A new book enPDFd cockpit resource management that can be a new way to explore the knowledge and get one thing to always remember in every reading time, even step by step is shown.