Agile Hive vs. Pivotal Tracker

Agile Hive is used for our value train
within a SAFe setup. Every quarter we organize a so-called Product Increment
(PI) Planning, where we plan all Features and Enablers in Agile Hive.
Based on the priority of the Product Manager all teams plan their Features and
Enablers accordingly to the sprints that are determined by the Release Train
Engineer and set up in Agile Hive. The teams then create User Stories and
estimate them and based on their sprint velocity (defined in Agile Hive)
Product Owners can see how many Features and Enablers are realistic in one
quarter (Product Increment). Further, dependencies across teams can be defined
and made visible in Agile Hive, so that the plan is feasible. Without Agile
Hive it would be hard or impossible to plan across several teams within a value
train and to manage all dependencies. Additionally, with Agile Hive the plan is
more realistic, so what can be achieved within one quarter in product
development.

Incentivized

The UI of the Pivotal tracker is really beautiful and amazing, which looks trivial, but we have it open all the time, so it's nice for us. In Pivotal tracker for me its very Easy to create tasks or stories anytime without facing any problems. Pivotal tracker provides us a ton of features to track the tasks and manage a team and the projects. Pivotal tracker allows for a entire team to be on the same page of the tool in regards to where is the project right now, right status of every task, what is being worked on and by whom.

Incentivized

• Roadmapping in terms of defining epics and planning them across a timeline and across teams.
• Showing dependencies within teams and across teams and over time horizon.
• Create transparency throughout the product organization and teams about what is planned.

• It's great for tracking milestones and reporting team velocity per sprint.
• Maintaining a prioritized backlog that is sharable with different members of your team is relatively simple.
• There's a free version of the product for up to 3 collaborators working on 2 projects and the starting price for larger packages is relatively low.

Incentivized

• I believe the training and support could be more hands on and easier.
• The Agile Hive - SAFe in Jira product can be a bit robust to understand.
• Having Knowledge transfer videos can help more than documentations.

Incentivized

• In-story task management is still a weak point. The ability to @mention users in tasks and mark tasks as 'in-progress' would go a long way.
• Epics do not span projects. This becomes troublesome when scaling Pivotal Tracker's agile methodology to multiple teams.
• Splitting stories is often confusing for team members as there is no concept of a 'parent' story with child stories that have split off of it. There are only two levels: Epic & Story.

Incentivized

I love the simplicity, non-configurability, and price/performance of this tool. Hands down my favorite project management tool for agile.

Incentivized

It has in general a good usability, but there are some downsides, the big picture view of the entire product increment is too static, so there is no zoom in or zoom out. Mostly throughout planning it is necessary to zoom in to a sprint level and manage the user stories there. Also, the pig picture view has some limitations, because you cannot read the entire user story name (boxes are too small).

Incentivized

It works good enough. I didn't have many problems with that. The user interface is a bit confusing though. The team took some time to understand where some configurations were.

Incentivized

We've never had to request support in the 5 years I have been using it. A solid solution! Everything I have had questions about is on the website. New features are in their newsletter with more details on their website. Often I am using the new features within a few minutes of reading the article.

Incentivized

With Jira Software alone it is also possible to plan a SAFe product increment planning, but it would be nearly impossible to see the overall big picture of all product teams involved in a release train. So, the planning on sprint level for one team would be more efficient, but the planning for a whole quarter with all dependencies across teams would be not feasible to present. Therefore, Agile SAFe enables value trains an efficient way to plan a product increment.

Incentivized

We have had employees in the past look at Drupal, and other open source project management tools to assist in our needs. Unfortunately each solution took too much time to implement, design and configure that we could not stop the work we were doing for clients to complete a full set up of a project tracker. Thankfully Pivotal is a predefined solution with no configuration needed. Simply input your projects, design your Stories with Tasks and begin your tracking.

Incentivized

• More transparency.
• Better product decisions.
• Saving time and resources.
• Less critical dependencies.

• Time is money with development and a lot of things can fall through the cracks. Having a good system for making sure you're building the most relevant product for customers is really important so it was well worth it for us.
• The process we used worked for us and it helped us streamline our development which reduced a lot of things falling through the cracks and headaches. I'm sure there are other products that can do the same job just as effectively but Pivotal Tracker worked well for us.

Incentivized