Scaling Development Teams with Pivotal Tracker

Scaling your development capacity can result in having multiple Development Teams. When using Scrum, the intent is to have one Product Owner managing one Product Backlog. With multiple Development Teams working on the same product, each Development Team has their own Sprint Backlog that they commit to for the duration of the iteration – the Sprint.

In turned out that Pivotal Tracker is not supporting this out of the box – One Product Backlog, multiple Sprint Backlogs. In this blog post I’m going to share how to organize Pivotal Tracker to support multiple Development Teams working on one Product Backlog.

LeSS Framework

I came across this challenge with my colleague Matthijs de Booij while investigating different Agile scaling frameworks. Based on our context we decided to experiment with the LeSS Framework.

Large-Scale Scrum (LeSS) is Scrum applied to many teams working together on one product. LeSS is (1) lightweight, (2) simple to understand, and (3) difficult to master—due to essential complexity.

 

LeSS Framework

During the investigation of the LeSS framework one of many topics we addressed was tooling to manage the Product Backlog. On the LeSS.works website the following information is posted about Product Backlog tools:

Use simple tools for the Product Backlog. We’ve seen LeSS Huge initiatives (with thousands of people) manage the Product Backlog with a simple spreadsheet. Avoid unnecessary and costly complication by using the simplest tools possible for managing the Product Backlog.

 

Here is a side note regarding tool usage in Scrum and in LeSS. It is common for organizations to look for tools to solve their problems even though tools are rarely the cause of the problem. Avoid solving problems with tools unless you truly, deeply understand the problem and consider a tool to be the the right solution for that particular problem.

Source: LeSS.Works

There is no real suggestions for tooling that works well with the LeSS framework. Since we have good experience with Pivotal Tracker we wanted to find out if it could fulfill our needs without making it unnecessary complicated.

Product Backlog

So the goal is to manage one Product Backlog (Pivotal Tracker calls this a project backlog) with multiple Sprint Backlogs. In Pivotal Tracker it is not possible to assign multiple teams to one Product Backlog, but there is the possibility to create workspaces that allows you to combine multiple “projects” in one overview. Within the workspace it is possible to move user stories from one project to another. The first step is to create a Pivotal project for the main Product Backlog and projects for each Development Team, serving as Sprint Backlogs.

Creating a workspace

On the main dashboard of Pivotal Tracker you can create a workspace. When creating the workspace you need to provide a name.

Projects-pivotal Projects-pivotal-workspace

After creating a workspace you have the ability to add projects and save this. The end result will be the current/backlog of the added projects in one overview.

Pivotal Workspace Add Pivotal Workspace Projects Pivotal-workspace-added

Please note: all the project needs to be configured the same like estimations scale otherwise it is not possible to move user stories to a different project.

User story flow

During Sprint Planning One the users stories of the Product Backlog will be distributed over the Sprint Backlogs for the upcoming sprint. Within the workspace you can move the user stories to the teams. After this is done, each Development Team can continue with Sprint Planning Two.

Pivotal-workspace-moving-story Pivotal-workspace-moving-story-moved

Velocity

For a Product Owner the velocity is an important metric. The velocity allows the Product Owner to prepare the upcoming sprints and provide timelines to stakeholders. This gets even more important when multiple teams are working on the same Product Backlog. Because user stories are moved from the Product Backlog to a Sprint Backlog , there won’t be an overall velocity available. Velocity will build up in each individual Sprint Backlogs because this is where the value is delivered. Within the Product Backlog there is no velocity and this will make it hard to prepare for the upcoming sprints and provide timelines. Because this functionality in unavailable in Pivotal Tracker, we created a work-around to force the velocity in the Product Backlog. By resetting the starting date of the Product Backlog each sprint and setting the initial starting velocity to the total velocity of all the teams you will get an estimation of how much can be delivered during a Sprint. This is very useful for Release and Sprint Planning.

Projects-pivotal-properties

 

Pivotal-workspace-velocity

Automation

Resetting the velocity in the Product Backlog every Sprint can be annoying but luckily Pivotal Tracker has a great API which we can use for adjusting the settings. In order to automatically reset the start date and velocity of the Product Backlog you can use this powershell script.

When running the script output will be displayed and Pivotal Tracker provides a message to reload the workspace because of changes.

Pivotal-project-reload

Conclusion

When multiple Development Teams are working on one Product Backlog, you want each Development Team to have their own Sprint Backlog, and you will need the overall estimated velocity in order to plan Sprints and releases.

Pivotal-workspace-moving-story-movedI would love to have this supported in Pivotal Tracker out of the box, for example by linking projects and combining the velocity in the Product Backlog. Luckily Pivotal Tracker has an API which can be used to apply the work around. I hope you find this useful and if you have questions or comments please feel free to contact me.