Defining the Initial Areas and Iterations in the Classification Plug-in

You define classifications to facilitate tracking, grouping, and reporting on work based on useful categories, such as related product features and project milestones. You define areas to organize work items into logical, physical, or functional categories. You define iterations to group work items into milestones or time cycle categories. For example, a team could organize the product work into a client area, a server area, and an extensibility area. Iterations that you define determine how many times the team will repeat a particular set of major activities, such as plan, develop, and test.

The classifications that you define appear in the Areas and Iteration dialog box for the new team project, as the following illustration shows:

After a team project has been created, you can use any client application for Team Foundation to modify the areas and iterations. You can also define permissions to control access to a project area or iteration. For guidelines and naming restrictions that apply to classifications, see Create and Modify Areas and Iterations. For information about the fields that track areas and iterations, see Areas and Iterations

In addition to areas and iterations, you specify the mapping file for Microsoft Project to upload within the Classification plug-in.

In this topic

• Classification Plug-in Name and Location

• Classification Tasks and Dependencies

• Specifying the Initial Product Areas

• Specifying the Initial Iterations

• Specifying the Microsoft Office Project Field Mapping File to Upload

• Classification Plug-in Element Reference

Classification Plug-in Name and Location

The following table lists the name of the file, the folder, and the plug-in for the process templates for Microsoft Solutions Framework (MSF):

Back to top

Classification Tasks and Dependencies

The Classification plug-in file must conform to its schema definition, as specified in the Css.xsd file, and the plug-in must be specified in its own file. You can download the schema files for process templates from the following page on the Microsoft website: Process Template and Work Item Schemas for Visual Studio Team Foundation.

In the XML file, you specify one or more tasks and their dependencies. In general, you only need one task to specify all the iterations and nodes that a team project requires.

Back to top

Specifying the Initial Product Areas

You specify the root node of areas by using the following syntax:

<Node StructureType="ProjectModelHierarchy" Name="Area" >

You specify zero or more children nodes for as many areas as you want for your process. You use the Node element to specify each area, and you set the StructureType attribute to ProjectModelHierarchy.

<Node StructureType="ProjectModelHierarchy" Name="NodeName" ></Node>

The following example shows how to specify two areas, Client and Server:

<?xml version="1.0" encoding="utf-8" ?>
<tasks>
   <task
      id="UploadStructure"
      name="Creating project structure"
      plugin="Microsoft.ProjectCreationWizard.Classification"
      completionMessage="Portfolio project structure created.">
      <taskXml>
         <Nodes>
            <Node StructureType="ProjectModelHierarchy" Name="Teams" >
               <Children>
                  <Node StructureType="ProjectModelHierarchy" Name="Client"></Node>
                  <Node StructureType="ProjectModelHierarchy" Name="Server"></Node>
               </Children>
            </Node>
         </Nodes>
      </taskXml>
   </task>
</tasks>

Back to top

Specifying the Initial Iteration Paths

You specify the root node for iterations by using the following syntax:

<Node StructureType="ProjectLifecycle" Name="NodeName" >

You specify zero or more children nodes for as many iterations as you want for your process. You use the Node element to specify each iteration, and you set the StructureType attribute to ProjectLifecycle.

The following example shows how to specify four iterations: Milestone 1, Milestone 2, Beta, and RTM.

<?xml version="1.0" encoding="utf-8" ?>
<tasks>
   <task
      id="UploadStructure"
      name="Creating project structure"
      plugin="Microsoft.ProjectCreationWizard.Classification"
      completionMessage="Team project structure created.">
      <taskXml>
         <Nodes>
            <Node StructureType="ProjectLifecycle" Name="Iteration" >
               <Children>
                  <Node StructureType="ProjectLifecycle" Name="Milestone 1"></Node>
                  <Node StructureType="ProjectLifecycle" Name="Milestone 2"></Node>
                  <Node StructureType="ProjectLifecycle" Name="Beta"></Node>
                  <Node StructureType="ProjectLifecycle" Name="RTM"></Node>
               </Children>
            </Node>
         </Nodes>
      </taskXml>
   </task>
</tasks>

Back to top

Specifying the Field Mapping File for Microsoft Project

You specify the file that contains the field mappings for Microsoft Project in the properties section of the Classification.xml file. You use the property element to specify the file to upload, which is labeled FileMapping.xml for MSF process templates. This file contains the mappings between fields in Microsoft Project and fields in Team Foundation. This file is uploaded to the database for the team project. The following example shows the syntax structure for this entry:

<properties>
   <property name="MSPROJ" 
             value="Classification\FileMapping.xml" 
             isFile="true" />
</properties>

To customize this file, see Mapping Microsoft Project Fields to Team Foundation Fields.

Back to top

Classification Plug-in Element Reference

The following table describes the elements that you use to define the initial product areas and iterations. You specify these elements within a taskXml container element in the Classification plug-in file. For information about this element, see Defining the Tasks to Process a Plug-in.

You define areas and iterations by specifying a tree path of nested nodes and children nodes. For more information, see Restrictions on Area and Iteration Paths.

<Children>
    <Node> . . . </Node>
</Children>

<Node StructureType="ProjectLifecycle | ProjectModelHierarchy" Name="NodeName">
   <Node> . . . </Node>
   <Children> . . . </Children>
</Node>

<Nodes>
   <Node> . . . </Node>
</Nodes>

<properties>
   <property />
</properties>

<property name="property name" value="Classification\FileName" isFile="true | false" />

Back to top

See Also

Tasks

Verify Classification Changes

Concepts

Create and Modify Areas and Iterations

Customizing Functional Areas within a Process Template

Change History