Story in Iteration don't display children from other sprints
In RTC we have a Iteration backlog plan defined and various Iteration sprint defined under that. We would keep our Stories in the Iteration backlog plan, create tasks as children of the story and move only the tasks to the 2 week iteration sprint associated with the timeframe we were working the sprint. Various tasks associated with the Story would span multiple sprints
In RTC release 1 if we used the Folder View we were able to see ALL of the task as children associated with the Story when we opened up the tree structure. A little arrow next to them would say which iteration they were actually in. This was very helpful. With RTC release 2 this no longer works. Only tasks associated with the Iteration backlog plan show up. We now have to go into the link section of the Story to see all the children (if they are in other sprints). It is better for us to see the children in the iteration plan Is there a way now to see all the children that span sprints under the Story in the Iteration backlog (like was done in RTC release 1). |
3 answers
For RTC 2.0 we worked hard to be more SCRUM conform, but this also means that we had to change the way some things work:
We introduced a "Epic" work item type, which is intended to span multiple sprints. Multiple story work items can be created as children of epics, splitting up the epic in smaller pieces. The stories are intended to be planned for a specific sprint. Finally, one or more Task will be created for the real implementation, as children of the story. Now you can create a "Product Backlog" plan, create the epics and stories in "Work Breakdown" mode, prioritize and stack rank them in the "Backlog" mode and finally plan the stories for a specific sprint in the "Iterations" mode. Create an "Sprint Backlog" plan for each sprint, the stories planned for the respective sprint show up in there. Again, you can use the "Work Breakdown" mode of the sprint backlog plan to crate the tasks, prioritize and stack rank the execution items in the "Backlog", and track the progress during the daily scrum in the "Developers Taskboard" If you migrated from 1.0, you might not see the Epic work item type. Please manually merge this from a Scrum project area created with RTC 2.0 -- MikeS Jazz Agile Planning team lsutclif wrote: In RTC we have a Iteration backlog plan defined and various Iteration |
|
Thanks for the reply. How do I manually merge this from a SCRUM project?
Also can you point me to any documentation on this new way of doing things. For RTC 2.0 we worked hard to be more SCRUM conform, but this also means that we had to change the way some things work: In RTC we have a Iteration backlog plan defined and various Iteration |
|
lsutclif wrote:
Thanks for the reply. How do I manually merge this from a SCRUM A possible way of achieving this is to create a new SCRUM project area on a test server. Then go to the process specification source tab, copy the XML and use your favorite diff tool to merge the changes in the process specification source found in your real project area. Be extra careful that all ID references in the merged XML are resolvable - its recommended to test this upgrade on a staging server and not on the production repository. There's story 87605 (https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/87605), which tracks the progress of making the upgrade of existing project areas easier. As for the documentation, there are a few articles that explain the new RTC 2.0 planning features: - Getting Started with Planning (http://jazz.net/library/article/203) - Effective Planning (http://jazz.net/library/article/197) -- MikeS Jazz Agile Planning team |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.