The hoops we ask people to jump through for ask mode...

  • Article

Next week, every bug that C# checks in to Whidbey Beta2 will have to be approved by our triage team. To simplify this process a little, we ask teams to come to us with a template of information already filled out about the bug. This makes discussion really fast. Whats in the template (hint...Doom!)...

Customer Problem.

We ask the dev to describe what the specific user scenario the customer runs into. This is to stop the inevitable explanation "We need to fix our CList data structure because you can have an infinite recursion". Statements like this are met with arched eyebrows and steely eyes that state "so what...does this affect the customer somehow". This is thus filled out with something like- "the customer loads his project, types blah de blah, opens class view, and his nodes are missing". This description is very important as it allows us to make decisions whether this is a mainline scenario, or something less common and hence puntable. ****

Workarounds.

Are there any workarounds to this problem? If there are, maybe some might be acceptable to the user. If there arent, it makes the problem a little more stark. ****

Regression.

Is this a regression from Everett? If we break a users experience from Everett, it might be an adoption blocker and hence something we need to fix. ****

Affected Dll’s.

A list of the dll’s affected by this fix. This is done mostly to assess the scope of the fix. ****

Dependencies.

A list of all teams affected by this change. Often we need to make sure we contact these guys to see if they are ok with this change. ****

Code Review.

We require one before checkin.

Test Signoff. We require QA to signoff on the fix before checkin.

Why wasnt this found earlier. We ask this to cover up test holes we might have.

Security Impact.

To make sure there isnt a security downside to the checkin. ****

UX Impact.

UX is user experience, but this is to make sure we can alert our document guys, designers and localizers of any string changes, dialog changes etc.

Cost. How many days of work is this for Dev, QA, PM?

Risk.

Is this a risky change? ****

Performance impact.

Is there any performance impact for this fix?

Shaykat