Hi experts, I am grateful to everybody who is giving support to me.
I would like to know one what is the best way to collect the requirements from client .
please dont tell this come by experience .
Every body is learner at first .
so experts u had implemented lot of projects . please tell the best way to collect requirements.
that means what they need , what they are lacking .
i look forward for your positive response .
Thanks and regards
There really isn't a "best" way, but generally speaking it comes down to answering the questions:
1. What do they want to do? Who does it? How often? What happens before? What happens after?
2. Why do they want to do it?
3. Is there anything that already does it? What are the differences and assumptions if we use an already existing tool? Do those violate any unstated requirements?
Figuring out number 3, unfortunately, requires experience. You need to be exposed to the different choices you have available - but you can always ask on here about that.
Doing number 1 and 2 correctly is just about listening really closely, and spending a lot of time communicating back to your client what you have heard.
hello experts,
sare your valuable experience..........................
lally:please dont tell this come by experience
Unfortunately that is the most important aspect. You start out with an education in business, whether that is college or an internet based course or whatever, which gives you the basic understanding of business processes. Then you apply for a job as a junior assistant consultant with a NAV partner, and from there you are assigned to projects. You work in those projects with more senior people, who show you how to do it.
The best way to learn what is the best way to do something is experience. The reason is that this business is so personal, everybody has different opinions about very similar things. There realy is not a 'best way', just a collection of experiences from people that have seen processes go really well, and trying to apply the same processes in other situations. You will find out (again, by experience) that what works REALLY well at one company, works like crap at another one.
Thank you experts,
I absolutely agree with that Experience will give that.
Here i would like to mention one thing . I joined in a company. That firm doesnot have senior consultants.
Most of companies not ready to pay high salaries. So they are taking freshers and reading manuals then start implementation.
this is process what happens generally.
So i am requesting u experts u had implemented projects, that you involved in lot of objects like requirements, custyomization, upgradtions....
I please throw your valuable informatons about requirements, how to collects.
what are steps tocollect requirements from client.
I hope u can understand this .
No as a matter of fact I don't understand this, and it is most certainly NOT what happens generally. Most companies have a mix of senior and junior people. Only hiring rookies without any support or training is a sure way to drive your company into the ground. For sure there need to be some veterans who have been there, done that, and know what to do in those situations. Your company needs to hire some senior people NOW, BEFORE the problems start piling up.
Gathering requirements is a relatively simple process.
Go to the client/prospective client.
Talk to them, and the main business process owners.
Let them talk, and draw from them using pointed questions from your understanding.
Make notes
Above all listen and understand
Compare notes, requirements and current issues to the standard functionality in NAV for a gap fit.
It will start to get easier the more you do it, basically with experience, which you do not want to hear - but that is life.