Reasons I wish retroratcheting (and by extension autoratcheting) moved the road up or down (based on yaw) instead of to the left:
- Retroratcheting wouldn’t move breaks, allowing for a goal with planned breaks to be retroratcheted.
- Retroratcheting wouldn’t mess up weekends off.
- The weekends off feature could schedule breaks to the end of the goal, instead of just the next weekend, making it possible to see what the current plan will result in.
As it is now, if you have weekends off, only the next weekend is scheduled, presumably to reduce the damage from autoratcheting. This results in an overly-optimistic value at the end of the road, since it doesn’t take into account all the weekend breaks that will be scheduled between the current weekend and the end of the road.
This is important to me because I’ve switched to explicitly using my contract time goals as my schedule when generating date-of-completion estimates for my clients. A road that overestimates the number of hours completed at the end of the road creates overly-optimistic estimates for my clients.