Contacting me by email is best to talk about any work I can do for your company: paul@hammant.org

I visit your enterprise software team, to help you change your branching model to Trunk-Based Development (TBD). I come to an understanding of how you develop and deploy software, with lots of questions to stakeholders and leaders, and then come up with a plan that gets you to your goals. Other than Trunk-Based Development, areas for questions, recommendation (and training) often stray into:

• Branch by Abstraction (I was the pioneer), and Feature Flags/Toggles (goes hand in hand)
• A second pivot to a Monorepo design and optionally a directed graph build system like Buck or Bazel
• Regular DevOps aspects around how to engineer Infrastructure as Code (IaC), and scaled Continuous Integration infra
• Agile enablement factors, including the flow of stories from backlog into development
• Good Behavior Driven Development (BDD) phrasing for work - for the least amount of defects during development
• Speedy test automation, featuring the correct testing technologies and Service Virtualization
• economic benefits for the proposed changes
• case studies that show the way, both industry ones and those I was pivotal for, myself

I have performed many assessments over the years. The beginning of those was via ThoughtWorks (a well known consultancy), twelve years ago, bore the title Agile assessments. Later ThoughtWorks would sell Continuous Delivery (CD) assessments as the techniques emerged and Jez Humble and Dave Farley’s CD book came out (that uses some of my diagrams). Most recently, ThoughtWorks sold DevOps assessments, extending the pieces that came before. Many of those were as a ‘Principal Consultant’, but more recently some have been as a solo operator.

I have presented findings to CEOs, CIOs and executive teams. I have seen clients say ‘yes’ to everything I have recommended, and implement them. I have also seen clients struggle to implement changes as their commitments, constraints and old habits put pressure on them to maintain the status quo. I have crafted my practice and honed my approach after tens of these assessments rather than break through to a higher-throughput place. Many times I have done follow-up visits to help measure progress towards goals for clients that want to run the execution of the plan on their own.

• I lead the creation of the info portal TrunkBasedDevelopment.com
• I am the person who has written most about Trunk-Based Development, generally
• I have implemented Trunk-Based Development migration plans for large enterprise development teams many times
• I am the first person to write about Branch by Abstraction, which former colleagues Martin Fowler and Jez Humble went on to write about too.
• I am able to help you move past simple Trunk Based Development and towards Google’s Monorepo design.
• I know how to massively reduce your test automation times using Test Impact Analysis (TIA)
• I have previously had Snr. Director of Engineering (2x), Chief Science Officer and Head of Development roles (but have otherwise coded during and before/after work for twenty-eight years)
• I have consulted inside Google (the Test Mercenaries team), a few US banks, a famous US budget airline, retailers, fin-tech and other startups
• I worked at the industry-leading ThoughtWorks (as mentioned), making my contributions to their canon
• I co-created the industry standard web testing technology, Selenium, back in 2004
• I co-created the first Dependency Injection Container that used Constructor Injection in 2003
• I and my materials are referenced in Continuous Delivery, Lean Enterprise, and The DevOps Handbook over the last seven years.
• I have been blogging about a wide range of software development topics since 2002