Comments on: Trying Pivotal Tracker

By: Finn

Finn — Thu, 04 Nov 2010 19:35:00 +0000

Check also smartQ (http://www.getsmartQ.com) – same concept, just with more universal approach.

By: Jake

Jake — Tue, 17 Mar 2009 10:11:13 +0000

Thanks for the tip. So far, we're happy with it, but this is a small team (2 devs, 1 PM). If we get into a disorganized mess, we'll check out Intervals.

By: John

John — Tue, 17 Mar 2009 03:38:35 +0000

Pivotal tracker is great. but it can quickly become disorganized once you've added too many stories. I would suggest also trying out Intervals, which organizes stories into tasks in a more traditional bug/issue tracking environment.

By: manalang

manalang — Sun, 15 Mar 2009 05:55:49 +0000

@raimonds, @jake we do use New Relic RPM. I love it.

By: Jake

Jake — Sat, 14 Mar 2009 04:17:06 +0000

Fast is definitely the key for stories, and I like what Tracker has done to address that. Paul may even start using it

Thanks for the tip on New Relic. Remember, Connect is a JRuby app, which may cause problems. I'm Rich knows for sure.

By: Raimonds

Raimonds — Sat, 14 Mar 2009 03:37:36 +0000

Two weeks ago I also moved my current company in-house projects to PivotalTracker and I am happy so far with it.

This is the first Agile planning tool that I really like as all the other tools were introducing too much complexity to the process. Therefore I tried to stick to user story index cards or used Excel sheets if all team was not co-located. But now finally with PivotalTracker it is much easier to work with remote team members – now it is very easy and fast to create user stories / bugs / other tasks during online meetings or during my e-mail processing.

BTW if you still do not use I also recommend New Relic RPM service for Rails production application monitoring. This was similar experience – I just installed it and instantly got very usable reports about how my application is performing and what are the usage statistics.