I need a good way to plan a release using Scrum that will take into account Date vs. Feature driven releases, multiple teams with varying velocities and backlogs, and feature and schedule buffering. This tool should take into account story priority (Musts vs. Shoulds) and be able to tell me when a team/project will be done with their backlog at a given velocity or how many and which stories I will get by a given date per team and per project.
by: Mike S. | over a year ago | Other
Comments
Projected end date would also be useful. The ability to easily change the end date of one release and the start date of another (some how link them). An easy way to see the "big" items in a release. In general the UI should help me plan the release.
Release Planning is a major reason we purchased a tool at all. The feature described here would be very helpful to us.
We could really use a calendar function to id the tasks & days needed to go through production release steps at the end or a Sprint. Currently using a SharePoint calendar to compensate for this missing function which needs to be visible to other areas of IT.
We could really use a calendar function to id the tasks & days needed to go through production release steps at the end or a Sprint. Currently using a SharePoint calendar to compensate for this missing function which needs to be visible to other areas of IT.
Production release steps should be their own sprint, so not sure why you are tracking in sharepoint.
Also, see related Idea submission: https://ideaspace.versionone.com/default/Idea/Detail/224
Really need to track individual stories in release as mentioned above.
The release scheduling page redesign in Winter '14 created a view that covers various methods of planning with capacity vs. planned work at both the release and team levels. We missed updating this idea at that point.