danp's dashboard

danp replied on November 20, 2009 20:12 to the problem "Auto leveling is turned off, but Tracker is still auto-leveling." in Pivotal Labs:

HI Devin, could you clarify what you mean by auto-leveling? Are you referring to commit mode, perhaps?

thanks
dan

danp replied on November 20, 2009 19:40 to the question "Override velocity after restarting stalled project" in Pivotal Labs:

Unfortunately it's not possible to override velocity for others, but you can use a combination of iteration length override and team strength. Take the iteration where that "stall" began, change it's length to however many weeks to stall continued for, and them change the team strength for that iteration to something that reflects the relative amount of energy that was being devoted to the project. You can make it 0, if no work went on at all.

This should align Tracker's view of the project with reality.

danp replied on November 19, 2009 22:56 to the problem "pivotal shows different velocities for teams in different timezones" in Pivotal Labs:

Hi, thanks for letting us know. This is a known issue, related to time zones and iteration boundaries, introduced in a recent release. We have it fixed, and will be deploying the fix over the weekend. Sorry for the confusion, hopefully you'll be able to live with it for another day? In the meantime, you can set your time zone (in My Profile) to that of the project, and you should see the same iterations.

danp replied on November 19, 2009 18:00 to the question "how to notify more people about story changes?" in Pivotal Labs:

danlevine - one thing you could do is change that alias user's notification preferences to receive all comment notifications (on the profile page). this way, everyone will get all of the comment emails, without having to make this user an owner of every story.

danp replied on November 19, 2009 17:55 to the praise "You folks are my new role models" in Pivotal Labs:

Dan, thanks, we love feedback like this.

Let us know know if there's anything we can help with, or questions we can answer.

dan

danp replied on November 19, 2009 17:39 to the idea "Option to skip weekends" in Pivotal Labs:

Hi, unfortunately we've been swamped with features requests, etc, and this has slipped. We'll do our best to get it in this year. It's probably a simple change, but may get a bit complicated due to time zones.

danp replied on November 17, 2009 13:35 to the question "still waiting for catch-up script to run, after 3 days" in SocialToo:

Gave up waiting, still no response. Deleted my account, lost $5.

danp replied on November 16, 2009 15:50 to the problem "Iterations still start on Sunday despite of setting that it should start on Monday" in Pivotal Labs:

Hi Rytis...we're looking into whether we introduced an iteration boundary bug in yesterdays release. Thanks for letting us know, we'll keep you posted.

danp replied on November 16, 2009 15:45 to the problem "Iteration boundaries may not be respecting project time zones" in Pivotal Labs:

Hi Donald, there were some bug fixes rolled out last yesterday, related to iteration boundaries and time zones. It's possible we introduced a problem. We're looking into it, in the meantime could you lets us know which project this is in, either here or by email (tracker at pivotallabs dot com)?

danp asked a question in SocialToo on November 13, 2009 23:59:

still waiting for catch-up script to run, after 3 days

Paid for the auto-follow catchup feature, it's the 3rd day and I still see the "waiting for script" to run message. No response from 2 emails to contact, either. Anyone there?

danp replied on November 12, 2009 16:01 to the idea "Two way integration with Zendesk" in Pivotal Labs:

Hi Linus....we're actually just about to being work on expanding the Tracker API to support for 2 way integrations. You'll be able to keep Tracker stories in sync with any external tool that has an API, including Zendesk.

danp replied on November 11, 2009 21:37 to the problem "API fails updating stories that have a deadline." in Pivotal Labs:

Hi, we actually just finished a fix for this, it will be deployed sometime later this week. Sorry, and thanks for letting us know.

danp replied on November 11, 2009 16:18 to the idea "Auto/manual move Done stories out of Current" in Pivotal Labs:

Hi Scott...stories don't move to Done, the entire iteration does, with accepted stories, at the end of the week. Would it help to have an option to hide accepted stories in current, though, for situations where there are a large number of them?

danp replied on November 10, 2009 15:22 to the problem "Owner/Requester role assurance" in Pivotal Labs:

Hi...anyone who is a member of a project can accept stories, or make other changes. We made it this way in order to encourage collective (team) ownership, and to make Tracker as easy to use as a shared whiteboard of story index cards. You can use project history, though, to see who accepted a given story.

danp replied on November 09, 2009 19:01 to the question "Integration with GetSatisfaction.com" in Pivotal Labs:

Hi, thanks!

We're actually about to start work on an integration framework (using the API) that will make integrating Tracker with various bug/issue management tools and community support forums easier, both for developers and end users. Satisfaction makes a lot of sense to integrate with, so watch for progress on this.

In the meantime, you could actually write an app that that used the existing Satisfaction and Tracker's APIs to automatically "push" new problem reports in to Tracker. There are some examples here:

http://www.pivotaltracker.com/help/th...

danp replied on November 09, 2009 17:26 to the question "How big should a project's scope be?" in Pivotal Labs:

Hi...generally, we try to align "projects" with stable teams, in order to have predictable velocity. Flip is the potential for projects to get very large, and hard to manage. One approach is to maintain a Tracker backlog for a few months out only (or the next couple of releases), and keep longer-range plans outside, for example in a shared spreadsheet, which allows you to react more easily as business priorities change. Also, labels can be very helpful to keep track of related stories - we use them quite extensively.

danp replied on November 09, 2009 15:47 to the question "languages" in Pivotal Labs:

hi, you can use UTF8 characters, but Tracker doesn't support other languages, yet. we're really hoping to tackle that at some point in the next year.

danp replied on November 08, 2009 23:03 to the problem "Attempting to save an 'accepted' story using the API causes server side error" in Pivotal Labs:

hi...this will be fixed in the next release, which will most likely be sometime this week.

danp replied on October 30, 2009 19:17 to the question "Current tab's points 3x higher than they should be" in Pivotal Labs:

hey Chris...in case you don't see the Twitter reply, your current iteration is set to be 3 week long (that's why the date range label is yellow). click on it to change (or revert) the 3 week override.

capacity calculation takes iteration length into consideration.

danp replied on October 30, 2009 13:36 to the question "Report for Points by Member" in Pivotal Labs:

The search results panel shows a point total at the top, as well as the # that have been completed.

Every project is different, but we've found that project planning at the team level is more effective than managing/allocating individuals on the team. Stable teams tend to have fairly predictable velocity, and with a prioritized backlog of estimated stories, work allocation happens without any overhead (people grab stories as they free up).