[读书笔记]Applying UML and patterns:The agile manifesto and principles

The agile manifesto and principles:

The agile manifesto

Individuals and interactions            over processes and tools.

Working software                       over comprehensive documentation

Customer collaboration                 over contract negotiation

Responding to change                  over following a plan

The agile 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 processed 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 time scale.

4.       Business people and developers must work together daily throughout the project.

5.       Build projects around motivated individuals.

6.       The most efficient and effective method of conveying information to and within a development team is face-to-face conversion.

7.       Working software is the primary measure of progress.

8.       Agile processed promote sustainable development.

9.       The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

10.   Continuous attention to technical excellence and good design enhances agility.

11.   Simplicity---the art of maximizing the amount of work not done----is essential.

12.   The best architectures, requirements, and designs emerge from self-organizing teams.

13.   At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

 

对于敏捷开发过程及其中所讲到的一些知识，其实在项目开发中多多少少的用到了一些，但也有一些与这种开发模式有冲突的地方。其中讨论的迭代开发模式感觉还不错。