Scheduling change and then managing change are important aspects of the
software life-cycle, but a change is useless if it can not be delivered to
where it is needed in a timely, secure, reliable and repeatable method.
"Automating" deployment means that the way in which software change is
delivered is trace-able, repeatable - and incidentally, reversible. There is
great peace of mind that comes from knowing that any delivery can be
reversed, "un-done", rolled back.