Why should I be using Lighthouse with Pivotal Tracker [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered 开发者_运维知识库with facts and citations by editing this post.

Closed 5 years ago.

Improve this question

I've started using Pivotal Tracker and really enjoy it. I've also started looking at Lighthouse. Is there any value in using both systems with Tracker's Lighthouse integration? Should I sync everything from Lighthouse to Pivotal or keep bugs separate in Lighthouse?

---

Lighthouse is a vanilla issue tracking system, along the same lines as Trac, Bugzilla, Github Issues et al, and is fine if all you want to do is maintain a list of bugs and features.

Pivotal Tracker is sold as an 'agile project management tool', and is geared towards teams who are specifically running an agile development process where development is done in sprints. Tracker allows your team to estimate your stories in points and, over time, it calculates your team's development velocity which, in theory, allows you to accurately predict when features will be delivered. This doesn't mean you can't use Tracker in the same way as Lighthouse (i.e. without worrying about points) - it will still work well for you like that.

Given this, I'd definitely use one system rather than a combination of both. Having had experience of both I'd recommend Tracker, but this is of course personal preference and YMMV.