It's all about the answers!

Ask a question

Iteration Plans and hierarcical team organizations


Thomas Frauenhofer (621) | asked Feb 26 '09, 2:21 p.m.
I am looking at using Jazz for a project which we have decomposed into several sub-projects. What I would like to do is divide these sub-projects so they have their own teams and then track the work items in a single iteration plan. The reason I want to have the different teams is to provide a little protection (such as who can remove a component from a stream, etc.).

So my team hierarchy looks as follows:

Top-level Team
|
+--> Child Team 1
|
+--> Child Team 2

The problem is that I would like to build a single iteration plan that includes work items for Top-level Team and all child teams, but that doesn't seem to be possible. When an iteration plan queries work items it only looks at the team associated with a work item - it doesn't seem to be able to "walk up the team hierarchy" to determine if it should include it in the plan. So if I have a work item that is associated with Milestone M1 and Child team 1, then an iteration plan for Top-level Team will not see it.

Is this correct? Is there any way to configure an iteration plan to include work items for an iteration that are associated with child team areas?

Thanks in advance.

One answer



permanent link
Johannes Rieken (1.2k1) | answered Feb 27 '09, 5:18 a.m.
frauen1 wrote:
I am looking at using Jazz for a project which we have decomposed into
several sub-projects. What I would like to do is divide these
sub-projects so they have their own teams and then track the work
items in a single iteration plan. The reason I want to have the
different teams is to provide a little protection (such as who can
remove a component from a stream, etc.).

So my team hierarchy looks as follows:

Top-level Team
|
+--> Child Team 1
|
+--> Child Team 2

The problem is that I would like to build a single iteration plan that
includes work items for Top-level Team and all child teams, but that
doesn't seem to be possible. When an iteration plan queries work
items it only looks at the team associated with a work item - it
doesn't seem to be able to "walk up the team hierarchy" to
determine if it should include it in the plan. So if I have a work
item that is associated with Milestone M1 and Child team 1, then an
iteration plan for Top-level Team will not see it.

Is this correct? Is there any way to configure an iteration plan to
include work items for an iteration that are associated with child
team areas?


You are right, plans do not include work items that belong to a child
team area. I have created an enhancement request for this:
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/72693.
Feel free to subscribe and participate in the discussion.


--
Cheers, Johannes
Agile Planning Team

Your answer


Register or to post 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.