TeamCompanion 4.2 released

Today we released new TeamCompanion v4.2 that comes with the upgrade of the agile project management features.

Here is the list of major new features.

1) Support for teams

2) Modified Backlog capacity charts, so they display iteration capacity in story points

3) Various enhancements

Let’s see what each of the entries from the above list is about.

 

1) Support for teams

Support for teams gives you ability to manage work for each team separately, including team wise backlog management, iteration planning and progress tracking.  You’re also still able to create a “super-team” that covers multiple smaller teams. That way TeamCompanion will let you manage team at different levels.

In order to create a team, user needs to provide following information defining the filter returning only work items belonging to that particular team:

  • Team Scope – only work items in this/these Area(s) will be visible as part of the “Plan and Prioritize” queries.
  • Team Members – only work items assigned to team members will be returned by query.
  • Team Iterations – select iterations this team is interested in. Usually you will here select the current iteration, a couple of previous iterations (to be able to follow the velocity) and next few iterations to facilitate planning.Additionally, here you will choose one iteration used for this team’s Backlog. 

Teams can be managed using the new “Manage Teams” action.

Ribbon

Using ribbon, you can always easily switch between teams or iterations that are part of some team.

Let’s take a look at a “Manage Teams” dialog:

ManageTeams_Overview

“Manage Teams” dialog can be used to create, delete or edit teams. First tab is primary used to define team scope (areas), but it can be used to define team administrators as well.

ManageTeams_Members

Second tab is used to manage team members. Using this tab they can be added, removed or assigned to some discipline (in order to facilitate management by disciplines where tasks are assigned to a discipline, instead of the management by particular team members). This tab is also used to define team administrators.

ManageTeams_Iterations

On the third tab, user can define backlog and team iterations. At least one backlog and team iteration must be selected. There may be multiple backlog iterations – work items from all of them appear in the team Backlog. The default Backlog iteration is the one used when a work item is returned back to the Backlog.

Once you define your team(s), you’ll be able to switch between them and to see charts and work items assigned to each particular team.

Iteration

 

2) Modified Backlog capacity charts, so that they display iteration capacity in story points

Starting with TeamCompanion v4.2, each sprint can be characterized not only with start and end date, but you can set the capacity of the team in that iteration as measured in story points. Note that the capacity in man/hours is calculated whereby the capacity in story points is simply set by the user.

This can be done using Capacity pane while some team and iteration are selected:

StoryPoints

Now when you open “Backlog plan” and select the iterations pane on the right side, you’ll see the capacity for that team for each iteration measured in story points.

Backlog

3) Various enhancements

TeamCompanion v4.2 comes with the bug fixes for the 66 known issues.  Also, we have further improved “Plan and Prioritize” performance.

 

Don’t wait, get the new TeamCompanion v4.2!

Go and grab your copy at www.teamcompanion.com\Download .

Watch all videos at www.teamcompanion.com\Video.

For all other information visit www.teamcompanion.com.

What others are saying.

No comments posted yet.

What do you have to say?

Title*
Name*
Email (never displayed)
(will show your gravatar)
Url
Comment*  
Please add 2 and 5 and type the answer here: