I can understand Commit Dates being of benefit if users and PMs are
acutely aware of them and actively managing them. However, my experience
is that more often than not, Commit Dates get set automatically to the
Planned Date when the user clicks 'Work On It'. Then, when the PM later
changes the Planned Dates of the Task, the end user doesn't go back and
change their Commit Date (and the PM can't change the Commit Date for
them). The user also still sees the Commit Date displayed prominently as
t...