This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.

In 2001, a bunch of people got together and wrote a manifesto on Agile software. There were two main factors that made the output suspect. First, the fact that they even called it a manifesto. Second, the manifesto had nothing to do with software. It talked about values.

For those in need of a refresher, here’s the “Manifesto for Agile Software Development:”

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

-- Individuals and interactions over processes and tools

-- Working software over comprehensive documentation

-- Customer collaboration over contract negotiation

-- Responding to change over following a plan --

That is, while there is value in the items on the right, we value the items on the left more.

Somewhere along the line, we started doing daily standups, two-week sprints, maybe a little pair programming here and there. Since then our software output and productivity have sky-rocketed. Remember when we used to have an end-of-project company bug hunt? How about the integration Continue reading