How many times have you heard “I have an easy request for you…” from either users or the non-technical manager with no concept of what it takes to create an integrated software application? Most of us that have been up and down the development block have experienced this I’m sure, and also for many of us the request has actually been easy! What a relief when it is!
But then … there are those other times which fall into a couple of different categories. The first category is the category where as the developer, after looking at the request more closely you determine (much to the dismay of the requestor) that to accomplish the task will really require some major changes – lots of work – and of course that also means time and money! After close consideration the idea for the change is either re-designed and re-considered, or scrapped.
Then there is the second category — I call it the “…seemed like a good idea at the time…” category. This is the project which is stated very simply, and upon further investigation as the developer you decide that it will in fact be a great enhancement to the program, and will not take much to implement. WRONG! This is the killer project! Not until getting into the finite details of the application do you realize that it is a monster! After spending double the time you expected on the project with no definitive end in sight reality has hit hard!
Very simply, the requirements were over-simplified, the review before the project was over-simplified, and the execution anything but over simplified. Oh well, chalk it up to just another day in the world of software development. Cheer up, there’s another project coming along right after you finish this one – if you ever do that is!