Reading Martin Fowler's experience in the new methodology-utopia-based development

1. agile methods are adaptive, not predictive (Adaptive rather than predictive), but human-oriented rather than process-oriented (People-oriented rather than process-oriented)

2.CodeIs the design document (source code is a design document)
For traditional engineering, design and construction can be separated, but for software engineering, all work is designed.

3. Demand is unpredictable and constantly changing. It is dangerous to try to predict unpredictable needs.
Some software companies first write down the requirements and ask the users to sign for confirmation. then, the development is centered on this requirement document, and only minor changes are allowed. however, this is not feasible or irresponsible.
Demand changes are a headache. when you are building a business software, even if the customer doesn't want to change their needs, the market environment forces him to change. The so-called mall is like a battlefield. I have worked on a software of this type. the result is that the software has been working, and the demand has been changing. At that time, it seems that this project can never be completed.

4. People-oriented! Developers are not compatible with programming units.

5. Developers should be more active in the project and develop their own work plans.
Developers should keep close contact with managers and users. indeed, because the software is made for use by people, more people should be involved in development. this prompted close contact among software developers. developers should actively participate in project management, which is the same as the management personnel, it is also up to developers to decide how to develop projects-This viewpoint is in conflict with the traditional management theory viewpoint.

6. How should I start agile development?
You should find a project that is relatively easy to manage and start to try agile development. It is better not to be a project of no importance.

7. Agile development is not just a small project.

8. Do not force development teams unwilling to use agile methods to use this method. for customers who do not want to follow agile methods, try to involve them in the project.