Backlog Aggregator: Roadmap preview (part one)

A Roadmap is a concept a little bit harder than a backlog to be managed using external tools. Pivotaltracker or software like that are very handy to manage a lot of things, but sometimes a roadmap’s content doesn’t fit perfectly with the approach that other software impose to you.

So while my teammates were thinking of how to aggregate the data and where to save them, I made the frontend as a Single Page Application using AngularJs and Jasmine and using Chutzpah as test runner.

One of the things I most appreciate using angular are the Directives.

The goal was to have a preview of a roadmap to use it in a dashboard able to summarize all the projects and their statuses.
What I wanted was to create a roadmap easily, something like

<roadmap-preview roadmap="roadmapContract"></roadmap-preview>

and I expected to have a result like
Continue reading


Backlog Aggregator: Pivotaltracker Plugin (part one)

There we are.
The goal with this plugin was to give an easy way to get from a project the stories of the current iteration.
I usually prefer to work time boxed when I play on an exploration task, so I decided to give five hours to this task and then evaluate the results and possible efforts/costs to obtain an usable version of the plugin.

My team uses Pivotatracker so I already had  the credentials to use the API, but before to write any code, I started reading a few of documentation and making some test using my REST Client.
After one hour I was sure to have enough information to start.

Continue reading

Backlog Aggregator: how

Well, the idea was to have a website where to show, for every project, backlog and other informations more related at the Company and its workflow.

We decided to split the work, so I was in charge to develop the website and to give a help to develop the plugins able to get stories from pivotaltracker and easybacklog and able to map them in a common DTO.

The others two team members started to analize a repository and a backoffice to put other relevant information apart the backlogs.

Continue reading

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.

Continue reading