It took 3 days to fully squeeze out the time in the sponge, read the "Easy Scrum Journey: Agile Development Story" This book, feel well written, interesting, found at the time to look at the design mode when the feeling.
From the title of the book can be seen, this book is mainly about agile development, I am also the first contact, understanding of the bad also please readers forgive me.
One, from a technical point of view: the traditional waterfall model because in the early days spent a lot of time to analyze requirements and prepare documents, resulting in the product model in the time of each iteration will be very long. And this is likely to occur in the constant change in demand, and even after the completion of the product has been divorced from the times, lost its role should have. The consequences are clear: the user is dissatisfied, and the cost is great.
Agile development is more ethereal and changeable. First, the lightweight documentation eliminates the need to prepare complex analyses and records that have been neglected for years, and the ample preparation for change is no longer a programmer's nightmare.
Second, from the perspective of organizational management, 1, our traditional team development is likely to exist the following phenomenon. such as: Inter-departmental uncoordinated, lack of adequate communication, interpersonal communication become a paper empty-talk; Members of the group often develop their own parts, the whole or related parts of the project is not very familiar with the lack of communication channels lead to upload release and team communication there are some unnecessary problems, even caused contradictions.
The root of these problems stems from the lack of appropriate mechanisms to organize and exchange, to fully express their views and ideas is the agile development of people-oriented, team cooperation purposes.
2, in the project control, the traditional development are defined, according to the plan to the overall task is fixed one-time, lack of flexibility, difficult to deal with the internal and external environment changes. However, the Backlog-story-task task partitioning mechanism in agile development solves this problem very well, so that when the demand of the project changes greatly, it can be fully dealt with in the way of first urgency and slow.
3, in the Division of the Department, Agile Development advocated by the Product division, not the department. By binding the coding and testers together, the entire development process becomes a smooth whole, avoiding competing resources, putting unit tests behind each sprint, easing the pressure on the integration test, and easing the testers ' lack of understanding The test is not exhaustive or the description is inaccurate and the programmer is divided.
Third, from the perspective of learning, we can learn from the agile development of some excellent experience and ideas. Usually take into account the overall planning and detail planning, in response to change to be flexible, to set aside enough buffer time for themselves.
It is a strong reference for self-adjustment to be good at interpersonal communication and to understand the situation of the group, the excellent or the individual who is closely related to oneself.
Finally, make the choice to find the right environment and method. Stepping on so many "Guan Yi" shoulders, we have enough level of knowledge and cognitive ability to adapt to the rhythm of the world.
A little sense of agile development
