Effective Multi-team Planning
All,
A question in general for the larger teams. How are you using plans for large multi-team environments with short sprints (2-weeks)?
Scenario:
5 teams of 8, and an additional 30 people who "aren't in a team"
Do you create a plan with the owner (ProjectName) and group by Team per sprint? (Thereby having one plan per sprint.)
or
Do you create a plan with the owner (Team) and group by Owner per sprint? (Thereby having 5 plans per sprint catered to the specific teams so they can monitor their own work.)
thanks
One answer
This type of question is really up to the administrator to determine based on how the team best works.
In house, one of my projects works in a combination. One team does not have a major amount of work and uses the project plan to track work. The second team is actively adding new features and uses their own plan to track the work.
Internally for RTC project development, each plan is owned by teams:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.apt.search&predef=current&tq=1383073261000
For larger projects, it is better to have multiple plans per sprint to cater to each specific team. Is it possible to combine the 30 people into a logical team to fit into this type of model?
In house, one of my projects works in a combination. One team does not have a major amount of work and uses the project plan to track work. The second team is actively adding new features and uses their own plan to track the work.
Internally for RTC project development, each plan is owned by teams:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.apt.search&predef=current&tq=1383073261000
For larger projects, it is better to have multiple plans per sprint to cater to each specific team. Is it possible to combine the 30 people into a logical team to fit into this type of model?