You create iterations from a backlog of user stories managed via a taskboard with a simple “workflow” from “todo” to “done.” You use Continuous Integration. But in your source control system you’ve just got files and branches. You could create a branch for every story, but that’s a lot of branches to manage! How can you ask the source control system which versions/files correspond to the stories that are done in order to build the “done” version and do exploratory testing? This session will show how to manage changes using stories and how to use branches to represent your workflow.
One of the biggest problems when managing Agile projects is to decide when and how to integrate a story. Traditional versioning tools offer poor support to branching and merging so it’s hard to select specific stories at the end of a sprint. In this talk, we present Git—a modern, distributed version control system—and an Agile versioning process using it that will help Agile Developers to solve those issues, offering a way to have a continuously releasable branch and also minimizing merging problems.