Key Points

• Businesses are becoming internet-centric. This presents several challenges to a traditionally organized test team.
• Microsoft's WebData Team (which delivers XML) has shifted to this model and is a good case study for successful change.
• Focusing on web-centric delivery mechanisms and timelines required a complete redesign of our processes.

Presentation Abstract

Gone are the days when developers are willing to wait six months to glimpse new features. E-businesses need solutions to data access problems yesterday. They want to hear about whatÆs coming down the pike, they want to see why itÆs valuable to them, and they want to know how theyÆll be able to use it. 

WebData was structured to accommodate the typical release model: spec, design, code, test, beta, release. As a component group, we had several major commitments to battleship projects, including Office, SQL, and Windows« 2000. We were moderately insolated from our customers and structured to deliver at what we would now consider the leisurely pace of every 3û4 months. When we initially asked our sub-teams about moving to the faster WebRelease strategy, we heard screams of agony, ôHow do you expect us to ship more frequently? WeÆre already breaking our necks!ö We realized that our approach to change would need to be organic, credible, and revolutionary.

About the Author