Agile development method

Agile development method is also called "lightweight" development method.

1, fast iteration

Compared with the semi-annual release of the large version, the requirements, development and testing of the small version are simpler and faster. Some companies only release 2-3 versions a year, and the release process is slow. They still adopt waterfall development mode, and more seriously, they have misunderstandings about agile development mode.

2. Let testers and developers participate in the requirements discussion.

It is most effective to discuss requirements in the form of discussion groups. The seminar team needs to include testers and developers, which makes it easier to define testable requirements, group requirements and determine priorities. At the same time, this method can also make full use of the complementary characteristics of team members. The demand determined in this way is often more efficient than the demand discussion meeting, and everyone is more active and has a stronger sense of participation.

3. Write testable requirements documents

Start with a "user story" (user? Story) method to write requirements documents. This approach allows us to focus on requirements rather than solutions and implementation technologies. Premature mention of technical realization will reduce the attention to requirements.

4. Communicate more and minimize files.

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

The team should ensure daily communication, and face-to-face communication is much better than email.

5. Make a good product prototype

Sketches and models are recommended to illustrate the user interface. Not everyone can understand a complicated document, but everyone can read pictures.

6. Consider testing as soon as possible

It is important to consider testing in the early stage of agile development. In traditional software development, test cases are written very late, which leads to problems in requirements being discovered too late and the cost of improvement is too high. Start writing test cases as early as possible. When the requirements are completed, the acceptable test cases are basically completed together.