Agile Source code Management Using Stories, Agile Workflow, and CI
Free On-Demand Webinar
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.
From this session you'll learn how to:'
- Manage via user stories rather than files and branches.
- Create and manage a simple Agile workflow in source control using branches for each workflow stage.
- Leverage your workflow create a build using only stories that are 'done' or only stories that are 'tested'.
- Take advantage of continuous integration to improve the flow of your workflow.
- Avoid the problem of building up inventory when using branches.
- Avoid creating integration delays when using branches.
- Reduce manual merging and conflict resolution using this method vs other methods.
- Apply this approach for both a single small team and a large distributed effort composed of 40+ Scrum teams.