Independent iteration plans for teams of same project area
We have one project area containing many team areas and we use Eclipse Way process. When it comes to ietration and ietration planning, there seems to be confusion.
We are told that development lines, iterations, start and end dates, and the current iteration designation are defined in the project area overview Process Iterations list. So we cann't modify them in individual team area? And it seems that we are allowed to create new iteration plan against the current iteration in the team area.
The question is that when teams create their ietration plan against the same iteration, then it seems that all work items added to their plans will show up in each team's own Planned items. And what if one team wants to have its own private iteration and plan? It seems we can only do this at project area level and then tell other teams not to use it but the work items will show up anyway.
It seems that under Jazz SCM, each team can create their own stream and then create change set on it to keep the privacy. But if we associate the work items with the change set, they become public again.
Is this designed behaviour?
We are told that development lines, iterations, start and end dates, and the current iteration designation are defined in the project area overview Process Iterations list. So we cann't modify them in individual team area? And it seems that we are allowed to create new iteration plan against the current iteration in the team area.
The question is that when teams create their ietration plan against the same iteration, then it seems that all work items added to their plans will show up in each team's own Planned items. And what if one team wants to have its own private iteration and plan? It seems we can only do this at project area level and then tell other teams not to use it but the work items will show up anyway.
It seems that under Jazz SCM, each team can create their own stream and then create change set on it to keep the privacy. But if we associate the work items with the change set, they become public again.
Is this designed behaviour?
2 answers
ghu wrote:
structure and teams are associated to developments. By doing so all
teams of a project follow the same 'rhythm'.
work item show up on the plan, its planned for attribute must match the
selected iteration and its category must be assigned to the selected
team (to see the category-team-associated open the Project Area editor
and select the Work Item Categories tab). Because a category belongs to
one team only, work items don't show up on different iteration plans.
--
Cheers, Johannes
Agile Planning Team
We have one project area containing many team areas and we use Eclipse
Way process. When it comes to ietration and ietration planning, there
seems to be confusion.
We are told that development lines, iterations, start and end dates,
and the current iteration designation are defined in the project area
overview Process Iterations list. So we cann't modify them in
individual team area? And it seems that we are allowed to create new
iteration plan against the current iteration in the team area.
This is by design. The project defines the development line/iteration
structure and teams are associated to developments. By doing so all
teams of a project follow the same 'rhythm'.
The question is that when teams create their ietration plan against
the same iteration, then it seems that all work items added to their
plans will show up in each team's own Planned items. And what if one
team wants to have its own private iteration and plan? It seems we
can only do this at project area level and then tell other teams not
to use it but the work items will show up anyway.
Iteration plans are always scoped for a team and an iteration. To make a
work item show up on the plan, its planned for attribute must match the
selected iteration and its category must be assigned to the selected
team (to see the category-team-associated open the Project Area editor
and select the Work Item Categories tab). Because a category belongs to
one team only, work items don't show up on different iteration plans.
--
Cheers, Johannes
Agile Planning Team