Simple Beauty-thinking of software development practitioners 02

Agile Development focuses on people, or individuals. The goal is to improve individual initiative and improve output efficiency. Agile Development requires teams to work together and even customers. Pair programming . Iterative delivery, three weeks for a cycle, each of which publishes the available, tested code. 2 to 5 cycles after a release. Agile development actively embraces change , relying primarily on code refactoring to match change.

The advantage of Agile development is short release time and response to demand changes, the disadvantage of agile development is poor operability. Practitioners often go into all kinds of misunderstandings. The root cause is still people, people's initiative and behavior in software development is affected by a variety of factors.

prepare two documents in the requirements analysis phase. A customer story is expressed in terms of the customer, and the other is a story that uses software terminology to express the software implementation. A requirement analyst is a bridge between the customer and the project team, a bridge between the customer and the software developer ,

Very similar to the surgical procedure, the software development team needs a solo surgeon, the software Architect. The software Architect ensures that the whole idea and architecture of the software is a subject. Rather than scattered, patchwork. This facilitates development and maintenance. Software architects typically have only one team, or a team of architects is headed by one of them. This ensures the consistency of the entire software system. The main basis of the Software Architect's work is experience. In the process of software development, people are the most important factor, while responsibility, rights and interests are the key to ensure this factor to play a role. Responsible culture is a kind of culture that must be possessed in the human society activities. Teams tend to be irresponsible. The purpose of establishing a system of responsibility is not to punish, but to show the fact that there is no diamond, no porcelain to live on, in the form of loss of interest. is also an important driver of quality assurance. On the 3rd chapter on the demand
Demand is like the source of a beam of light, near misses, great difference. No one does not pay attention to the problem of demand, however, how many people can speak clearly the idea of solving the demand problem? Ask yourself, how much confidence does the demand-tracking matrix and the demand-change committee raise?
This chapter tries to give a solution to the demand problem. The logic of this method is very simple, first of all, we need to accurately express demand, terminology and storytelling are two good auxiliary means; second, we want to work with customers to drive demand change, demand change is not synonymous with cost, passively accept demand change is the main culprit of devouring costs.

Simple Beauty-thinking of software development practitioners 02