It's all about the answers!

Ask a question

One team one Timeline contrary to customers reality


Ralph Schoon (63.2k33646) | asked Aug 20 '09, 1:41 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi,

I ran into a customer project where the requirement to map a team to one timeline rather deviated from their reality.

They have several teams that do the development as expected. But the way they work with customers and their customers requirements force them to deliver special releases that are usually shifted for some period of time based upon a common code stream.

Creating all the teams needed to manage that with the way RTC handles it today would create rather big administrative overhead.

They would rather require several timelines that run in parallel in various rhythms and teams work against the different timelines in parallel.

This would make load management for them easier too, assuming that a person works x% for the team and needs to split the work on different timelines the load would probably balance over all the work the person needs to do in parallel.

I am sure there are caveats with this approach too. However I think I read similar statements here and I have been in contact with people with i believe similar requirements.

Are there any considerations to advance agile planning to support other models of mapping teams and timelines?

Thanks,

Ralph

Accepted answer


permanent link
Geoffrey Clemm (30.1k33035) | answered Aug 20 '09, 8:12 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The main thing to ask yourself is "what are you trying to share here"?

It sounds like the main thing you are trying to share is team membership
(i.e. who is on a team and what role they play). You then want this
team definition to be shareable in multiple team areas.

Or stated otherwise, you'd like to be able to say "I inherit my team
membership from this other team area".

I've submitted work item 90831 to track this idea/request.

And if this wouldn't address the issue you raised, please elaborate (:-)

Cheers,
Geoff

rschoon wrote:
Hi,

I ran into a customer project where the requirement to map a team to
one timeline rather deviated from their reality.

They have several teams that do the development as expected. But the
way they work with customers and their customers requirements force
them to deliver special releases that are usually shifted for some
period of time based upon a common code stream.

Creating all the teams needed to manage that with the way RTC handles
it today would create rather big administrative overhead.

They would rather require several timelines that run in parallel in
various rhythms and teams work against the different timelines in
parallel.

This would make load management for them easier too, assuming that a
person works x% for the team and needs to split the work on different
timelines the load would probably balance over all the work the person
needs to do in parallel.

I am sure there are caveats with this approach too. However I think I
read similar statements here and I have been in contact with people
with i believe similar requirements.

Are there any considerations to advance agile planning to support
other models of mapping teams and timelines?

Thanks,

Ralph
Ralph Schoon selected this answer as the correct answer

One other answer



permanent link
Ralph Schoon (63.2k33646) | answered Aug 21 '09, 12:41 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Thanks Geoff,

i will try to gather more details.

Ralph

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.