How to manage workload across multiple development lines?
We're trying to deploy RTC (1.0.1.1) for a few teams in my organization that have both new development and several service releases. These releases run in parallel with the same people doing work on multiple releases at the same time.
We created a development line for each service release and new release. But we have discovered we cannot manage the team's workload across these multiple releases (development lines). We can see how a person is booked for a particular release, but not their overall capacity.
And in a given week, other tasks arise that affect how much time is spent on each of the releases they're currently working on.
How have other teams handled this in RTC?
And, does anyone know if RTC 2.0 will address this limitation?
We created a development line for each service release and new release. But we have discovered we cannot manage the team's workload across these multiple releases (development lines). We can see how a person is booked for a particular release, but not their overall capacity.
And in a given week, other tasks arise that affect how much time is spent on each of the releases they're currently working on.
How have other teams handled this in RTC?
And, does anyone know if RTC 2.0 will address this limitation?
One answer
linden wrote:
Right, in 1.0 this is not possible. You can manage/view load only for a
single team area (which is always bound to a development line). In RTC
2.0 you'll be able to configure the Team Load view to show load for a
project area (or team area). Similar, it will be possible to create
plans that are 'owned' by a project area.
--
Cheers, Johannes
Agile Planning Team
We're trying to deploy RTC (1.0.1.1) for a few teams in my
organization that have both new development and several service
releases. These releases run in parallel with the same people doing
work on multiple releases at the same time.
We created a development line for each service release and new
release. But we have discovered we cannot manage the team's workload
across these multiple releases (development lines). We can see how a
person is booked for a particular release, but not their overall
capacity.
And in a given week, other tasks arise that affect how much time is
spent on each of the releases they're currently working on.
How have other teams handled this in RTC?
And, does anyone know if RTC 2.0 will address this limitation?
Right, in 1.0 this is not possible. You can manage/view load only for a
single team area (which is always bound to a development line). In RTC
2.0 you'll be able to configure the Team Load view to show load for a
project area (or team area). Similar, it will be possible to create
plans that are 'owned' by a project area.
--
Cheers, Johannes
Agile Planning Team