Agile

最近，由于一些原因触发自己对敏捷软件开发有了一个全新的反思。

 

可能敏捷软件开发会比较适合我目前公司遇到的问题，可惜没有时间和机会去验证了。碰巧这个时候看到Martin Flower的一篇关于"Using an Agile Software Process with Offshore Development"的文章（http://martinfowler.com/articles/agileOffshore.html），觉得说得有一定道理。看来，我们公司很多地方都踩到那个点了，只是没有很坚持或者系统化。

 

在这里把敏捷宣言和一些原则重新敲一遍，我想接下来会有更多的时间去熟悉它：

 

Manifesto for Agile Software Development

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

 

Individuals and interactions over processes and tools

人是最关键的，这一条回答了如何在一个team or project中定位一个人：他的行为，角色和职能，以及人与人之间交互的方式

Working software over comprehensive documentation

项目的目的就是做事情，这一条告诉我们如何来使得我们的工作成果更容易体现出来，以何种形式体现出来。

Customer collaboration over contract negotiation

 项目的最终受众是customer，项目成败的关键在于customer的满意度以及在整个开发过程中的幸福度。

Responding to change over following a plan

而软件开发最大的天敌就是变化，对于它的态度以及应对的策略将最终决定你的项目成败。

 

That is, while there is value in the items on the right, we value the items on the left more.

 

 

Principles behind the Agile Manifesto

 

We follow these principles:

Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.

Deliver working software 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.

Build projects around motivated individuals.
Give them 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 software 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 maximizing the amount
of work not done--is essential.

The best architectures, 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.