Try to be crystal clear from the start what you have to achieve.
Try to finalize the scope with client. The Sloppiest part; to be rigid with the scope aspect, tries to make the stuff in black in white. (Still client say is the veto, but at least you can restrict him to some boundaries).
Person Responsible for scope:-
Dedicatedly assign a person for scope management, mere it a project manager or a business consultant or any person in charge. But his say should be considered as full and final and he should be the only accountable person for scope as well. He should have been given the powers to say Yes or No to the client, irrespective of any pressure from higher ups.
Centralized Scope management document:-
There should be a centralized location where all documents should be kept. Scope document should be under a version control system (e.g. SVN) to log the changes, rather than creating copies of document.
It’s nearly impossible for client to visualize all, what you have documented. His thinking will start once you deliver the project. So it’s better to create wireframe for the application you are going to create.
Create a realistic deadline:-
Once you know your entire requirements, try to break up all in small tasks. The more specific you are; more on target you will be. Don’t be ashamed to consult the person, doing the job, for estimation.
“Nobody can go back and start a new beginning, but anyone can start today and make a new ending.”
“If you start soon enough, you won’t have to run to catch up.”
Once you start up you will find certain thing, for sure, that you might have or haven’t planned for.
Once you proceed with the project, you clients mind will start working and he will come up with new changes and requirement, try to analyze the impact of each and every possible change. For each and every change your immediate response should be “NO”. Then use negotiation to turn this “NO” to “YES”. Any big change should never be allowed in middle of the project, it will surely spoil you whole project and waste your time, effort and money.
Changes should be incorporate in any future release.
May 15, 2012