Agile development - 备忘

Introduction

Agile is a relatively new development methodology, that is based on the iterative and incremental development model.

For a long time development and project managers followed the waterfall method where they compared software development to a manufacturing line. That is they wanted each stage of the development life-cycle to be complete before the start of the next stage.

It took decades before they realized that developing software products was a lot more volatile process than that, there are relatively few if at all any software development projects that could be run through these various stages one after the other. The changes in scope, budget are continuously changing.

Software development is more like the development of a new product as apposed to a production line. Also there are many over laps between the various stages of development. By Incorporating these overlaps in your development life-cycle leads to reducing the cost of change.

In the early nineties the Japanese manufacturing companies began to practice lean manufacturing technics such as JIT. This improvement in the manufacturing industry gave rise to the concept of Agile method of software development.

Definition :- Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.

Over View

In simpler words Agile is a culture and not a process. There are no defined process as such, but over the years there has been a common set of approaches have evolved.

Below are a list of common steps between the various approaches.

1. Product owners in association with developers create stories in a backlog
2. Developers estimate based on rough ball park figures
3. Product owners create development cycles of six weeks and arrange stories for each run
4. At the end of each run the development team produces a full implementation of the product
5. The product owner can calculate effort against time taken for the first run to arrive at the velocity.
6. The teams will meet on regular basis every day for short stand up meetings to discuss issues/timelines etc

7. Development cycles will get repeated till completion of the product

http://kb.cnblogs.com/page/107587/

12 principle

敏捷开发的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 mouths, with a preference for 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. 
　　团队要定期反省如何能够做到更有效，并相应地调整团队的行为。

http://kb.cnblogs.com/page/107587/