Skip to content

Excellent!

Drectly quoting: Re: When does Agile fail?

The answer would have to look like:

- When does it work better to focus on process and tools, because focusing on individuals and interactions would fail?
- When does it work better to focus on comprehensive documentation, because focusing on working software would fail?
- When does it work better to focus on contract negotiation, because focusing on customer collaboration would fail?
- When does it work better to focus on following a plan, because focusing on responding to change would fail?

Pretty much everything else comes down to, “we tried some set of techniques and strategies, and operationally, they didn’t work for us.”

Which doesn’t say anything about whether “agile” works or not, more about how well the organization reacted, how appropriate the
strategies chosen, and how the people worked together.

By the way, if you think this is an unfair test, try reversing it:

- When does it work better to focus on individuals and interactions, because focusing on process and tools would fail?
- When does it work better to focus on working software, because focusing on comprehensive documentation would fail?
- When does it work better to focus on customer collaboration, because focusing on contract negotiation would fail?
- When does it work better to focus on responding to change, because focusing on following a plan would fail?

I think we can construct answers to those.

Tags:

C, Java Enterprise Edition, JEE, J2EE, JBoss, Application Server, Glassfish, JavaServer Pages, JSP, Tag Libraries, Servlets, Enterprise Java Beans, EJB, Java Messaging Service JMS, BEA Weblogic, JBoss, Application Servers, Spring Framework, Groovy, Grails, Griffon, GPars, GAnt, Spock, Gradle, Seam, Open Source, Service Oriented Architectures, SOA, Java 2 Standard Edition, J2SE, Eclipse, Intellij, Oracle Service Bus, OSB