Agile Manifesto
Better ways of developing software by doing it and helping others do it.
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
The agile industrial complex. Everyone know agile, but really?
Many argue that “faux agile,” as it’s also called, and its evil twin “dark agile,” are exacerbated by the monetization of agile education and consulting.
“There’s cargo cult agile where you’re doing and saying the right things, but you don’t understand the fundamental principles. You’re not getting the results,” Buchanan said.
Call it “faux,” “dark,” or “cargo cult,” these agile subversions often lead to situations that fly in the face of the Manifesto’s intentions—micromanagement, burnout-rate pacing, lack of delivery, and adherence to process over principles register as the most egregious—even if their practitioners come with a certificate. Unfortunately, these dark agile experiences cause some people to swear off agile altogether, (or rewrite it to reflect their real-world experience with it.)
What does it all mean?
So, the agile principles existed before the Agile Manifesto. People applied them to software development. Those values were captured in the Agile Manifesto. Then, people took the Manifesto’s principles and started applying them to their own work.
“In a lot of ways, the Manifesto is a basis of a conversation,” Wortham said. “Here’s how I interpret it. How do you interpret it? All right, let’s figure out how to work together.”
Ref: