Manifesto for Agile [Product] Development
"We are uncovering better ways of developing products by doing it and helping others to do it. Through this work we have come to value—
• Individuals and interactions over processes and tools
• Working products over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
That is, while there is value on the items on the right, we value the items on the left more."
Principles Behind the Agile Manifesto
• "Our highest priority is to satisfy the customer through early and continuous delivery of valuable [products].
• Changing requirements should be welcomed, even late in development. Agile processes harness change for the customer's competitive advantage.
• The delivery of working [products] should be frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
• Business people and developers must work together daily throughout the project.
• Projects should be built around motivated individuals. Give these individuals the environment and support they need, and trust them to get the job done.
• The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
• Working [products] is the primary measure of progress.
• Agile processes promote sustainable development. The sponsors, developers and users should be able to maintain a constant pace indefinitely.
• Continuous attention to technical excellence and good design enhances agility.
• Simplicity — the art of maximising the amount of work not done — is essential.
• The best architectures, requirements, and designs emerge from self-organising teams.
• At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly."
Assuming that your project involves innovation, requires unique expertise and needs a timely turnaround, an agile project approach can provide the solutions or outcome that you need.