If you have read the book “The Monk who sold his Ferrari” by Robin Sharma, then you know what a monk means, but the monk of my story is different, this monk has joined a software development company as a consultant, continue reading to see what happened.
There was complete silence as the monk(who became a consultant) entered the room, because you don’t see a monk everyday in a meeting room. People waited for him to speak, he whose wisdom was without boundaries. Then he stood up, a sudden silence spread across the room.
The monk look around him, all eyes were upon on him. Everyone was waiting to hear his pearls of wisdom. Suspense filled the room.
And then he spoke…
“Give a man a fish and you feed him for a day.
Teach a man, to fish and you feed him for a lifetime.”
His words thundered across the room, people responded by nodding their heads.
Just as the monk sat down, the business analyst from the back of the room asked, what kind of fish? Mackerel, Sea Bass, Shark?
The process analyst joined by adding, “How can we teach fishing without proper process in place, we should spend some time to define fishing methodology”
The IT admin raised his concerns by asking “we don’t have fish servers, what types of specs are we looking for. It’s going to to take time ordering the sea servers and installing the underwater software.”
“We will need a new standard to make sure everyone is following proper fishing standards”, added the QA.
The project manager, “We should create a new training department for fishing.”
As the questions continued, the end-user sitting next to the monk whispered, “Not exactly the reaction you were hoping for”.
“Not really, no”, the monk replied quietly.
“Don’t worry about it, I’m allergic to fish anyway.” said the end-user with a smile.
Moral: An example of how user requirements and the very purpose of any IT project can get lost so easily.
Simply Simple 