How do I create a sprint plan for multiple teams?
Hi all,
I had opened a feature request for this and apparently this has already been implemented in 2.0 M3, but I don't understand how to do it. To give quick context, here's the hierarchy structure of my teams in RTC: Release x.x team -- Architecture -- Development -- QA -- ID I also have a hiercharchy for my categories: Architecture -- Install -- Component -- Runtime Development -- Install -- Component -- Runtime QA -- Install -- Component -- Runtime ID -- Install -- Component -- Runtime What I would like to do is to associate the correct team to each category in order to be able to track where the teams are spending their time. I want to be able to select any one of the teams and generate a burndown chart for them. Currently in RTC 1.0.1, you must create one sprint plan per team area in order for this to work, because if you select the root team area (Release x.x team), all it's sub teams are not inherited automatically in the sprint plan. I do not want to create multiple plans because it's too much overhead. We currently have all our teams add their work to the same sprint plan. This works because all of the categories are assigned to the same team (Release x.x team) instead of the individual teams. When I opened my feature request, I got notified this capability was already available in RTC 2.0 M3. We've deployed it internally on a test machine and I can't figure out how to do it. When configuring a plan, I now see two options though for Team Members. I see Project Area and Team Area. The Team Area option seems to be the same as it was before. When I select a project area, I get a message when I open my sprint plan that there are no categories associated with the project area. I'm not sure how I'm supposed to fix this problem. If I go in the Project Area editor in the Work Categories tab, all categories have a team area associated with it. I'm not sure how to associate a category with the project area itself. Can anyone please clarify this for me? Can what I want to do really be done now? Regards, Steffan |
5 answers
ssurdek wrote:
Hi all, What you are looking for are plan types. We now have three different kinds of plan types: # Iteration Plans - as known from RTC 1.x # Team Release Plans - All work items from a team/project and an iteration plus all child iterations # Project Release Plans - All work item from a team/project plus all children and an iteration plus all child iterations. Categories are orthogonal from this. In order to associate a work item with a team/project, you must associate a category with it. This is done in the Project Area editor. If a category has no team assigned nor inherits one it is associated with the project area. -- Cheers, Johannes Agile Planning Team |
I am having the same problem as original poster. How does one create those three types of iterations you mention below? The Plan dialog gives options Product Backlog, Team Backlog, Spring backlog, and Schedule Risk. But not those you mention below. The planning article (http://jazz.net/library/article/203) does discuss your plan terms below, but if I follow its example of selecting Product Backlog for a the Product Backlog (aka Product Release Plan) I get the same error as the original poster. It would be simple if the dialogs simply gave the options you list below. Very confusing... ANy help is appreciated.
ssurdek wrote: |
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 10 '09, 11:48 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In order to associate a category with its project area, remove its
association to a team area. To remove its association to a team area, you first use "disassociate" if you've explicitly associated it with a team area. Then if its parent category is associated with a team area, you also need to select "Use Default" to disassociate it from the team area of its parent category. Not quite sure why the team picked the rather unintuitive (to me) verb "Use Default" ... perhaps someone from the process team can comment on that terminology question. WRT the names of the plan types, those were picked to try to allign with the terminology of that process type. But if you don't like the name they have by default, just go into the Process Configuration page, and select ProjectConfiguration:ConfigurationData:Planning:PlanTypes. Then select the plan type you want to rename, and give it a new name. Cheers, Geoff harryk wrote: I am having the same problem as original poster. How does one create |
|
Thanks Geoff - great answer. For those that bump into this thread, the process XML defines the three plan types below and they are discussed in the RTC Plans documentation (I assume releasePlan is 'Team Release Plan' in the docs and Schedule Risk is an iterationPlan). Are there any other plan type in RTC other than those three? Also interesting is I could only change the plan names in the XML, the editor text field appears read-only.
http://publib.boulder.ibm.com/infocenter/rtc/v2r0m0/index.jsp com.ibm.team.apt.planitems.iterationPlan com.ibm.team.apt.planitems.releasePlan com.ibm.team.apt.planitems.projectReleasePlan |
|
harryk wrote:
I am having the same problem as original poster. How does one create The plan types you can select depend on the process template you use. So the name may differ from project to project. Still, how work items are selected and what makes them appear on a plan is still the same. In case you selected a project area as plan owner you have to ensure that a category is associated with it. To do so, open the Project Area editor, select the Work Item Categories tab and ensure that a category hasn't a team area associated *and* does inherit a team area association. This will, implicitly, associate the category with the project area. -- Cheers, Johannes 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.