Overall Satisfaction with Bitbucket
Bitbucket is perfect for all sized companies - it works even if you are using the free version and it works even better with the paid versions. Initially, we started out using bitbucket as simply a code repository so we could quickly set up projects - as we expanded and started using Atlassian's project management tools then it became important for us to integrate the development teams with the PM teams. The integrations gave Project Management teams insights into the technical issues without necessarily being burdened by the details. I especially like the ability to have control over changes being deployed directly into production - running continuous integrations to ensure the code quality is maintained!
- Positive ROI especially with increased communications between PM and Developers
- Positive ROI - don't need a release engineer
When GitHub was acquired by Microsoft my previous organization had concerns about paywalls and additional restrictions that might be placed on the projects. We had made a move to Bitbucket as a result. The acquisition didn't seem to have any implications on the overall company and it might not have been worth the switch, but there was very little difference. Bitbucket obviously had better integrations with Atlassian JIRA and therefore worked better.
Do you think Bitbucket delivers good value for the price?
Are you happy with Bitbucket's feature set?
Did Bitbucket live up to sales and marketing promises?
Did implementation of Bitbucket go as expected?
Would you buy Bitbucket again?
In the Caribbean - with limited resources, it is nice to know a company will be there in assisting you to grow. They will start you off with a very good free tier and you can scale easier on a predictable budget. Bitbucket works especially when you are using Atlassian's toolset. If you aren't married to the company - then you can explore others like GitHub which offers comparable features without much compromise.
6 - The 5 developers are the primary users, using it to tackle code sprints and code reviews. The final person is an infrastructure guy with some background in doing automated deployments. His only integration is usually to set up deployments or make minor adjustments. The developers also participate in the development of items in the product backlog - outside of code sprints.
1 - Honestly - there is no real need to support Bitbucket. Once someone is there to manage the creation of the project the rest is a cakewalk. Developers are all aware of how to use platforms like bitbucket and GitHub, so support is becoming less and less of a need. The majority of users require 1-day training on the appropriate use of the tool and then after that, it just works.
- Continuous Deployments/Integration
- Code Reviews
- Updates to the Product Backlog
- Customer Service can get some insight into when problems/issues are solved by tracking [the] project issue page.
- Releases can be accompanied with release notes that, if well written, can go straight to the client.
All products have room for improvement. The system improves over time with better and better integrations and I look forward to even more features without paying extra! The system has increased transparency across my organization and with this transparency comes increased throughput on projects. I don't think I can go back to any other system and we are definitely married to this product.