Dan PodsedlyDan Podsedly
Mar. 30 Tracker Outage
edit Posted by Dan Podsedly on Tuesday March 31, 2009 at 10:23PM

Here's some information from Engine Yard (our hosting service provider) about yesterday afternoon's data center outage, which affected a number of applications including Pivotal Tracker:

http://blog.engineyard.com/2009/03/31/march-30th-outage

We apologize for the inconvenience this outage caused, and appreciate everyone's patience. As detailed in Engine Yard's post, steps are being taken to ensure that this does not happen again.

Ian McFarlandIan McFarland
Pivotal Tracker wins the Jolt Award
edit Posted by Ian McFarland on Thursday March 12, 2009 at 03:38AM

I'm very pleased to announce that Pivotal Tracker has won the coveted Jolt Award, in the Project Management category.

I want to thank the judges for selecting Pivotal Tracker above a category dominated by Agile project management tools, and for rewarding Tracker for innovation.

I want to thank the community who have used, evangelized, and supported Tracker, and in particular Obie Fernandez, Ward Cunningham, and Nivi; plus everyone over at Engine Yard for hosting the app.

And of course I want to thank and congratulate the development team and visionaries, particularly Dan Podsedly, Alex Chaffee, Rob Mee, Mark Michael, and Edward Hieatt for envisioning and then building the tool that we've come to depend on.

Ben WoosleyBen Woosley
Pivotal Tracker and the Planning Fallacy
edit Posted by Ben Woosley on Wednesday March 11, 2009 at 04:32PM

I came across an interesting post on Overcoming Bias today about the Planning Fallacy. In short, the evidence shows that individual predictions generally occur in a rosy inaccurate world where everything goes according to plan, even when interruptions and setbacks are inevitable:

Buehler et. al. (1995) asked their students for estimates of when they (the students) thought they would complete their personal academic projects. Specifically, the researchers asked for estimated times by which the students thought it was 50%, 75%, and 99% probable their personal projects would be done. Would you care to guess how many students finished on or before their estimated 50%, 75%, and 99% probability levels?

  • 13% of subjects finished their project by the time they had assigned a 50% probability level;
  • 19% finished by the time assigned a 75% probability level;
  • and only 45% (less than half!) finished by the time of their 99% probability level.

As Buehler et. al. (2002) wrote, "The results for the 99% probability level are especially striking: Even when asked to make a highly conservative forecast, a prediction that they felt virtually certain that they would fulfill, students' confidence in their time estimates far exceeded their accomplishments."

But it seems one can overcome this bias towards optimism by getting an "outside view" on the problem as it relates to the timelines on previous similar projects:

Buehler et. al. (2002), found that Japanese students expected to finish their essays 10 days before deadline. They actually finished 1 day before deadline. Asked when they had previously completed similar tasks, they responded, "1 day before deadline." This is the power of the outside view over the inside view.

So there is a fairly reliable way to fix the planning fallacy, if you're doing something broadly similar to a reference class of previous projects. Just ask how long similar projects have taken in the past, without considering any of the special properties of this project. Better yet, ask an experienced outsider how long similar projects have taken.

Pivotal Tracker, unlike other project management software, is built on exactly this idea of the outside view, via points and emergent iterations:

Tracker calculates future iterations based on historical performance. Focus on prioritizing and completing your stories; let Tracker take care of planning future iterations, based on actual progress.

It's gratifying to see that the emergent iterations are not just easier for the user, as there's no need to manually specify them - they're also more likely to be accurate, as they're based on an external view of your own progress. Yet another reason to look to Tracker for your project management needs.

Dan PodsedlyDan Podsedly
Public projects in Pivotal Tracker
edit Posted by Dan Podsedly on Saturday March 07, 2009 at 12:44AM

If you use Pivotal Tracker for open source projects, and would like to increase visibility into what your team is working on, you can now do so by making your Tracker project public.

As a project owner, you can enable public access for your project on the Project Settings page, by selecting the Public Access checkbox. The public URL to the project is to the right of the checkbox, in the format http://www.pivotaltracker.com/projects/xxx, where xxx is the id of the project. You can also append a dash to that URL, with a more descriptive name of your project, for example http://www.pivotaltracker.com/projects/xxx-My-Cool-Project.

Anyone you give the project URL to will be able view stories in your project, without having to sign in to Tracker. They'll also be able request project membership by clicking the "Join This Project" button.