cmurph's dashboard

cmurph started following the idea "JIRA plugin for Tracker using the tracker API" in Pivotal Labs.

cmurph started following the idea "Delete/Edit Comments" in Pivotal Labs.

cmurph replied on November 12, 2009 00:42 to the idea "Edit comments on stories" in Pivotal Labs:

comments should be edit-able and delete-able.

cmurph replied on November 11, 2009 18:35 to the question "Does tracker supports boolean searching?" in Pivotal Labs:

this would be very valuable for us

cmurph started following the question "Does tracker supports boolean searching?" in Pivotal Labs.

cmurph replied on November 10, 2009 19:11 to the idea "Bugs and Chores should be estimable, without counting toward velocity." in Pivotal Labs:

I've read all the back and forth debate about estimating bugs/chores, I'm familiar with Pivotal's stance, etc... but I just can't wrap my head around this:

If (1) Tracker automatically moves bugs & chores from the backlog to the current iteration and (2) Tracker doesn't allow point values to be assigned to bugs and chores then (3) Tracker has the potential to add an infinite number of bugs and chores to the current iteration.

In other words, if my current iteration is filled to 14 out of 15 points, and I have 367 bugs and chores at the top of my backlog, they will ALL be moved into the current iteration. This just doesn't compute.

The workaround seems to be manually intervening in order to move stories around (and potentially artificially "block" them from getting added to the current iteration)... but Tracker supposedly promotes an automatic, hands-off assignment of stories. What gives?

cmurph started following the idea "Bugs and Chores should be estimable, without counting toward velocity." in Pivotal Labs.

cmurph started following the question "Placement of release bar." in Pivotal Labs.

A comment on the idea "Would love to have different velocity per team member" in Pivotal Labs:

we have this same "dilemma"... two developers, both with different skillsets and rarely on the same project. For now, we are doing what you suggested and manually ensure that each iteration has enough work for bob and enough work for bill... we are just starting out and so i unfortunately can't tell you the effectiveness of this method yet! – cmurph, on November 07, 2009 07:50

cmurph marked one of Peter Lübeck's replies in Pivotal Labs as useful. Peter Lübeck replied to the idea "Would love to have different velocity per team member".

cmurph replied on November 07, 2009 04:19 to the question "Moving a story from a project to the other" in Pivotal Labs:

I've successfully selected a number of stories and then used the "export selected as csv" function in the actions menu to export them and then import that same file into another project... maintaining the estimation, owner, requester, and all other story info....

cmurph started following the question "Is PivotalTracker suitable as a bug tracker?" in Pivotal Labs.

cmurph started following the question "Is it possible to fomally tie bugs or chores to specific user stories?" in Pivotal Labs.

cmurph asked a question in Pivotal Labs on November 06, 2009 16:19:

How big should a project's scope be?

My first inclination was to break out projects according to the areas of our web app: reporting, import widget, profile page, support ticket system, signup process.... however, some have suggested that we should instead have one project for, basically, everything.

cmurph started following the question "Should I have one Project per application, or one per project?" in Pivotal Labs.