Agile Principles


We believe that the use of Agile Principles in Software Development provides significant benefits to all the stakeholders in the development process. The core principles were set out by a group of software development luminaries whose goal is to uncover better ways of developing software. This is covered in the Agile Manifesto which can be found at These agile principles act as a practical pragmatic guide for how software development is performed. They promote the de-emphasis of aspects of the software development process that though important, can de-rail the actual end goal of working useful software.

Though work processes and tools are important...


Individuals and Interactions are more important. In other words, the quality of the people that are working and their willingness to achieve a goal together is more important than the work processes and tools they use. We deliver software early and often as part of our typical development process. It gets the software in your hands quickly and allows you to
Though comprehensive documentation is important....


Working software is more important. There is no point having detailed documentation if the software being documented is not operational and working.
Though contract negotiation is important...

Fine Print Contract

Customer collaboration is more important. Arguing over the finer points of a contract that probably doesn’t define what is needed in totality wastes everyone’s time. It’s far more effective to be practical and work together towards a goal that may change during a project.

Though following a plan laid out at the beginning of a project is important....


Responding to change is more important. This is similar in intent to the quote from Eisenhower:
Plans are worthless. Planning is essential.

Yes, we need to plan up front, but it’s more important to be able to learn as you get into a project and adjust to new information and understanding as it is made available or uncovered.