The method of construction reading notes

We have learned the principles and outlines of agile processes, and we can all appreciate the benefits and benefits of agile processes, but agile processes are not necessarily suitable for all project tasks, so let's continue to understand agile processes.

MSF is Microsoft's methodology for software development, Microsoft's solution framework, and Microsoft's recommended software development approach. And MSF has its own basic principles. 1. Promote information sharing and communication, which means keeping and disclosing all of the information. 2 "Work for a common vision, to do this, it is necessary to set a clear goal, and this goal for the members of the daily work has a guiding role 3" full authorization and trust, which will be our team members are equal cooperation, we have to fully empower the team and members. 4 "Each of the responsibilities of the project, to clear the responsibility of each person, out of the question to be responsible for 5" value business values, provide incremental value, which requires us to say clearly what our products solve the problem, for whom to solve the problem, why solve these problems 6 "maintain agility, anticipation and adaptation to change, Software development process is a lot of changes, we want to keep agile, anticipate and adapt to change 7 "Quality of investment, this principle tells us that investment to talk about efficiency, investment to talk about timing, investment is long 8" learning all the experience of the MSF Team Model, it defines the team peer members of some roles and responsibilities,  In this model, each role has an extremely important role, and if a role does not accomplish the goal, it can endanger the entire project. MSF also has an agile development model that emphasizes communication with users. Pay attention to quality and do it in the bud.  It also emphasizes the quality under actual combat conditions, and it streamlines the process and goes straight to the subject. MSF also supports CMMIC capability set Maturity Model integration, which greatly increases the quality of the project and the scheduled completion rate.

Agile to the team's requirements is simple: self-management, self-organization, multi-functional, but "self-management" is not equal to "no management", their own selection of tasks, after each end to summarize the deficiencies, propose improvements; and now everyone is going to unite to be responsible for the project, everyone is fully responsible for the specification, Communicate with others and take care of your own tests. Teams need to have the strength and level to be able to use agile processes, otherwise they can backfire and often require multiple sprints to get scrum on track.

We need to learn to measure whether a development process is appropriate for the current project or team, and the team also needs a strong project manager. Agile processes take a divide-and-conquer approach to the many requirements of a project, allowing the relevant people to focus on solving some of the problems within a certain period of time, emphasizing short iterations, summarizing in iterations, and improving the team's processes and product capabilities.

According to the experience of such a long period of time, agile shows only a few priorities, not as rules or dogma; Agile processes are not perfect, so when it comes to complex projects, the development process is decided according to the actual situation.

Agile processes are good, but they are based on the actual situation of the project, complexity, team characteristics to determine the development method.

The method of construction reading notes