Agile/scrum Mode development based on Visual Studio 2010

According to a study by Forrester Research in the second quarter of this year, 10.9% of the more than 1000 professional developers who use the Agile model for software development have adopted the scrum model, ranking first in all agile development models, In all software project management models, the agile model is used by 35% of developers. Of course, the research report presents us with just a statistical view of what development models your development team should adopt, depending on their different development environments, staffing, corporate structure, and cultural background.

Figure 1:forrester Investigation report on the Agile model

Visual Studio 2010 is a new generation of integrated development environments released by Microsoft in April 2010, in conjunction with Team Foundation Server (tfs--), Provides a comprehensive application lifecycle management (ALM) tool and platform for the development team. In the 2010 version, support for agility, or the scrum model, is unprecedented. Although Microsoft's Visual Studio Team System has provided an Agile process template (the MSF Agile) template since its release in 2005, the Agile process template before release 2008 is based on the MSF (Microsoft Solution Framework) This framework is a summary of Microsoft's best practices for its own research and development team, and it does not fit well with many of the agile methods prevalent in the agile development community, creating a lot of areas where the development team is not applicable when implemented. So, in developing the 2010 version, Microsoft has heard a lot of voices in the agile development Community, and has done a lot of agile in its own MSF Agile 5.0 template, and more specifically the scrum development model, enabling the MSF Agile integrated in version 2010 The 5.0 template is perfect for our scrum model development organization. Of course, Microsoft's products, in pursuit of versatility, did not fully adopt the scrum-style name and process in the MSF Agile 5.0 template, and Microsoft released a pure Scrum process template for use by a development team that wanted to fully use the scrum model two weeks ago. Of course, this template is still a beta version now.

I personally think that the development team to adopt which template is not the most important, it is important that we need to continuously improve the process in the development process, and to customize the template to fit our own development process. That's why TFS provides a template, because it's designed to keep improving on the basis of this template and ultimately find the right

The process of developing your own team. In fact, this is also consistent with the idea of the scrum model; to put it simply, the scrum pattern is a framework for the process organization of complex projects, with the goal of developing higher quality software products. Around this goal, the scrum model provides us with a team model, a series of tools, and a simple process. Under such a framework, the scrum model requires that we continually improve the process to fit the best of the team, and that the requirement for improvement is one of the important features of the scrum pattern that distinguishes it from other development processes.

Why is the scrum model appropriate for software development?

Software industry has been more than 40 years of history, a lot of software engineering management methods are constantly groping in the improvement. The early software industry due to limited size, the vast majority of the workshop type, several people together by their own ingenuity to create software products; But as the team expands, developers begin to need a model to organize an increasingly large team to meet increasingly complex requirements. Because there is no experience to follow, the software development team has a lot of traditional industrial engineering methods for reference to the software industry, thus appearing like "Waterfall" model. The waterfall model requires that we do a lot of careful design and planning before the actual development work, trying to refine the uncontrollable development process into controllable particles to achieve the overall control of complex projects. But the "waterfall" model ignores one of the essential features of software projects, that is, the uncertainty of demand; we can't make cars like we did on the production line. All the parts are well designed, all the procedures are set and then assembled. Because no one knows how the code should be implemented until it is actually coded, and each developer's level is different, the custom is different, the code written is different, plus the customer's demand for software is changing, the business process a year ago is likely to change after a year, If you also follow the previous requirements of development, then the delivery must not meet the requirements; More importantly, they can never tell you exactly what they want until they see or actually operate the SOFTWARE PRODUCT. For all these reasons, software development is unlikely to be organized using traditional engineering methods, because it is an exploratory sexual act that relies on the wisdom of developers, and a large part of our software projects fail.

The scrum model is based on the understanding of the nature of software development behavior, provides a loose framework, let us use an exploratory process approach to organize the development process is an exploratory, fundamentally meet the software development itself for the process requirements. This methodology is in fact based on the management of the Deming Ring proposed by Edward Deming; Deming Cycle theory suggests that the most effective process by which humans can succeed in any complex activity is through: Plan plans –do perform –check check –act improvements, four sub processes, and iterative to find the best way to solve the problem. This theory is not aimed at software development, but software development itself is actually the most typical complex activity.

Diagram 2:scrum Process