Extreme programming explained: embrace change
Extreme programming explained: embrace change
Adaptive software development: a collaborative approach to managing complex systems
Adaptive software development: a collaborative approach to managing complex systems
A Practical Guide to Feature-Driven Development
A Practical Guide to Feature-Driven Development
New directions on agile methods: a comparative analysis
Proceedings of the 25th International Conference on Software Engineering
Toward a conceptual framework of agile methods: a study of agility in different disciplines
Proceedings of the 2004 ACM workshop on Interdisciplinary software engineering research
Use of relative code churn measures to predict system defect density
Proceedings of the 27th international conference on Software engineering
Software quality development and assurance in RUP, MSF and XP: a comparative study
3-WoSQ Proceedings of the third workshop on Software quality
Formalizing Agility: An Agile Organization's Journey toward CMMI Accreditation
ADC '05 Proceedings of the Agile Development Conference
ADC '05 Proceedings of the Agile Development Conference
Software Engineering with Microsoft Visual Studio Team System (Microsoft .NET Development Series)
Software Engineering with Microsoft Visual Studio Team System (Microsoft .NET Development Series)
| Hi-index | 0.00 |
Increasingly many software development organizations must pursue at least a level 3 CMMI certification to compete in the marketplace. Not all software organizations are under this constraint, but the CMMI model offers benefit beyond just a marketing advantage. Agile methods have taken hold in many of the same organizations that stand to gain benefit from CMMI. CMMI adds some stress to the Agile approach by nature of more detailed planning and tracking. Microsoft and other software development organizations have endeavored to automate the more tedious aspects of CMMI, thus making it easier to support agile approaches within more rigid frameworks. The Microsoft Solutions Framework (MSF) initially founded on Microsoft software best practices observed internally and externally has expanded to integrate automated software configuration for team projects. The Team Foundation Server (TFS) product leverages MSF and supports both CMMI and Agile as process templates and provides tools around these templates to automate the use of either approach. In this paper, we explore how Microsoft has integrated these approaches into TFS, the rationale and implications for selecting one approach over another and how agile practices can be integrated into a CMMI framework.