The Panic Driven Development Manifesto
To begin the story you should know about the Manifesto for Agile Software Development
These ideas are now more than a decade old and just as most other noble ideas they have morphed into thorny parodies of the original.
A lot of my customers practice Panic Driven Development
|Individuals and interactions over processes and tools||do whatever we're told in response to uninformed panic.|
|Working software over comprehensive documentation||fix it when some one panics, unless it's documented. Then it's a know issue.|
|Customer collaboration over contract negotiation||make it a two way hostage negotiation, with panic in both camps.|
|Responding to change over following a plan||panic.|