Sixth chapter-Agile processes
The sixth chapter introduces the agile process in detail, in the Software engineering category, "Agile process" is a set of values and methodologies. This chapter is based on the scrum methodology of agile processes, and the essence of agile processes is rapid delivery. The process of agile development is as follows:
1. Find out what needs to be done-product Backlog.
2. Decide what the current sprint needs to solve--sprint Backlog.
3. Sprint (Sprint). In the sprint phase, outsiders cannot directly disturb team members. During the daily meeting, report the progress to the companion and put the problem on the materializing. Start the daily build at the same time, so that you can see a gradually improved version every day. Show the progress of the whole project with a concise chart (burndown chart/Kanban chart). The sprint phase is time-driven and ends when the time is up.
4, get an incremental version of the software, released to the user. The new features and improvements of the incremental are then further planned on this basis.
Each team needs a lot of time to run, whether it is the program or team members themselves have to spend time to run, agile process for the team has three requirements: self-management, self-organization, multi-functional, in the team to maximize the use of agile processes in order to improve our efficiency.
Seventh Chapter-MSF
In the seventh chapter, MSF, MSF, the Microsoft Solution Framework (Microsoft Solution Framework), is Microsoft's recommended software development. It's not like an agile process with a manifesto, but a framework of ideas.
Ideological framework--9 Basic principles:
1. Promote information sharing and communication
2. Work for a common vision
3. Full Authorization and trust
4. Co-responsible for the project
5. Value of delivery increment
6. Keep agile, anticipate and adapt to change
7. Investment Quality
8, learn all the experience
9. Cooperation with customers
The MSF Team Model MSF process model MSF Agile Development Model MSF CMMI Development model is the model mentioned in this chapter.
See here, I feel that each team will have differences, in some places may also have some conflict, from the book it seems that the concept of different will have a very complex relationship, but, I think this should be the self-cultivation of each programmer and the quality of completion of work, only in this way can get higher efficiency and quality.
The 6th to 7th chapter of the Law of construction