Branching Strategies Ultimately Determine Product Complexity

The ideal DevOps project starts with everything stored in source control. As a coach I often find that too little thought is given to how a team will handle their source control branching strategy. Time and time again I have seen how this lone decision determines much of the complexity of both product and process. The ease of your journey to continuous delivery is largely dependent on this decision. I’d like to discuss this idea and talk about teams seeing success when they take time to make this decision and don’t just buy into master-only development or a model such as git flow. Instead, they think about how they want to manage complexity, and it starts with source control and branching strategy.



Logan Daigle


Logan is a DevOps Coach with VersionOne from Charlotte, NC. He has been involved with providing and implementing DevOps solutions since 2011. He has development and DevOps experience in the military, government, healthcare, retail and finance industries. Logan has a passion for being Agile, doing DevOps well and using agile engineering practices to build, test and deploy software. His experiences have been in support of both Windows and Linux infrastructure, and many tools that are key to the success of applications in both. He is currently focusing on evangelizing in the technology community to bring DevOps to the masses. You can follow Logan on Twitter @TheDevOpsGuru.