The other day I stumbled upon a blog entry by a programmer on how to become a business analyst. Kingsley Tagbo’s article makes a number of good points but what caught my eye was his observation that many programmers/developers do not even realize that they have the option of becoming business analysts.
Becoming a business analyst (or a systems analyst) is a good career option for those who feel they are not cut out to be a programmer but who want to stay close to technology.
However – the role of a business analyst itself is not for everybody – if you do not have good communication skills (many programmers do not) or if you don’t care to constantly interact with people on a daily basis – you might want to think twice before making the jump to business systems analysis.
Here’s the full article:
How to Become a Business Analyst
Speaking of programmers views on business analysis, here is an article/essay from a programmer I know on the role of the BA over the last 60-70 years and how it has evolved.
http://businessanalyst.wikia.com/wiki/A_potted_history
"As far back as Aristotle, the division and departmentalising of labour has been something society and business has been putting down on paper proposed theories and solutions for. These theories and solutions are important to the BA, as the BA is often responsible for mapping processes and reengineering or modifying them."
brought to you by enabling practitioners & organizations to achieve their goals using: