After having installed TeamPulse the first thing a user is going to have to do is create a new project. Creating a new project presents the important decision of choosing a template for the project. Once a project is created you cannot change the template later so the decision is one not to be taken lightly. After reading this blog post you will understand what is a project template in TeamPulse as well as understand each of the different project templates available in order to be capable of choosing the correct template for your project.
A project template in TeamPulse is a definition of how your project will behave. If you are familiar with project templates in Team Foundation Server (TFS) then the concept is the same. Templates define the following aspects of your project:
The list of possible statuses that stories and tasks can have as well as the valid transitions between the statuses
Which statuses are to be considered as indicating that the story and task is “Done”; This is necessary for a number of features in TeamPulse including reporting and our Dashboard
Which statuses are to be excluded when calculating things such as percent complete, for example the TeamPulse template would exclude “Deferred” and “Deleted” statuses
Validation rules for stories and tasks
Allowed value rules for various properties of stories and tasks
Which status values to display on the story board
This information is defined as XML in our database. By defining all of this information in a declarative way it opens up many possibilities such as one day having the ability to modify the templates to suite your individual team needs or to create brand new templates from scratch.
The project creation screen gives the option of 6 projects templates:
The default choice is the TeamPulse template. The other templates represent those that are available to TFS users. Let’s go into each template in detail so that it’ll be clear that you’ll know what you’re getting when you make your choice. In general, if you ever intend to sync your project with TFS then you will want to choose the template that corresponds to the target TFS project.
This template was designed and used internally with much success by the TeamPulse team.
This template allows you to organize and track the progress and health of a small- to medium-sized Agile project.
This template allows you to organize and track the progress and health of projects that require a framework for process improvement.
This template encompasses the statuses of the Scrum TFS template provided by EMC. Scrum is an agile process that can be used to manage software and product development using an iterative process.
This template has the same underpinnings as the 2008 one but provides an updated version of the EMC template.
This template allows you to organize and track the progress and health of a small- to medium-sized Scrum project.
And there you have it! With the detail provided above you will know exactly what you are getting when you select a template. At the moment we aren’t supporting modifying these templates or creating new ones however you can be sure that we are working on making this available to you in an upcoming release.
As always, let us know what you think. We’d love to hear from you!
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.