In scope or not?

- Image by Getty Images via Daylife
This week, I had a meeting with the finance depattment of client to review their requirements for a project to change their Business Repoting process. Turns out that most of the points we asked were responded with “please put it as an option in the proposal”. What this indicates is that clients don’t know what they want at all and go fishing.
Some would argue that having options would provide a choice to opt in or opt out of the functions of the application based on the cost of the option, similar to having a choice of transmission when buying a car. For example, data cleansing and data reconciliation, can that be left out of the process?
I would also challenge the abilities of over 60% of CFOs also don’t “know” what their business needs and having that as the organizations road map. Most of the time spent in meetings solving day to day financial problem. Believe me, I’ve seen CFOs chasing numbers themselves during month ends. This is even worse when you deal with staff in large organization who has no idea what other departments are doing and the relationship between departments.
Not only do I find this with CFOs, but surprisingly I find it in almost every graduate student I supervise. Research scope enables one to focus only on variables directly related to the study while filters unnecessary variables.
In my opinion, the ability to “know” what you want and being able to view the “road map” is the skill that lacks here. To have one, experience with business understandings is needed, with the ability to analyze and prioritize the project life cycle and it’s integration to the business.
I am sorry to say, but some people will never be able to achieve that level, as it requires both seeking and gifted talents. In one’s life time, we seldom come across these type of material. Be sure to know when you meet one!
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=f77abd5c-aca2-49e4-bf7f-ef7a3c8fb46a)