Overlapping Releases

Follow

Comments

3 comments

  • Avatar
    Chris Leon

    We do this with two trees:  Release->Release Patch->Story and Iteration->Story.

  • Avatar
    Ron

    We've been discussing this as well and are moving to a model similar to Chris.


    Release >Feature > Story and


    Iteration > Story


    The reasoning behind having 2 seperate trees is that Iterations are time based (weekly) while Releases are deployment based, at least in our case. As a result we could potentially have releases that bridge iterations and iterations that bridge releases depending on the needs of the customer.

  • Avatar
    Wes Williams

    thanks for the ideas, I think two trees is more complex for my simple situation which generally has one week of overlap and minimal work on the previous release.

Please sign in to leave a comment.