We are using the sprint Burndowns to forecast delivery dates and to measure progress against deadlines. This is being used across multiple new teams. We have several Fix Versions set up for each team which map to our actual releases.
We now have completed 3 sprints for some of the teams and have established a velocity in Jira .
However, one of the teams is completing MVP1.0 and moving into MVP1.1, the release burndown for MVP1.1 is stating that it requires 3 sprints to be completed..... but the team has already established a velocity from MVP1.0. If for every release 3 sprints are required this renders the report useless unless you have releases far into the future.
Any guidance or workarounds on this would be great?
