Agile Hive - SAFe in Jira vs. Pipefy

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

Pipefy is very well suited if you have a team doing any sort of process... for real! It simplified everything from our sales and marketing objectives/processes, to our onboarding and accounting side of things. Since you can share different pipes with others, it's easy to see where others are at in the process and move the card along while keeping others informed. It makes sure you don't miss any information or steps along the way, which is great if your process is detail-oriented. It is a little less appropriate for marketing efforts, but we still try to use it to keep track of things in a central space. Definitely best suited for sales, technical things, and accounting.

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.

• Flexibility on process management.
• Internal automations and connections to different data bases and boards.
• Easily connection with external programs through API's.

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

• I would like to be able to add a due date without a time attached.
• I would like to see completed tasks be deleted after a set amount of time.

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

Pipefy support is pretty good. There were a few instances where the agent didn't really understand what I was trying to get help with, but that was only once. Every other time it has been pretty fast and efficient. They are also very kind and understanding. I don't think they need much help in that dept

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 started using software we already had (such as Slack and Sheets) but this software is not actually ideal to manage processes, which led to errors, miscommunication, and execution problems. Trello is good for managing demand but offers no process customization or approval and Jira is too focused on development for our needs, and also hard to customize.

Incentivized

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

• Our processes are more organized and we are not missing any steps.
• We are able to touch base with customers easier since we have all potential/missed clients in one pipe, with automated alerts (i.e. it has been 60 days since contact with this customer).
• We are able to keep track of customer billing changes easier.

Incentivized