Hi there,
I am working on different Releases (say Release A, Release B) at the same time in one Backlog and in a sprint.
Release A might be usability stuff or bug fixes that will be released in pretty short iterations while Release B might take me a while have a working version cause it's a way more complex starting from scratch feature.
Apparently the issues in backlog (with both Releases) won't be ordered like:
issue 01 - release A
issue 02 - release A
issue 03 - release A
issue 04 - release B
issue 05 - release B
issue 06 - release B
but more like:
issue 01 - release A
issue 02 - release B
issue 03 - release B
issue 04 - release A
issue 05 - release A
issue 06 - release B
Does the Release Burn Down Report considere that I there are different releases I work on or does it predict the sprints left to finish a release assuming that I work on e.g. Release B only?
Regards
Martin
