How we stopped worrying and learned to love Agile versioning

room: Grand Ballroom C North — time: Tuesday 16:45-17:30
Level: Practicing

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.

Process/Mechanics

During this talk, we will go through the following points:

  1. Why we need Agile versioning
  2. How we did versioning
  3. How we do Agile versioning
  4. The failure of traditional versioning tools
  5. The advantages of separate story branches
  6. How Git fits into an Agile versioning process
  7. Release environments
  8. The drawbacks of separate story branches
  9. Further improvements
Learning outcomes
  • The benefits and drawbacks of separate story branches, the core of Agile versioning
  • Why traditional versioning tools fail to support Agile versioning
  • Versioning as support for prioritization
Featured participants
Primary target persona
Reviews

No reviews

Subscribe to an RSS feed of reviews of this proposal Syndicate content