There’s an exciting trend out there, especially among teams using distributed version control. It’s called story-branching, or issue-driven development. For each issue a team implements – user story, bug, spike, technical task – a new development branch is created. Madness?! You be the judge.
Story-branching protects your master code line and encourages innovation. Transferring work in progress to other branches helps keep master in a releasable state. And working in isolation on a branch gives developers more freedom to experiment.
This session will cover two common approaches to issue-driven development, as practiced by development teams at Atlassian, including a real-world demonstration showing how automation can neutralize potential branching and merging overhead for coders. Along the way, I’ll discuss how issue-driven development reduces logistical friction and helps teams deliver incremental value to their customers faster.
You must be a Member to view this post and you are currently not logged in.
You can either log in below or sign up here.