敏捷

 

转园中的文章－－－－－－

敏捷宣言(Manifesto for Agile Software Development)

Individuals and interactions over processes and tools    个体和交互胜过过程和工具

Working software over comprehensive documentation   可用的软件胜于详尽的文档

Customer collaboration over contract negotiation           客户协作胜于合同谈判

Responding to change over following a plan                   响应变化胜于恪守计划

----- Kent Beck,Mike Beedle,Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, on Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas

把宣言人的名字列在这里，可以给大家买书做个参考，比如Dave Thomas 写的Agile web development  with Ruby on Rails.

敏捷宣言12条原则

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.

   团队定期地对运作如何更加有效进行反思，并相应地调整、校正自己的行为

转载于:https://www.cnblogs.com/zhangli/archive/2008/11/19/1336871.html