Agile Hive vs. Planview AgilePlace

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

This tool enables the visual management needed in many offshore teams to easily and quickly see the pending work, work in progress and completed work.For teams that work with a waterfall methodology and do not have AGILE internalized, I believe there are other solutions from Planview or other providers.

• 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.

• Visual kanban board that is easy to customize as the team's needs change
• Real time collaboration allowing teams working remotely to stay up to date on current status
• Allows versatility for how a team needs to capture details on the work at hand by utilizing card icons, card types and custom data points
• Card scoring is easy to setup and provides the team the ability to set values to better prioritize their backlog
• Ability to add card automation to take out some of the repetitive manual actions

• 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

• Ability to add more than 1 visual cue to the card. We use custom icons and sometimes more than 1 is appropriate but you have to choose which is most important since only 1 can be applied.
• Better visibility to board access from the user administration screens. Currently have to run 1-2 reports to see this information. Would like to be able to click on a user within Configure Users and see what boards they have access to quickly.

we are happy with the tool and the service and continuos improvement of the tool so there is no need yet to change to another one.

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

LeanKit isn't the best designed Kanban system I've seen, but overall it's pretty usable. The boards I've used are pretty complex, so it can be difficult to find things. I found that searching and filtering for specific cards was somewhat of a challenge. Dragging a card from one lane to another is kind of a fun way to get things done though.

Incentivized

Not experienced any outage

Incentivized

Larger boards take longer to load

Incentivized

Every time I have reached out to the AgilePlace support team I have received a timely response in addition to professional & personal feedback. Their consultants are knowledgeable and the management team is happy to jump in and help when needed.

Very easy.

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

Originally, we had evaluated two other tools next to Planview LeanKit: Kanbantool and Kanbanflow. The latter was a close contestant for productive use, as it was also very customizable and a joy to work with and look at. It also had lower user fees and a mobile integration. In the end, we picked Planview LeanKit because of several reasons: Aesthetics: The look was much more clean and professional. Reporting: It was obvious from the start that we could use Planview LeanKit as a tool for improvement. API: We needed to integrate the Kanban into our central systems and Planview LeanKit API was (and still is) a way to do it. Card Headers: This sounds like a simple thing, but the headers above the titles fit our work perfectly and looked perfect, which helped the decision.

Incentivized

Good use cases for small/large teams

Incentivized

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

• LeanKit has made it easier for new employees to understand other employees' roles in the company by seeing their workload.
• It makes it clear who is responsible for what project so that there is more accountability at our company.
• It helps our project manager schedule new projects in a way that we all can see.

Incentivized