Looking at Software Development through an OODA Loop

Last Updated on Wednesday, 20 August 2008 06:35 Written by admin Wednesday, 20 August 2008 06:35

Great post by John Scott at PowderMonkey wherein he uses the Department of Defense OODA loop (Observe, Orient, Decide, Act) to identify a few strategic failings in defense software development.

Here’s the money quote:

Why does this matter? Software is what runs the military and not being able to rapidly incorporate new ideas into the collective of military systems leaves the US at a disadvantage when our enemies grab and install versus how we do it: need/req’s/allocate funds/design/construct/test/reconstruct/test deploy/throw away/blame contractors/start over.