We use a form of Kanban during our development process, but the stories we complete throughout a release cycle all have the same fix version of "Product Version xxxx".
Previously, we could make intermediary WIP releases throughout the cycle simply by clicking the 'Release' button on the kanban board - we'd specify what this intermediary release was, and the stories would have this intermediary version ADDED to the existing main product release version. This was great, it allowed us to:
- Keep stories in the correct product version so we could look back at everything completed for the next actual released version
- Review and 'release' intermediary versions on the fly
With the new Release button, you only have the option to release a pre-defined version - it forces you to go through your stories BEFORE they are done and decide that they will be ' released' together. First off this seems to go a bit against the Kanban method, forcing you to plan a release rather than releasing on the fly when ready.
Secondly, in our specific cases, this forces us to re-open issues and bulk change them in order to append a version before we do our reviews and intermediary releases.
Does anyone have any similar issues with the new Release button? How did you get around it, or modified your workflow to better work with it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.