Driving to ZBB

With the successful release of Whidbey Beta1 a few weeks ago, we’re now moving toward Beta2. The next key milestone between now and Beta2 is “ZBB.”  It is critical to close down on open issues during the drive to ZBB, because doing so significantly impacts our execution efficiency for months to come. Hitting this deliverable…

18

In the home stretch….

Wow! It’s hard to believe but we’ve completed 5 weeks of “Ask Mode”.  Every day for the past 5 weeks, representatives of each product team in the Division have met daily for 2 to 3 hours reviewing each change that is going into the product.  We look first at the customer scenario that is being…

18

Product Unit Reviews

We’ve been driving our bug counts down over the past few months, with an eye on what we call ZBB. We “went dark” a few weeks back, which had a significant impact on the overall bug count and really improved the quality of the product. We’ve fixed a tremendous number of bugs and have only…

6

Whidbey Security Push Progress

The past few weeks have been pretty busy for me. In my last blog I mentioned I was working on planning our “Security Push”, which is a time we allocate in our product cycle where the top priority and focus is security. Having this kind of time is very valuable because you can get everyone…

5

DCRs and Breaking Changes

Have you ever been asked to change something when you felt you were done?  It happens; customers provide feedback, security reviews reveal vulnerabilities in a design…there’s always a reason for a change.  A “DCR” is a Design Change Request and are designed to track these types of change requests to the original design.  Often DCRs…

5

Product Metrics/Release Criteria

As we drive towards Whidbey Beta 2, the Product Metrics/Release Criteria are a main guiding principle in assuring we are shipping the right quality product.  These metrics/criteria are made up of a number of goals and test coverage requirements (approx. 40) which were defined during Beta 1.  Some examples are: ·         Stress goals that ensure…

5

Whidbey Beta 2 Tell Mode

Two weeks ago, we entered a phase of the Beta 2 product cycle we call “Tell Mode”.  This is the point which marks the transition to the end game for Beta 2.  Here’s what has happened so far, and an idea of what’s to come for Beta 2.   ZBB: 11/19/2004 Security Push: 11/15/2004 through…

5

Whidbey Community Technology Previews (CTP)

Most of you are already aware of the Visual Studio 2005 Community Technology Previews (CTP) and are familiar with the philosophy and benefits of the CTPs – you get working bits more frequently, great opportunity for feedback from you to the product teams (using Ladybug), potential of finding issues earlier than RTM, ability for you…

5

Starting Ask Mode!

Check off another mini-milestone for Whidbey! Beta 2 Tell Mode is over, and we started “Ask Mode” today.  Over the course of the last week, we finished up a round of what we called “aggressive” integrations of the source code branches and are currently in the process of moving to a single Beta 2 branch…

4

Whidbey Beta 2 “Broad Go-Live”

One of the things we are doing in Whidbey Beta 2 is providing a broad Go-Live License agreement.  Some of you may remember we provided an ASP.NET Go-Live License with the Beta 2 release of the .NET Framework 1.0, from an old blog post by Scott Guthrie.  We view this as a terrific way to help…

4