敏捷原则

Principles behind the Agile Manifesto:
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.      即使到了开发的后期，也欢迎改变需求，敏捷过程利用变化来为客户创造竞争优势。

3.      经常性地交付可以工作的软件，交付的间隔可以从几个星期到几个月，交付的时间间隔越短越好。

4.      在整个项目开发期间，业务人员和开发人员必须天天都在一起工作。

5.      围绕被激励起来的个体来构建项目。给他们提供所需的环境和支持，并且信任他们能够完成工作。

6.      在团队内部，最具有效果并且富有效率的传递信息的方法，就是面对面的交流。

7.      工作的软件是首要的进度度量标准。

8.      敏捷过程提倡可持续的开发速度。责任人、开发者和用户应该能够保持一个长期的、恒定的开发速度。

9.      不断地关注优秀的技能和好的设计会增强敏捷能力。

10.  简单--使未完成的工作最大化的艺术---是根本的。

11.  最好的构架、需求和设计出自于自组织的团队。

12.每隔一定时间，团队会在如何才能更有效地工作方面进行反省，然后相应地对自己的行为进行调整。