A survey of Agile development methods

The so-called agile development, is to take the user's needs evolve as the core, the use of iterative, gradual approach to software development. In agile development, software projects are cut into multiple sub-projects in the early stages of construction, and the results of each sub-project are tested for visual, integrated, and operational use features. 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.

The process of agile development:

In the context of software engineering, "agile Processes" are a collection of values and methodologies. The principles it follows are:

1. Fast Iteration

The requirements, development, and testing of a small version are much simpler and faster than that of a half-yearly large release. Some companies publish only two or three versions a year, the release process is slow, they still use the waterfall development model, more serious is the Agile development model has misunderstood.

2. involve testers and developers in the requirements discussion

The demand discussion is most efficient in the form of discussion groups. Discussion groups, which need to include testers and developers, make it easier to define testable requirements, group requirements, and prioritize them. At the same time, this method can also make full use of the complementary characteristics between team members. The need for such certainty is often more efficient, more active and more participatory than the need to discuss the conference.

3. Write a testable requirements document

Start by using the user story method to write the requirements document. This approach allows us to focus on requirements rather than solutions and implementation techniques. Premature mention of a technology implementation reduces the need for attention.

4. communicate more, minimize documentation

Communication is a common problem in any project. Good communication is a prerequisite for agile development. The longer you mix in a circle, the more you emphasize the importance of good and efficient communication.

The team wants to make sure that everyday communication is much better than email.

5. do the product prototype

It is recommended that you use sketches and models to clarify the user interface. Not everyone can understand a complex document, but everyone will look at the picture.

6. Early consideration of testing

It is important to consider testing early in agile development. Traditional software development, test cases start writing late, which leads to late detection of problems in demand, making the cost of improvement too high. Start writing test cases earlier, and when the requirements are complete, the acceptable test cases are basically complete.

Process Overview:

1. Find out what you need to do to complete the product

2. Decide what you need to solve for your current sprint

3. Sprint

A survey of Agile development methods