How Microsoft/DevDiv uses TFS - Chapter 3 (Implementing the Process)
In previous posts and I talked about out processes. Today I'm going to introduce how we implemented our processes using TFS.
In review, our process looks something like this. Read this post, for more information on the process.
We used work items to tracking the above information.
The Value Proposition work item
Note the following:
- The Scenarios are implemented by creating a Scenario field on the Value Prop work item, and setting ALLOWEDVALUES to the list of Scenarios. Since Scenarios (aka Pillars or Business Objectives) were small in number and fairly fixed as to what they were, this seemed appropriate.
- The relationship between Value Props and Experiences were tracked by linking Value Prop work items to Experience work items.
- The Value Prop has several fields to define the Value Prop, most notably the Description field to describe what the Value Prop was.
The Experience work item
Note the following
- Experiences are linked up to Value Props
- Experiences are linked down to Features
The Feature work item
Note the following:
- Features are linked up to Experiences
- The feature has many fields defining it. The Description field gives the curious browser a short description of the feature.
- For more information, a person can go to the One Page spec on the feature. An URL is provided in the field.
What's next...
Will talk about how the planning process worked in Orcas.
