The Kanban view

The Pivotal Tracker view is a great tool for managing projects, especially the new version that was just released. It gives you a clear overview of what's being worked on and how much work there is left to do on a given iteration. We've decided to take it one step Read More

2 reasons why estimating isn’t actually about estimating

It's often said that estimates for software development are inaccurate and time-consuming. There's even a #NoEstimates movement that preaches that we stop sizing stories all together and "just start developing" instead. Although I agree that estimates are time-consuming to make and rarely reflect reality, I don't agree that they're a Read More

When you should change the done state from accepted to something else

The states in Pivotal Tracker can mean different things to different teams. Typically, the finished state means developers have finished coding a story and have run their standard tests. The story is then delivered when it's ready for acceptance testing (deployed to a staging environment perhaps). If the acceptance test Read More

2 metrics most velocity charts are missing

Velocity is how much work a team can handle in an iteration. It's largely estimated by looking at previous iterations, and it's important because it gives you an idea of how much work a team should be able to take on in future iterations. Almost every Scrum team tracks velocity, Read More