[Codex]

At the end of the day some people fail to understand that software development, no matter what the project, is not an exact science. And it's unfortunate that we live in a "I must have it now" society where some people find it hard to come to grips with the concept of patience.

Here’s an email trail of my experience at work …

Manager:

Hi Marc,
In <boss>'s absence could you please advise on the below?

Hi <boss>,
Could you please advise when our Team Leaders will have access to the Performance Calculator?

Me:

Hi <Manager>,

I'm unable to give an exact date, <boss> and I need to run some tests on the data your Team Leaders have provided us to make sure the calculator is reflecting accurate results before releasing it. I've set aside two weeks ( ) to get things finalised; however, <boss> has got the final say on when it goes live.

Manager:

Hi Marc,

Due to the fact that we need to deliver Performance Management Reviews now, can we aim to get this application ASAP? Or should I advise the Team Leader to deliver PMRs in the old excel docs?
This "unknown" is frustrating for the Team Leaders and Consultants.”

Me:

If the TL's need to deliver their Performance Reviews right now then by all means deliver them via the old workbooks.

I can appreciate the frustration. At this time though, we still don't have all the Team Leader’s half year results as requested, and all their workstation ID to deploy the Calculator. Also, I'm testing the integrity of the data that we do have through the calculator, and coding in the "print" function so the TL's can produce a hardcopy of the results.

Having discussed this with <boss> our aim is to have everything in place, ready to go for Team Leader's to start entering in April's results by May, and to have all the first half results stored and verified.

I hope this provides you with some clarity.

... this happened a day after demonstrating the application at a managers meeting and clearly stating that the application was not ready.

I feel for you Luthier