I can only speak from the perspective of a dev in the UK, you might find things are different in India, so YMMV. Business Analysts (BAs) tend to be either failed devs or [worse] people with MBAs (Master's degree in Business Administration) who think they know about systems design because they have done a short course on it. The main purpose of an BA is to drive out requirements from a business and translate these into something akin to a systems requirements so the dev team can get cracking. Theoretically this is a skilled job, but it is rarely done well in my experience as the companies don't want the expenditure of getting someone in who really does the job well. To make matters worse, they tend to put such people at in charge of at least parts of the project, which is a bit like making a Confectioner a site foreman on a large construction project because knowing how to make icing is similar to making motar in principle. Often this is predicated on the idea that devs are not normal, and shouldn't speak to real human beings. Sorry to be so downer on this, but it has been my experience in the past.
SPG from Bangalore wrote:
Suppose,if I go ahead,will it problem in future for me to come back to core development,or is it good to go further positions in same field.
Again, YMMV, but in my view yes, even with a gap of a couple of years you'll miss the latest developments in IT. At some point most devs face the dilemma you are having: 1) Go into management: dull, but you have more apparent control and better pay or 2) Remain a dev: Work is interesting, even fun but once you get to a senior level you hit a ceiling and progression is hard (though there is contracting, or setting up your own company as an option).
Sort of a cross between Lawrence of Arabia and Dilbert.[^]
