TFS (Team Foundation server) agile use tutorial (III): customizing agile process templates

Agile Process Template

Team Foundation server 2010Two built-in process templates, althoughTFSThe process help documentation, but Microsoft does not provide the practices and examples we need most. We always use"MSF for Agile Software Development V5.0"For a long time, we have tried our best to adapt to this template and use it as a standard. However, we gradually find that this process template is not consistent with our actual development work. On the one hand, this template is just a perfect product, which is quite different from the characteristics of Chinese-style software; on the other hand, continuous improvement of software processes is a constant rule, and the current work characteristics must be consistent with the current situation of the Process Template, rather than one step in place.

Start Visual Studio 2010, open "Team \ team project set Settings \ Process Template manager", and download"MSF for Agile Software Development V5.0"To the local folder.

Download team Foundation server power tools. After installation, Run "tool \ process editor \ process Templates \ Open Process Template" in Visual Studio."MSF for Agile Software Development V5.0.

 

1 iteration (iterations)

The first stage of a team project is "iteration ".1"," IterationN"And so on. In addition, a special iteration is added: "backlog"(Backlog), Unplanned, unclear, and urgent work items are temporarily put into the "backlog". With the progress of the project and the requirements of the customer, the work items in the "backlog" are arranged in the "iteration"N.

Group)

Add three groups:Developers (Developer),Support (Technical Support),Testers (Tester)

3. Team queries)

As shown in the default team query generated by the agile process template, it looks complicated. We have customized a new query and used it for two years. Finally, we summarized the most common queries, the infrequently used queries are all deleted.

Figure 1 before modification Figure 2 after modification

3.1 modify Query

3.2 All my jobs

This query reflects personal attention and serves as an entry to the project member's work. It displays the user scenarios, tasks, problems, and bugs assigned to all projects in a table, this allows him to quickly and easily view his tasks, such as new tasks, unfinished tasks, and high-priority tasks. Practice has found that this method is more effective than asking him to search for "My tasks" and "my bugs" in various projects, this is especially true for multi-project parallel development and cross-department collaboration.

 

 

3.3 All jobs

This query shows the project's focus on all the work items of the project and the parent-child relationship between the work items.

4. Work Item)
 

4.1 default work item)

Tfs2010 supports the hierarchy of work items, so that when there are a lot of work items, it is not as messy as tfs2008. Therefore, we need to manually create identical top-level summary tasks in each new team project. repetitive work is coming again. It is our duty to eliminate repetitive work and improve the automation level, add it to the default work item directly. It is a small pity that a parent-child relationship cannot be established and can only be manually completed after a team project is created.

 

4.2 work item type (work item type)

I didn't want to customize the work item type, but agile process templates do not support "Start Date" and "completion date". If you want to set the "completion date" of the work item ", you can also use office project to open TFs to modify the "completion date ". This is too agile. Open the "Type Definitions" Edit task and add "Start Date" and "completion date ".

Preview and see the results. It looks quite appropriate! Since the two fields are put out, comfort has increased by 20%.

 

Finally, rename the modified process template :"MSF for Agile Software Development v5.1", Open the Process Template manager again and upload it to the server.

Code download