Agile Hive vs. Alfresco

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

Easy integration with the external APIs Workflows can be invoked via REST call Wonderful swagger documentation for process REST APIs REST, MULE, CAMEL, Google Drive, and Box features are available with Alfresco Process Services The micro-service version deployment should be well documented and needs improvement

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.

• Basic workflows are easy enough for casual users to set up and utilize.
• Cloud sync capability provides a great way to share documents with third parties and to use as a backup system for critical documents.
• Alfresco mobile app makes it easy for those on the road to access, approve and share documents.
• Folder rules are easy to set up and make assignment of metadata easier to automate.

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

• Alfresco Process Services and Alfresco Application Development Framework integration makes for best functionality/application of ECM.
• Use case alignment - Marketing content and documentation of specific business requirements and user stories being available as reference material/documentation.
• Integration with multiple silos for content.

Incentivized

As per the current market and the line of products that are available for content and document management system, Alfresco is a very good option compared to other systems in terms of features and cost. Plus the community support is great. Also since the product is open source, it can be extended or understood in a better way.

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

The UI is very intuitive, most of our users figure out how to use the platform by themselves, so there's not much training needed.

You can upload files by using the web drag and drop, WebDAV, FTP, and more.

Most of the platform already works as-is so you can just deploy it using Docker and it's mostly ready to go.

Incentivized

I am not big fan of Alfresco Content Services' support; it works on its own speed and sometimes it becomes challenging to achieve business needs. However, I appreciate regular delivery of security patches and updates

Incentivized

Process was relatively smooth and overall, downtime minimal. MSI was very responsive to our needs and made the transition easier than it otherwise might have been.

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

All software has some pros and some cons. Alfresco has some good pluses, and suits our environment very well. It fit perfectly in the place that we are working on. That is why we decided to go with this software. Overall, the kind of content management that needs to be done in an organization is what would determine which software to use.

Incentivized

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

• Instant document lookup - No paper files to mail which saves in all areas of postage, truck delivery, physical storage warehouse space, printing, etc
• No longer losing important documents - Previously with paper files things would go missing and those could be costly reports/assessments.
• Ability to secure documents and provide access to only those who should be allowed to see that content

Incentivized