Devops for Growth

Git-flow Trunk-based As far as possible from main branch As close as possible to main branch New features started from develop branch Short-lived feature branches started from main branch New release branch derived from develop branch, after stabilized release branch deployed Main branch always in a state ready to be deployed to production Only hotfixes derived from main branch Hotfixes start from main or release branch, need to be cherry-picked back to main

Git-flow Trunk-based Lack of seniority within the team Well-composed and experienced team Working with other vendors/third-party Team augmentation model

Git-flow Trunk-based Complex, mature, monolithic product Microservices Brown-field product Modern single page application (SPA) / Mobile apps   Proof-of-concept (POC) / Prototype   Distributed system components

Git-flow Trunk-based Governed Team-driven

Git-flow Trunk-based Various deployment models used Continuous Deployment practices recommended, such as feature toggles, quality gates, canary testing, self-service automation (e.g.. ChatOps), and monitoring

Git-flow Trunk-based Slower release cadence, pre-determined schedule Teams able to iterate quickly and independently