51279Release management in Scrum
- May 16, 2011Hi,
We are executing our projects Scrum way. We have releases for product, but the problem is for the next release planning we need some analysis for stories to give coarse estimates.
Since there is back to back release, we come to a dead lock situation wherein we have spillovers and support for earlier release.
The senior developer is always working on support and consultation for spill-overs. And when we start with the next release, release plan for the new work is always postponed as analysis is not done and release cannot be planned. So release planning for new release happens only mid-way after completing spillovers.
How do we solve this deadlock .
- Next post in topic >>