Principles behind the Agile Manifesto

Principles behind the Agile Manifesto


We follow these principles:

1. Our highest priority is to satisfy the customer through early and continuous delivery
of valuable software.
我们最优先要做的是通过尽早、持续地交付有价值的软件来使客户满意。

2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
即使到了开发后期，也欢迎需求变化。敏捷过程能从顾客的改变中获取竞争优势。

3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
经常性地交付可以工作的软件。从几周到几月，我们偏爱短的时间尺度。

4. Business people and developers must work together daily throughout the project.
在项目的整个开发期间，业务人员和开发人员始终在一起工作。

5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
围绕被激励起的个体来构建项目。为他们提供所需的环境和支持，并信任他们能胜任工作。

6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
在团队内部，最有效果和最有效率的传递信息的方法是面对面地交流。

7. Working software is the primary measure of progress.
可以工作的软件是主要的进度度量标准。

8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
敏捷过程提倡可持续的开发速度。

9. Continuous attention to technical excellence and good design enhances agility.
持续关注最优秀的技术和良好的设计以增强敏捷能力。

10. Simplicity--the art of maximizing the amount of work not done--is essential.
简单是根本的。

11. The best architectures, requirements, and designs emerge from self-organizing teams.
最好的架构、需求和设计来自于自组织的团队。

12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
开发团队每隔一定时间，都对如何能有效地工作进行反省，然后对自己的行为进行调整。

参考：
1.
2. http://www.ibm.com/developerworks/cn/architecture/ar-archman1/