Hi All,

Hopefully this is the correct forum to start this discussion.

I have been using the Enhanced Release Burndown plug-in (very nice) that is supposedly going to be integrated with RTC 3.0. What I'm looking for is getting support out of RTC and the Enhanced Release Burndown that allows for an ideal plan line to be "curvy" based on resource changes across the release. If we could assign a "resource unit (floating point value)" value to iterations, the release burndown can project a more true expected burn. Resources come and go in our projects. Summer months have less capacity due to vacations. We don't want different sized time boxes. Velocity would then be points completed divided by "resource units" for the iteration.

Thoughts?