Bamboo vs. FinancialForce HCM (Discontinued)

If you value integration over cost, Bamboo is clearly the way to go. It offers tight integration to the rest of the Atlassian suite, and when you need traceability from issue to build, Atlassian is the right way to go. However, if you find yourself needing to save on costs, you may consider taking an approach of rolling your own build system with open source alternatives, such as Jenkins, if you don't [mind] putting in a little extra elbow grease.

Incentivized

FinancialForce HCM gives HR admins the full Hire to Retire experience while also meeting the needs of the worker/end user. Additionally, the application is well suited for talent management, shift scheduling, electronic benefits transmissions and connecting to payroll providers. Integration of HCM with other FinancialForce offerings, such as PSA and Accounting, completes the connection of front to back office.

Incentivized

• Levels of granularity. Organization has many projects that have many build plans that have many jobs that have many tasks, etc. And branch builds allow source control branches to be built separately.
• Versatility. I can use bamboo to manage my Java, node, or .NET build plans. I can use it to spin up Windows or Linux build agents, or install it on a Mac to build there as well.
• Bamboo integrates with other Atlassian products like Bitbucket, Stash, JIRA, etc. If a company commits to the entire Atlassian stack then work can be tracked through the whole development lifecycle which is really useful.

Incentivized

• It's customizable for every department.
• The "back-end" is easy to use. You do not always need to contact support to tweak items.
• Once a process flow is created, it is VERY user-friendly.
• We can integrate other platforms such as Formstack into FF.

Incentivized

• Extremely hard barrier to entry for non-backend developers
• Blackbox makes it hard to customize functionality
• The inability to add features without breaking core functionality
• No cloud solution
• Tasks cannot be put in if/else statements
• No clear right way to form build plans

Incentivized

• Dashboards need updating
• Difficult to customise reports
• Salesforce is not always as quick to respond with service issues as they could be

Incentivized

Bamboo was fairly easy to navigate but in the end it always felt as if it was developed as a bolt-on and not a true group up user interface. There were multiple ways to get to everything and the path was never the same. So it was difficult for users to really get a feel of how to use the application.

Support for Bamboo has started lack a little over the years. Atlassian has been moving more towards Bitbucket Pipelines and away from the on-premise install of Bamboo. While the tool is still great, it may take a little bit of time to get a question answered by official support.

We selected Bamboo because its capabilities to integrate with other Atlassian products specially Jira Software, Bitbucket and in some useful scenarios with Confluence. Also, we found these pros important for us: great user interface, easily agent deployment, Docker compability, simply to maintain / manage, and straightforwardly integration with different notification platforms

Incentivized

From a pricing perspective, FinancialForce HCM is very competitive in both licensing and implementation costs. Ultimately having an application that was native to Salesforce drove our final decision. While we were hoping to find an application that included the ability to process payroll internally we settled on the process of linking to a 3rd party vendor. The other options were either too pricey or lacked some of the key functionality we required.

Incentivized

• It helped us achieve the Continuous Deployment and Continuous Integration goals for our applications, a huge milestone that saved a lot of time for developers in making the builds and deployments and saved time for QA in running the automated tests.
• Helped with DevOps: we moved the formal approval from the email to the system and allowed the approver to actually push the button for the production deployments.
• Biggest positive impact of using Bamboo is that it improved our response time to customers and increased the frequency of our deliveries to them.

Incentivized

• It improved self service capabilities - saving significant HR time.

Incentivized