I've modified them slightly to better fit game development.
We are uncovering better ways of developing games by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over process and tools
- Working game over comprehensive design documentation
- Publisher collaboration over milestone negotiation
- Responding to change over following a plan
The principles behind the Agile Manifesto:
- Highest priority is to satisfy the customer through early & continuous delivery of valuable software, assets and gameplay.
- Welcome changing requirements, even late in development. Agile processes harness change for the developer's competitive advantage.
- Deliver working gameplay frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- Business people & developers must work together daily throughout the project.
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
- The most efficient & effective way of conveying info within a dev team is face-to-face conversation.
- A working game is the primary measure of progress.
- Agile processes promote sustainable development. The sponsors and developers should be able to maintain a constant pace indefinitely.
- Continuous attention to balanced artistic quality, technical excellence and good design enhances agility.
- Simplicity--the art of maximizing the amount of work not done—is essential.
- The best architectures, budgets, assets, requirements, and designs emerge from self organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.