Juicy questions, Vazgen! Having hit this a couple of years ago when we created our "https://store.atappstore.com/products/all/" Resource Contouring solution -- we decided that protecting a carefully crafted (and time consuming) contour was the MOST important priority, and therefor went with the following:
Allow contouring at the Day, or Week, or Month level (but storing under the hood at the day level), for a more efficient and pleasant user experience
Allow people to change the Planned Hours or the Duration at the Task level in a way that also preserves the current contour (to avoid rework)
Prevent saving the data in an imbalanced state (e.g. "Please correct the imbalance"), to ensure data integrity
Highlight any imbalance in red when such a change (e.g. "extra planned hours, longer duration) occurs
Update the imbalance visually as the end user adjusts the contour accordingly (e.g. adding hours at the end)
Restore visual normalcy (e.g. back to green) once the imbalance is removed
BONUS as there a number of standard use cases in this area, we also invented a few right click helpers (e.g. front load, back load, spread remaining balance evenly until end of duration, etc.) to help project managers adjust their plans more effectively
I'm very interested to see how other folks answer this one -- both Vazgen's initial questions, and any thoughts on the decisions we went with in our solution. Regards, Doug Doug Den Hoed - AtAppStore
