MSF for agile thinking (reference msfguildline)

MSF is not only a group of activities to be followed. It tries to create a culture that promotes project success. The way of thinking is a collection of values that determine how the team interprets and responds to the situation. Whether it is a decision, determining the priority of the work, indicating the role group or communicating with team members and other shareholders, each team member should keep in mind the way of thinking throughout the project. There are eight ways of thinking in MSF.

Customer Quality Evaluation-Customer satisfaction is the highest priority for any outstanding team. This includes satisfaction from internal and external customers. Customer-centric in development, which means the team is committed to understanding and solving the customer's business problems. Once you understand the business issues, you must maximize the customer's participation to ensure that the customer's expectations are consistent with the project. Support for setting and managing customer expectations includes: To-Do report tasks, small batch generation, and high-quality products.

Professionalism-Proud to contribute to the solution, which is an important factor in creating high-quality products. This is a source of pride in motivation and responsibility. It is the responsibility of individuals and organizations to establish a professional and happy business philosophy. Methods that help maintain this sense of ownership include bottom-up evaluation, project code identification to clearly identify the project, and team functions.I personally think that only by establishing a good incentive mechanism (including training, personal career development space opportunities, material rewards) and good communication can we be able to achieve professionalism.

Equal team-The "equal team" mentality gives each role group the same value. This mindset requires unrestricted communication between roles, transparency, and a single visible To-Do schedule. The result is to enhance the Team responsibility mechanism and reach effective communication.

Frequent delivery-There is nothing more reliable than frequent delivery. It is very important to have products that can be submitted on a daily basis. In addition, to respond to customer requirements with high-quality small-scale delivery products, this shows the progress of the project. Through frequent delivery, the process and infrastructure can be verified and improved. Risks, bugs, and omissions can be identified in the early stages. Feedback can be provided when exceptions are found. Key Points of frequent delivery are: keeping small batches of delivery, "real-time" delivery, and leaving some options for future post-processing by eliminating immature decisions. Frequent delivery should be a way of thinking that goes deep into the concept of the software development team.Vstf is responsible for its trivial management and organization of various documents, greatly reducing the cost of project management and communication and greatly improving the efficiency.

Willing to learn-Each Development Project, environment, and team has their own characteristics. Therefore, iteration in each project and project can create learning opportunities. However, without honest feedback and reflection, you may not be able to learn. Unless there is a supported environment that encourages brave behaviors and protects personal privacy, feedback will be restricted and will not improve. Once these factors are met, individuals and teams can focus on continuous self-improvement, collecting and sharing knowledge and learning useful experiences. In addition, you can also implement the practices verified by others and arrange time learning in projects. The methods required for establishing feedback for a learning mindset include Cooperative Review and efficient review.

Start practical work as soon as possible-Too many projects delay too much time in the "big" direction, but cannot solve the problems that can be solved. This way of thinking emphasizes taking one step at a time to learn from the specific situation rather than abstraction. Defining a project by day is critical to effectively generating work code, testing, and creating a product that can be submitted. Another aspect that can be learned from specific situations is in the deployment process. Methods that support this approach include: People, solutions, deployment-oriented design, and test cases.

Service quality-Examine the solution in the way of service quality thinking, and develop plans based on various aspects of the customer experience. The concept is that service quality (such as performance and security) should not be considered in the later stage of the project, but service quality should be considered throughout the project. If these service quality are ignored, the customer will eventually be dissatisfied, and these service quality usually lead to some implicit assumptions about how the solution works. Using this way of thinking, you can examine the overall situation and turn implicit assumptions into clear service quality requirements. Methods that support this approach include using expert advice when necessary and identifying risks as early as possible.

Rights and Responsibilities-The responsibility-based approach focuses on the management of enterprise, project, and computing resources. Rights and responsibilities are manifested in many aspects, from effectively guiding projects to optimizing the use of web services. Support for Rights and Responsibilities includes: Re-assigning bugs with all necessary information so that others can immediately start to solve the problem or provide a good estimate of the workload of development or test tasks.