Monday, November 14, 2011

Let's first make it work.....

Instead of knowing the REQUIREMENT.....

We love to show our capabilities and on our intention of delivering a better product to Client, add a lot more considerations to that Requirement.

I ended up creating an entire socket-programmed Custom HTTP Service and scrapping it off. :(

It's good. But what is not..... Is the act of delivering our considerations along-with the Requirement.

What Client wants is a robust implementation of just & just the requirement stated.
Finish that. Finish whatever more is required.

You'll always have time to come back if there is time and work on your considerations.

Several times it might happen that your considerations get served with the future requirements or get changed with the coming restrictions.
In both cases, you'll end up doing more work on it.

Though you might think Client doesn't understand but requires it.

Work on what they require first, and any problem that might come up because you didn't tackled your considerations can always be presented to them if there are collisions.

Implementing your considerations might become an overkill for actual requirement if not controlled.

No comments:

Post a Comment