Thank you for your interest and continued support.
This is Takahashi from the Marketing Plan Research Laboratory.
We sometimes receive (proposed) project schedules from clients regarding system development.
I myself sometimes present a schedule to my team and assign tasks with the deadline as one of the goals.
The longer a schedule gets, the less likely anyone is to actually try to meet those deadlines.
Strangely enough, even the person creating the schedule often thinks, “We probably won’t be able to meet this deadline,”
and hand it over to someone else.
What is the point of a schedule that neither the creator nor the viewer believes in?
I can’t help but feel that such a schedule has little
other than to extract approval or money from someone (pardon my crude language).
The key to minimizing overall schedule delays is to create multiple project schedules with the shortest possible timeframes
and presenting them in small increments—that’s the key to minimizing overall schedule delays.
I believe the same principle applies to the day-to-day operations of each of our clients.
Please take this as a general reference and adapt it to your specific situation.
That's all, Thank you for reading.
------------------------------
■ Previous / Next Column ■
<<< Next Column Vol.3 - Ordering a system from an acquaintance leads to trouble 2010.08.01
>>> Previous Column Vol.1 - Too busy to think about your system? 2010.06.01
Sending your message. Please wait...