The customer alerted us to a multi part problem they needed fixed. The project manager asked our team to estimate how long it would take to correct each piece. We procided a high fidelity estimate. That resulted in a schedule of release for each part of the fix.
On the day when the first part of the fix was supposed to be delivered, the customer asked the project manager if we were sending out the fix. That resulted in him asking the developer assigned whether this thing was ready to go out. I came in to work and had a call from that developer asking what exactly the customer problem was. Fail!
Luckily the first part of the fix was a well known issue. I walked the developer through the steps to reproduce the problem. Then I showed the developer the database table that controlled the erroneous config info. The developer proceeded to generate a fix. However the fix was not ready until late at night. The test team was surprised that they were asked to do the fix late in the evening. Thus it did not get done.
The project manager warned this developer to make sure the second part of the fix was going to be on schedule. Let's hope the developer takes this lesson to heart.
Performance Tricks in Other Databases - I have been working exclusively with the Oracle database for over 15 years. Now I have jumped to a project that uses the Greenplum database. This is a dis...