1. Fast iterations 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 requirements discussion in the form of a discussion group to be most efficient. 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. Writing a testable requirements document starts with a "user story" approach to writing 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. Multi-communication, minimizing documentation in any project, communication is a common problem. 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 a good job prototyping recommends using 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 in early consideration of testing is important 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.
Principles of Agile Development