Agile Manifesto And The Politics of Software Development

"Customer collaboration over contract negotiation
Responding to change over following a plan"

It's funny when other developer's invoke these words while they rant against customers. On a looming deadline they will call for more customer collaboration because "software is abstract", on a never-ending change requests they will use the "contract negotiation" to avoid work for what they are paid for.

Now this is for the project managers..."Responding to change when the plan goes haywire". We still need a plan and the plan is expected to be followed and responding to change is just a contingency...a very unnecessary contingency. But where is the plan to start with?


Anonymous said…
I don't follow your post. It is hard to tell what you are trying to say. Are you saying that people are misusing part of the agile manifesto to "cover" for their shortcomings or are you saying the manifesto somehow lends itself to abuse in this way? Could you elaborate on your points?

Popular Posts