Creating a process template
A process template provides a new project area with an initial process configuration and iteration structure. When you create a project area, you must specify a process template.
You must be a member of the JazzAdmins group to perform this task. You can create a process template with no initial content, except the process configuration structure and placeholder iterations. Alternatively, you can create a process template from an existing project area and customize it. The latter option enables your team to create project areas based on a successful process that is implemented in an existing project.
1: Create template
- Perform one of the following steps:
- To create a process template with only placeholder content, right-click a repository connection in the Team Artifacts view and click .
- To create a process template from an existing project area, right-click a project area in the Team Artifacts view and click Extract Process Template.
- In the Create Process Template window, enter a name and a process ID for the template, and click Finish. The new process template opens in the Process Template editor.
2: Add or modify timelines and iterationsIn the Timelines section, add or modify timelines and iterations. To designate a timeline as the project timeline, select it and click , the Set the Selected Timeline as the Project Timeline toolbar icon. To set an iteration as the current iteration, select it and click , the Set the Selected Iteration as Current toolbar icon.
3: Add user rolesClick the Process Configuration tab. Click Roles. To add a role, click , the Create a new role toolbar icon. To indicate that the role is intended to be assigned to only one team member, set the Cardinality attribute to single. To indicate that the role is intended to be assigned to multiple team members, set the Cardinality attribute to many.
4: Assign project-level permissionsIn the Configuration pane, expand Project Configuration and click Permissions. For each of the roles, select the actions that users with that role are permitted to perform by selecting check boxes in the Permitted actions section. The permissions at this level apply to the global project context. They apply regardless of the current iteration or timeline, and they cannot be customized in specific team areas.
5: Assign team-level permissionsExpand Team Configuration and click Permissions. For each of the roles, select the permitted actions. The permissions at this level apply to all of the teams that belong to the project area. However, each team area can customize the permissions. You can also customize permissions for specific timelines, iterations, and iteration types.
6: Configure work item typesExpand Project Configuration, then expand Configuration Data and Work Items. Use the aspect editors in this section to define and configure the work item types that members of your project area will use to track their work. See Customizing work items.
7: Specify project area initialization actionsIn the Project Configuration section, click Project Area Initialization. You can specify follow-up actions to be executed when project areas based on this process template are created and initialized. For example, to have team areas created for the project area, click Add in the Server follow-up actions section, then select Create Team Areas. In the Team Hierarchy section, click Create Root to create a team area. You can specify additional team areas to be created at the root level. You can also select a root-level team area and click Create to create team area that is a child of that root-level team area.
8: Specify project-level preconditions and follow-up actionsIn the Project Configuration section, click Operation Behavior. For each role and operation, you can configure preconditions and follow-up actions. For example, you can specify a precondition on the Save personal dashboard operation that requires the user to be a member of the project area or team area. To configure a precondition or follow-up action for a role, select the cell for the role and operation. Select Preconditions and follow-up actions are configured for this operation. In the Preconditions or Follow-up actions section, click Add and select the precondition or follow-up action. To prevent other project areas that use this project area's process from overriding the setting, select Final (ignore customization of this operation in child areas). The operation behavior at this level applies to the global project context.
9: Specify team-level preconditions and follow-up actionsIn the Team Configuration section, click Operation Behavior. Configure preconditions and follow-up actions for roles and operations. The operation behavior at this level applies to all of the teams that belong to the project area. However, each team area can customize the operation behavior. You can also customize operation behavior for specific timelines, iterations, and iteration types.
Click Save to save the process template.
The new template is added to the Process Templates view. You can now create project areas based on the template.