Building the Law--team & Scrum & MSF

Fifth chapter (Team and process) 83-99  

This chapter mainly introduces the team spirit

Does that mean that as long as you can group together, you make a team? In fact, software teams have various forms that apply to different people and needs. For their team to win!

A good team process can release the positive aspects of the conflict (each trying to do their job well, persuade others) and avoid negative aspects (negative, conflicting emotions, etc.) that arise from the conflict. We cannot relax our demands because of the team-mates, because the quality of each person's work directly affects the quality of the final software, and when all the high-quality work is combined, it is possible to achieve a good team quality work project.

There are many types of software team models: Attending physician mode, star mode, community mode, amateur theatre model, secret Team mode, Agent team mode, Symphony mode, jazz mode, functional team mode, and bureaucratic model. Each team can not be directed at the most profitable and self-created patterns or patterns, suitable for their team and project requirements is the most important. So how to strengthen cooperation with others? In an organization, most of the time, the members of the cooperation is not what we can choose, so it is likely that the group members of the various aspects of the ability to be uneven, if as a leader, at this time need a good cohesion ability, can put the characteristics of most of the members of the various aspects of cohesion together, It also requires leaders to have a good ability to interact and communicate with different people. If leaders do not set an example at the outset to do all aspects of the work, there will be many undesirable consequences.

Therefore, learn to cooperate with others, play a team spirit in the specific life of the use, can make us receive a multiplier effect, can make our work more well forward development.

• Sixth chapter (Agile process) 100-119

"Agile Processes" are a collection of values and methodologies that have been affirmed by some experts in the software community.

In 6.1.1 , there is the principle of agile development, one of which says "frequent release of software available, the release interval can be from a few weeks to a few months, can be short," then, is it possible to map the problem to our usual computer or phone software updates? I believe everyone will encounter such a confusion, our computer and mobile phone will pop up a box from time to time to remind us to update the version of the system software, but, the version is updated so frequently, those software needs our updated software, if we update, the software is really new? Will there be a better experience? The answer is different, because as a user of us, from the actual combat can be drawn, sometimes some software update is only very small, after the update almost can not find any big changes, this time will let some users feel that the company is in the "cheat traffic or cheat clicks." These are individual, because sometimes some software updates can really make users more convenient or have greater visual impact shock.

Agile's scope of application is limited, agile requirements for the team is simple: self-management (self-managing), self-management (self-organizing), multi-functional (cross-functional), the average person can not immediately do this, it is not "silver bullet", does not solve all the problems of software development, so the agile approach is not omnipotent, it can help you know earlier whether you can complete the task as scheduled, that is, when is it appropriate to choose agile? This depends on the actual needs of different users and different projects, so we cannot rely too much on agile practices.

• Chapter Seventh (MSF) 120-140

What is MSF? It is actually Microsoft's recommended way to do software-Microsoft Solution FRAMEWORK,MSF.

I appreciate the nine basic principles of MSF: to promote information sharing and communication, to work for a common vision, to be fully empowered and trusted, to be responsible for the project, to deliver incremental value, to maintain agility, anticipate and adapt to change, to invest in quality, to learn all the experience, to work with customers.

With MSF planning so reasonable, is it possible to be free? The answer goes without saying that MSF is trained worldwide by Microsoft Consulting and Microsoft Certified Training Centers, and it is evolving, it is a framework, it is not immutable. Instead, MSF continues to evolve and refine as we learn from Microsoft's customers and partners, and new ideas and guidelines are constantly being introduced to MSF. These developments will adapt to technological updates, changes in business needs, and support for building better software solutions.

MSF focuses on the team model, which demonstrates how to organize project teams to deliver system solutions efficiently and with time-controlled and continuous development initiatives. It describes six basic roles (product management, project management, development, release management, testing, user experience). In the MSF Team Model, any technical project must meet specific key quality objectives to be considered a successful project. No one role can achieve its goals, all of which will risk the entire project. Therefore, each role is considered equally important and important decisions are made together.

Building the Law--team & Scrum & MSF