One thing that certainly needs to be understood here is Business Analysis is not like any other professions. In fact, this is the only profession that has been welcoming all with open arms. But the way this profession work is very different. While being technical is a NEED for other profession here its just an ADD ON. So what this profession demands exactly. Well the demands of this professions are not that much than what you might have perceived about it.
I interviews many aspiring developers and found they loose to very little things. Because they never put the needed energy in understanding the profession.
For instance: If I ask a developer how would you communicate a complex requirement to a Business stakeholder who is not tech savvy. Their immediate answer would be like they would forward a BRD or a subset FSD or split user stories so that it is easily comprehensible. But the answer is not that complex. Its just a matter of helping the business visualize the functionality which can be easily explained via wire frames or if it is too complex then via flow charts. Isn’t it?
To understand more, Let us do a comparison on what you do as a developer currently and how to transition your existing skillsets into Business Analysis.
| SKILLSETS you already have as DEVELOPER | SKILLSETS you need for transitioning into BUSINESS ANALYST |
|---|---|
| 01. Collaboration | Well you already have been collaborating with people here you just need to use it for management of people referred as “Stakeholder Management” |
| 02. Analysis | Great! You already know about the architecture of the internal system. Now you have to come a level above where you are expected to do requirements engineering. |
| 03. Code | You already know about the implementation of the functionality now you are expected to clarify the functionality to the Development Team and be their mentor. |
| 04. Communication | Well! This is something you have been doing the day you entered into the IT Industry but here you are expected to make it more formal aligned with Business needs. |
| 05. Management | You are already very good at managing your code. Here you have to manage the requirements. While the same versioning and tracing concepts apply here as well. |
| 06. Analytical Thinking | You have already thought a lot about it during implementation now you have to think of it as a feature that delivers value to business. |
| 07. Planning | You have planned deployment cycles a lot. Here you are expected to plan the RELEASES/EPICS/FEATURES/STORIES that deliver the business value. |
| 08. Domain Competency | You already know the domain during development now its time to shift your focus. |
| 09. Technology Competency | You are master in this. Knowledge is never wasted and this will help here in coming up with concrete impact analysis reports. |
| 10. Product Competency | You already know the product during development now its time to shift your focus to understand your product functionally. |
Most of the times despite having full potential to grow developers are often in jeopardy around transitioning their careers. I would say its not that hard transition as you have to just shift your focus from DEVELOPMENT mindset to ANALYSIS mindset.
Usually career transition takes sometime but if you shift your focus its not hard to achieve. Business Analysis is not a profession where you can get a ON JOB SUPPORT this if a profession where you either LIKE IT OR LEAVE IT. There is no space for survivors.
A learning initiative by SUNILKUMARMAJHI.COM
Checkout my FREE BUSINESS ANALYSIS COURSES on YouTube Channel. Follow the Playlist.