Agile Software Development for the Entire Project


Team System’s Randy Miller has an article in this month’s issue of CrossTalk: The Journal of Defense Software Engineering. In it, he discusses Microsoft’s internal use of personas, shadow applications, and test thresholds to achieve a more agile software development process, which are also reflected in MSF for Agile Software Development.



STSC CrossTalk - Agile Software Development for the Entire Project - Dec 2005


Agile Software Development for the Entire Project
Granville Miller, Microsoft

Does an agile software development process require real organizational change or can an existing organization become more agile? How do the many traditional information technology (IT) roles such as the business analyst, architect, and tester become a more integrated part of an agile process? Some recent work [1] debunks the myths that agile processes require on-site customers, produce ad-hoc requirements and design, and cannot scale to large projects. This article furthers this work by introducing innovative techniques from a new agile process developed and used by projects within Microsoft. These techniques span the traditional IT roles such as the business analyst, project manager, architect, developer, tester, and release manager.

Comments (0)

Skip to main content