Backlog Aggregator: why

Long story short : it is three years I am working in an agile team (two years as Scrum Master) . Initially, the team was supposed to be a pilot for the company and because of some results we brought, it was decided to migrate other teams in an agile approach .

In the spirit of the methodology, each team have had the possibility to self-organizing; after that, they chose which tools ( electronic or not) they could use to optimize their work.

The result of this approach has inevitably caused the use of different tools just to manage the backlog and this has made it incredibly difficult for the stakeholders to have an overall view of the progress of the various projects.

To avoid having multiple accounts on different tools, the boss has proposed to create an aggregator of backlog and has gathered a few of us from different teams to work on this project with a “best effort” approach, that was in addition to the daily activities that each of us should carry on.

This new team decided obviously an iterative approach: we started a month ago and we were able to spend only a few tens of hours (at least I ) to the activity .

At present time the aim of the game is to get from the various online tools the stories of each backlog.

For now we have to deal with: Pivotaltracker, Easybacklog, TFS, Trello .

My former team is the only one that uses pivotaltracker 🙂

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s