We are using Pivotal Tracker in our current project and I have to say it’s a pretty well done product. It gives us the ability to manage and track our development process.
You can:
create Features Stories, Chore Stories, Bug Stories and Release Stories.
estimate those stories.
keep track of the state of the stories (started, finished, delivered, accepted).
maintain a backlog.
set releases.
I highly recommend you give it a go, also because it’s completely free
But ok, back to the subject of this page: Pivotal Tracker Story Board extension.
I ended up creating this extension only because I wanted to have a clear and simple view of the current iteration in Pivotal Tracker. If you look at Pivotal Tracker you’ll see that it already gives you a view of the current iteration, but it’s just a list of stories, with pre-set states (start, finish, deliver, accept/reject) and it won’t hide the stories that are completed.
What I wanted was a column based view where I could specify each story state as I wanted. This to simplify readability for Customers/Product Owners.
Another reason is that we use those story states to specify different stages in our development process like:
When we finish a story the developer will click on the finish button which indicates that the story has been developed reviewed and committed.
Now the story can be picked up by the Test team which will run the different acceptance tests against it.
After that if the tests are passed the Test Team will click on the deliver button which will set the story to the “Accept / Reject” state.
Now the Product Owner will try out the story and if satisfied accept it.
In our everyday lingo we use the following terminology for each state:
not started => not started
started => in development
finished => ready to test
delivered => ready for acceptance
I know it is a small difference but I think it makes it easier for people outside the team to understand the process better.
And this is how Pivotal Tracker Story Board helps us achieving that:
You can change the title of each column in the Options page of the extension accessible from the Extension page in Chrome:
The Options page is also the place where you need to input your API Token and also set the frequency by which Pivotal Tracker Story Board will updated itself.
That’s it.
N.B.
To make Pivotal Tracker Story Board being able to access your project data, you need to tick the Allow API Access check box in the Settings page of your project. (for each project if you have more than one!)
another thing to remember is that the API token is relative to the User, so if, for example, you have two accounts in Pivotal Tracker , Pivotal Tracker Story Board will work for just one of them, as it can store only one API token at any time.
Pivotal Tracker Story Board
We are using Pivotal Tracker in our current project and I have to say it’s a pretty well done product. It gives us the ability to manage and track our development process.
You can:
I highly recommend you give it a go, also because it’s completely free
But ok, back to the subject of this page: Pivotal Tracker Story Board extension.
I ended up creating this extension only because I wanted to have a clear and simple view of the current iteration in Pivotal Tracker. If you look at Pivotal Tracker you’ll see that it already gives you a view of the current iteration, but it’s just a list of stories, with pre-set states (start, finish, deliver, accept/reject) and it won’t hide the stories that are completed.
What I wanted was a column based view where I could specify each story state as I wanted. This to simplify readability for Customers/Product Owners.
Another reason is that we use those story states to specify different stages in our development process like:
In our everyday lingo we use the following terminology for each state:
I know it is a small difference but I think it makes it easier for people outside the team to understand the process better.
And this is how Pivotal Tracker Story Board helps us achieving that:
You can change the title of each column in the Options page of the extension accessible from the Extension page in Chrome:
The Options page is also the place where you need to input your API Token and also set the frequency by which Pivotal Tracker Story Board will updated itself.
That’s it.
N.B.
To make Pivotal Tracker Story Board being able to access your project data, you need to tick the Allow API Access check box in the Settings page of your project. (for each project if you have more than one!)
another thing to remember is that the API token is relative to the User, so if, for example, you have two accounts in Pivotal Tracker , Pivotal Tracker Story Board will work for just one of them, as it can store only one API token at any time.
Vizio