Who this is for
- Government and enterprise teams still on TFVC, SVN, or a source-control system nobody remembers choosing.
- Teams already on Git whose branching, review and release practice has grown tangled.
- Organisations moving to microservices, cloud or a new platform and wanting to fix delivery at the same time.
What an engagement includes
| Stage | What we do |
|---|---|
| Assess | Inventory every repository and application. Map dependencies, build pipelines and release cycles. Identify what must move first and what can wait. |
| Make the case | A written recommendation the whole team can read: the benefits, the risks, the plan, and the tooling choice (Bitbucket, GitHub or Azure DevOps) that fits what you already use, such as Jira. |
| Design the workflow | A branching model the team can hold in their head, commit and pull-request conventions, code-review expectations, and how releases and hotfixes flow. |
| Set up the tooling | Repository hosting, permissions, integrations, CI/CD pipelines and quality gates. |
| Train, hands on | Weekly sessions from Git basics to conflict resolution and rebasing, in sandbox repositories, until nobody needs the cheat sheet. |
| Migrate in phases | Repositories move one at a time, lowest risk first, with full history preserved. Dual running while the team adjusts. |
| Champion | A named Booolean engineer stays available to answer every "how do I..." for the life of the programme. |
Proof
For a NSW Government treasury agency, Booolean moved more than twenty applications from a legacy source-control system to Git on Bitbucket Server over a three-month programme, with weekly training and a branching model inspired by Git Flow. Every repository kept its history. The team did not go back.
We have also advised an Australian health insurer on moving microservices from TFS to Git, and designed TFS branching models that borrowed from Git practice for teams not yet ready to switch.
Beyond source control
Git is the foundation. Around it we set up the practices that make delivery dependable:
- Continuous integration with automated builds and tests.
- Database change under version control with Dubnium.
- Encrypted configuration in the repository with Cryptex.
- Browser test automation with Paxter.
- Coding standards, review checklists and onboarding documentation that outlast the engagement.
Read the story: Moving a government agency to Git.
Start here
Tell us what you are on today and how many applications are involved. We will scope an assessment and give you a realistic view of the path. Get in touch.