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