Chapter Fifth section III
The book shows us the waterfall model, the sashimi model, the sub-waterfall model, and the RUP, and in fact the current company makes a software that is constantly circulating in a gradual delivery process, and finally deciding on the final version?
Chapter Sixth section II
This chapter talks about agile processes, the problems and solutions of agile processes, agile teams, agile summaries, and agile stories, knowing that agility can greatly improve the motivation of the team. Agile processes in software development projects are organized into members of each team, but it is not necessarily appropriate for each team member, what should happen? When to use agile is the most suitable?
Seventh chapter Fifth Section
In the fifth chapter, it is said that developers and testers will produce a kind of antagonistic emotion, which can stimulate the enthusiasm of the members in a short time, and the long term will be harmful. In a real company, what should developers and testers do if they have conflicting emotions? How to reduce the impact of this antagonistic mood on them?
Post-reading experience:
By reading these chapters, I learned that the development process, agile process, and MSF knowledge, not only enrich my knowledge, but also let me understand that in a team, each member of the team should be responsible for the project, and more importantly, each member's goal must be consistent , so that we can make a project to do the best, or even if your project is made, your project is rotten unspeakable (such as the book up and down the example of Go), each member can not be a spectator mentality to treat the project, must be responsible attitude to treat it. The success or failure of a team depends on whether the members of your team are responsible for your team.
Read the 5-7 chapter of the Law of construction