No one ever says "I want to be a BUSINESS ANALYST when I grow up”
The question “what do you do for a living?” is usually not a simple one for me. I can’t simply say sales or nursing. The title business analyst doesn’t help clarify things for people who are not aware of such an occupation. The name itself makes one think it is related more to data mining, accounting, or finance, rather than software development. It is at this point in the conversation where I am usually asked to explain my job. A conversation inevitably ensues, even in situations where I’d rather just leave (but, then I’d appear rude.)
At the highest level, a business analyst is responsible for writing how a piece of software is to look and behave. These requirements are a translation of terms gathered from a business group and handed to a software development team. It is analogous to an architect meeting with a client and designing a house, then handing the drawings to the contractor. The drawings must be understood and agreed upon by all parties before ground is broken. The same is true for the business requirements – the business and the software teams must agree to the terms presented.
The complexity of business analysis derives from the inherent tension between the groups and individuals involved. When teams want opposing functionalities or even the same functionalities just presented differently, it is the job of the business analyst to meet these demands and to find compromises all parties can agree to. These challenging relationships help to build successful software products in the end.
Could the world survive without business analysts? Sadly, yes, but it would cost businesses more time and money to develop software products without well-written business requirements. To continue the example of the architect, imagine the contractor simply builds the house without having any design drawings. In the end, the house may end up with a poor support structure, the water line may not be run to the bathroom, and the bedroom may not have a roof. It will cost the homeowner much more time and money in the end to make the repairs than to have simply planned appropriately from the beginning.
Maybe business analysts need to change the title to Super-Fantastic-Requirements-Gatherers and Writers or we can just stick with BA and explain our jobs in fewer than 450 words! What do you think would be a good superhero name for a business analyst?
