Development Methodology (Agile)
We are uncovering better ways of developing software by doing it and showing others how to 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

Ten Commandments of our Software Development Process

• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
• Always provide the best value for the money.
• Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. (Everything is changeable.)
• Working software is the primary measure of progress. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. (An 80 percent solution today instead of 100 percent solution tomorrow.)
• Success depends on active customer participation. Business people and developers must work together daily throughout the project.
• The best architectures, requirements, and designs emerge from self-organizing teams.
• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Continuous attention to technical excellence and good design enhances agility.
• The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
• Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
• Simplicity--the art of maximizing the amount of work not done--is essential.