Anatomy of a Project
Aug. 20th, 2004 02:13 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
kingandyThree weeks ago we were given a task: Implement a reporting process that will tell the client how much each department is spending each month. Meeting with director to discuss this. Only one out of the two developers assigned is present, due to having a baby (wife).
Over the next two weeks we work out how to use the godawful reporting tool (which the director loves because he never actually has to deal with it) and manage to wrestle together some sort of data on which to report. All through this time we are labouring under best guesses and half-truths, as we have yet to be presented with an absolute spec regarding exactly what it is we're supposed to be reporting on.
This week we finally got specs. Sort of.
On Monday we thought we had a spec.
On Tuesday we were assured that a different spec was the right one.
Wednesday (the day before the deadline we were given) we were given yet another spec. And told that the data was wrong somehow.
Yesterday we sorted one of the filtering problems with the data (with the help of one of the clients' staff who appears to actually have his head screwed on right), and were told to send it over again. Team Leader talked it through with the client contact, and assured me it would do. So naturally this morning I got a mail back from the client contact, which in her typical helpful and useful habit of sending full and complete information on the problem consisted of exactly one sentence:
"What is this, the figures are wosre than before."
Blindingly helpful.
This morning I've exported this data, using different constraints and table joins, about three times. Poor Saleem has to re-generate the charts every time, because the reporting tool will not allow you to simply plug new data into the old ones.
We eventually got a final, actual, complete and accurate specification, at 11:30. An hour and a half before our director was due to formally present it to the client. Bear in mind this is supposed to be a proper functional reporting tool that the client can use every month, not a static chart, which is what it is. We seem to have more or less pulled it off, but if we'd only been given these vital details - such as who to charge and when - three weeks ago we may have been able to actually produce something useful rather than just demo-fodder.
Over the next two weeks we work out how to use the godawful reporting tool (which the director loves because he never actually has to deal with it) and manage to wrestle together some sort of data on which to report. All through this time we are labouring under best guesses and half-truths, as we have yet to be presented with an absolute spec regarding exactly what it is we're supposed to be reporting on.
This week we finally got specs. Sort of.
On Monday we thought we had a spec.
On Tuesday we were assured that a different spec was the right one.
Wednesday (the day before the deadline we were given) we were given yet another spec. And told that the data was wrong somehow.
Yesterday we sorted one of the filtering problems with the data (with the help of one of the clients' staff who appears to actually have his head screwed on right), and were told to send it over again. Team Leader talked it through with the client contact, and assured me it would do. So naturally this morning I got a mail back from the client contact, which in her typical helpful and useful habit of sending full and complete information on the problem consisted of exactly one sentence:
"What is this, the figures are wosre than before."
Blindingly helpful.
This morning I've exported this data, using different constraints and table joins, about three times. Poor Saleem has to re-generate the charts every time, because the reporting tool will not allow you to simply plug new data into the old ones.
We eventually got a final, actual, complete and accurate specification, at 11:30. An hour and a half before our director was due to formally present it to the client. Bear in mind this is supposed to be a proper functional reporting tool that the client can use every month, not a static chart, which is what it is. We seem to have more or less pulled it off, but if we'd only been given these vital details - such as who to charge and when - three weeks ago we may have been able to actually produce something useful rather than just demo-fodder.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
Hugs
Date: 2004-08-20 06:23 am (UTC)Mostly because I have very little else to do.
I'm not helping, am I?
Re: Hugs
Date: 2004-08-20 06:32 am (UTC)Like, pretty men dressed as cats! Or whatever.
Re: Hugs
Date: 2004-08-20 06:37 am (UTC)Nice kitty costume by the way!
no subject
Date: 2004-08-20 08:22 am (UTC)This afternoon we were finally given a cost code and work-order number that we could charge against to actually buy the new hardware. We've spent 3 days trying to get this information. With luck, the hardware may actually be delivered by mid-week. Thats if the Finance director signs it off. He may be on holiday.
no subject
Date: 2004-08-20 09:46 am (UTC)no subject
Date: 2004-08-20 11:36 am (UTC)