Comments on "Lateness"

The scheduling method defines in this lecture that is   often implemented under the constraint of a described deadline.  If best estimates indicate that the deadline is unrealistic a competent project manager should protect her or his team from under pressure reflects the pressure back to its originators.

To describe, suppose that a software development set has been asked to develop a real time controller for a medical diagnostic instrument which is to be introduced to the market in nine months.   After the careful estimation and risk analysis the software project manager comes to the conclusion which the software as requested will need 14 calendar months to build with available staff.  How does the project manager process?

It is not realistic to march into the customer's office and demand in which the delivery date be changed. External market pressures have been dictated the date and the product must be released.    It is simultaneously foolhardy to refuse to undertake the work. So the question is what to do?

The following steps are recommended in this condition:

1.    Perform a detailed estimate using data from previous projects. Which determine the estimated effort and duration for the project?

2.    By using  an  incremental  procedure  model  build    a  development planning  which  will  deliver  critical functionality through the imposed deadline but delay other functionality until later. The Document planned.

3.       Meet with the customer and explain why the imposed deadline is not realistic.  Be certain to note which is estimate are based on performance on previous projects.  Also be certain to indicate the % improvement which would be needed to get the deadline as it presently exists.   The following comment is appropriate:

I thing we may have a problem with the delivery date for the ABC controller software.  I have given each of you an abbreviated breakdown of production rates for previous projects and an estimate that we have done a number of various ways.  You will note that I have supposed a 20 % improvement in previous production rates but we still get a delivery date that's 14 calendar months rather than nine months away.

4.    Offer the incremental development planning as an alternative.

We have a few options and I would like you to make a decision based on them. 1^st, we can rise the budget and bring on additional resources so that we will have a shot at getting this job done in 9 months. But understand which will increase risk of poor quality due to the tight time line.   2^nd, we can erase a number of the software capabilities and functions that you are requesting.  This will make the preliminary version of the product somewhat less functionality and then deliver over the 14 month time.  3^rd, we can dispense with reality and wish the project complete in 9 months.  We will wind up with nothing which can be delivered to a customer. The 3^rd option I hope you will agree is unacceptable. Past history and our best estimates say which it is unrealistic and a recipe for disaster.

There will be some grumbling but if solid estimates based on good historical data are presented, it's likely that negotiated versions of either option one or option two will be chosen. The not realistic deadline evaporates.