We'll respond shortly.
On April 29, 2009 Pivotal Labs hosted the inaugural San Francisco Pivotal Tracker User’s Group. It was a great success! As an avid Pivotal Tracker user (and sometimes developer) for over 3 years I am very interested in making Tracker a better product and teaching others how to use Tracker to improve their organization.
Here are a few thoughts I took away from the meeting, and a few tips and tricks.
Once someone has created their first Project in Tracker, we don’t give you much guidance on what to do next. People need help getting past the “blank page problem:” faced with an empty project, it’s daunting to get started. Did you know you can create a demo project that’s filled with example Stories?
First, Login and click Create a Project
Next, click create a demo project
Check out the results!
What is the Difference between a Story, Bug, Chore, and Release? When should I use one versus the other? Good questions! To get started, check out the Stories section of the FAQ.
This is one of our top questions. The answer is this: Tracker doesn’t think you can get it done. Or, more specifically, history has shown that your team completes the number of points per iteration indicated by your Velocity. If history shows that you get 7 points done per iteration, Tracker will move the top 7 points worth of stories into the Current panel. Again, more details are available the Velocity and Iterations section of the FAQ.
This might help: to minimize this confusion, you can stack your Current panel on top of your Backlog (future) panel, giving you one big list. Choose View => Include Current in Backlog
At Pivotal, which is a large consulting practice first and a developer of Pivotal Tracker second, we have always refer to the tool as “Tracker.” But, at the user’s group we continually heard people refer to it as “Pivotal.” Interesting!
That’s it for now, but look for more Tracker (or Pivotal) tips and tricks in the future!