Agile Source Code Management using Stories, Agile Workflow, and CI
Add to calendarYou 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.
This is a cross between a tutorial and a demo, illustrating how these techniques have been used in the real world with both large and small teams. While the techniques will be demonstrated using AccuRev as the change management tool and Cruise Control as the CI tool, the focus is on the patterns and techniques for managing source code with stories, simple workflow, and CI that can be implemented with a variety of tools.
The combination tutorial/demo will be 25 minutes, allowing 20 minutes for Q&A.
- How to manage via user stories rather than files and branches.
- How to create and manage a simple Agile workflow in source control using branches for each workflow stage.
- How to leverage your workflow to do things like create a build using only stories that are “done” or only stories that are “tested”.
- How to take advantage of continuous integration to improve the flow of your workflow.
- How to avoid the problem of building up inventory when using branches.
- How to avoid creating integration delays when using branches.
- How to reduce manual merging and conflict resolution using this method vs other methods.
- How to apply this approach for both a single small team and a large distributed effort composed of 40+ Scrum teams.
