A survey of Agile development methods

Agile development is a human-centered, iterative, progressive development approach. In agile development, the construction of software projects is divided into sub-projects, the results of each sub-project are tested, with integration and operational characteristics. In other words, a large project is divided into several interconnected, but also can be run independently of small projects, and completed, in the process of software has been in a state of use.

Agile Modeling,am's values include the four values of XP (Extreme Programming: Extreme Programming): Communication, simplicity, feedback, courage, and, in addition, a fifth value: humility.

Scrum and XP are specific ways to develop agile.

The difference between scrum and XP is that scrum focuses on the process, while XP focuses on practice, but in practice, the two are applied in combination.

Scrum refers to an iterative incremental software development process, often used for agile software development. Although scrum is developed for managing software development projects, it can also be used to run software maintenance teams or as a plan management approach. Collaboration between scrum is called "Scrum of Scrums".

The three major roles in the scrum development process:

Product owner is primarily responsible for determining the functionality of the product and meeting the required standards, specifying the release date and delivery content of the software, as well as the right to accept or reject the work of the development team.

The Process Manager (Scrum Master) is primarily responsible for the smooth implementation and execution of the entire Scrum process within the project, as well as the removal of communication barriers between the customer and the development effort, enabling customers to drive development directly.

The development team (Scrum team) is primarily responsible for the development of the SOFTWARE PRODUCT under the scrum specification process, the number of people is controlled by the 5~10, each member may be responsible for different technical aspects, but requires that each member must have a strong self-management ability, but also have a certain ability to express Members can work in any way they can, as long as they reach the sprint goal.

In each sprint (a 15-30-day cycle, whose length is determined by the development team), the development team creates an increment of available (ready-to-roll) software. Each sprint is implemented from the product backlog. Product orders are the requirements for a summary of the work to be done in priority order, and which order items will be added to a sprint will be determined by the sprint planning meeting. During the meeting, the product owner tells the development team what order items he needs to complete in the product order. The development team decides how many order items they can commit to complete in the next sprint. During the sprint, no one can change the sprint order, which means that demand is frozen in a sprint.

There are many ways to manage the scrum process, from instant stickers to whiteboards to software packages. One of the biggest benefits of scrum is that it's very easy to learn, and it doesn't take much effort to start a scrum application.

Refer to the following content:

http://wiki.mbalib.com/wiki/Agile Development

Http://wiki.mbalib.com/wiki/Scrum

Http://www.cnblogs.com/taven/archive/2010/10/17/1853386.html

Http://baike.baidu.com/link?url=3mcKhVMG5OXKeNgnCGK-l4zaY9zP9Tc247M1PRfn_vk-YdP3g4MJ0Ip1IZP9WC8THqf-3cixnCmQtZJklVAPPq#12

Http://baike.baidu.com/link?url=OFE6U5YXWpVBqEnOV-TffBLRdYIJjCebNFNsU6S1jMjxG7NZhGtcYiPE0CGW6Zn4pUk38zooIv5j4mnoo6en4a#4

A survey of Agile development methods