3 ms·

Pivotal: Horrible, abysmal tool. Hate it with a passion. No clear overview at all, UI is full of shiny colors but is messy as hell. I'm really glad we've switch

by st0p 14y ago

Pivotal: Horrible, abysmal tool. Hate it with a passion. No clear overview at all, UI is full of shiny colors but is messy as hell. I'm really glad we've switched to Jira[1] after fighting with pivotal for a couple of months. YMMV ofcourse :) [1] http://www.atlassian.com/software/jira/overview http://www.atlassian.com/software/jira/overview

netshade 14y ago
I definitely agree with the YMMV bit; I have found this category of tools to be incredibly divisive. I know a lot of folks who thought that going in the opposite direction of yours, Jira to Pivotal, was one of the best decisions they've made for a project. I've only ever casually used Jira, however, so am ill qualified to speak to its strengths.
- ziel 14y ago
  I'm in the category you're describing. (Switched from Jira/Greenhopper to Pivotal and happy about it). I think the divisive bit may, in part, be that Pivotal is a strongly opinionated tool while Jira is a fairly customizable and open ended tool. For projects & teams committed to the process Pivotal champions, it's highly optimized. For teams using a different process, or who need to customize views for different people etc, Jira can provide more options, and be a better fit. For me personally... at the moment, I really appreciate Pivotal's relative simplicity and the way it encourages folks to focus on the somewhat nearer term.
bzalasky 14y ago
I love Pivotal. While I haven't used Jira, I've gotten the feeling that other members of my team have used it in the past, and don't like it at all. On another note, Siebel time tracking is a pit of hell.
jerryr 14y ago
Pivotal is an agile planning tool; JIRA is an issue tracking and classical project management tool. While each can be coerced to the other's function, it's really comparing apples and oranges. I'll admit that JIRA and Pivotal continue to muddy the differentiation with afterthought additions like JIRA's Greenhopper and Pivotal's time tracking. But JIRA is a good tool for issue tracking and Pivotal is a good tool for agile planning. If you're trying to use either tool for the other's purpose, you'll hate it.
- ajross 14y ago
  I still can't read "tool for agile planning" without crying inside my head. We really need "tools" to "implement" "processes" in the spirit of a 6-line manifesto, do we? Sigh.
  - jerryr 14y ago
    Aww. Don't cry. It's not a process tool. It's a prioritized to-do list that can track your velocity. Despite being opinionated, it doesn't enforce a process. Though you'll find that if you don't embrace those 6 lines, you'll quickly make a mess inside Pivotal and it will happily let you do so.

by st0p 14y ago

netshade 14y ago

I definitely agree with the YMMV bit; I have found this category of tools to be incredibly divisive. I know a lot of folks who thought that going in the opposite direction of yours, Jira to Pivotal, was one of the best decisions they've made for a project. I've only ever casually used Jira, however, so am ill qualified to speak to its strengths.

ziel 14y ago
I'm in the category you're describing. (Switched from Jira/Greenhopper to Pivotal and happy about it). I think the divisive bit may, in part, be that Pivotal is a strongly opinionated tool while Jira is a fairly customizable and open ended tool. For projects & teams committed to the process Pivotal champions, it's highly optimized. For teams using a different process, or who need to customize views for different people etc, Jira can provide more options, and be a better fit. For me personally... at the moment, I really appreciate Pivotal's relative simplicity and the way it encourages folks to focus on the somewhat nearer term.

bzalasky 14y ago

I love Pivotal. While I haven't used Jira, I've gotten the feeling that other members of my team have used it in the past, and don't like it at all. On another note, Siebel time tracking is a pit of hell.

jerryr 14y ago

Pivotal is an agile planning tool; JIRA is an issue tracking and classical project management tool. While each can be coerced to the other's function, it's really comparing apples and oranges. I'll admit that JIRA and Pivotal continue to muddy the differentiation with afterthought additions like JIRA's Greenhopper and Pivotal's time tracking. But JIRA is a good tool for issue tracking and Pivotal is a good tool for agile planning. If you're trying to use either tool for the other's purpose, you'll hate it.

ajross 14y ago
I still can't read "tool for agile planning" without crying inside my head. We really need "tools" to "implement" "processes" in the spirit of a 6-line manifesto, do we? Sigh.
- jerryr 14y ago
  Aww. Don't cry. It's not a process tool. It's a prioritized to-do list that can track your velocity. Despite being opinionated, it doesn't enforce a process. Though you'll find that if you don't embrace those 6 lines, you'll quickly make a mess inside Pivotal and it will happily let you do so.