Let’s be honest. Money is important. It’s often the top factor that motivates a career switch. Who doesn’t love a bumped-up salary? The charts below show how much business analysts are making on average compared to software testers (QA) (source: Glassdoor).
Since there’s a significant gap between testers and business analysts, some testers decide to make the jump. So you’re excited about switching from software testing to a business analyst (BA)? Cool! Let’s get started.
Why Read This?
I started my career out as a BA, not a tester. But I have my fair share of knowledge about testers and the nitty-gritty of their jobs since testers are the end-users of the products I manage. It’s my duty to view the world through the lens of testers. Thanks to this unique perspective, I could promise you some useful insights that smooths out the transition from tester to BA.
Why Business Analysis?
Before embarking on this risky albeit exciting journey, you should make up your mind first. It’s worthwhile to spend some time thinking through the questions below.
Do you actually want to leave the software testing profession?
Software testing is a prestigious profession and there’s a lot to it. As a tester, you have a long and fruitful road ahead. You could progress from manual testing to automation testing. You could get promoted to QA Lead, QA Consultant, QA Manager, and even Test Architect. So don’t leave the software testing profession just because you think it lacks upward mobility or excitement.
What are the headaches your future self must deal with day by day as a BA?
As a BA, you must be passionate about communicating with customers, understanding what they want versus what they need, skillfully extracting the hidden information that you don’t or forget tell you, writing many documents and religiously keeping those documents up to date, etc. All of those tasks make up a typical day of a BA. Be sure that you love the BA challenges before moving on.
Are you quitting with good reasons?
Are you quitting because you’re bored or because testing is too hard? If you quit because you cannot manage to get your testing works done on time and with high quality, I’m sorry to say BA is not the career for you. If you quit because you do your job so well you feel bored, good! You are ahead of the game. Some of the testing skills you already have are extremely valuable to your future BA role.
Business Analysis Skills
There are 3 primary skill sets that every BA must have:
- Analytical skills
- Communication skills
- Technical skills
I’ve drawn a diagram to illustrate the relationships between these skills and the day-to-day tasks of BA below.
Note that the diagram doesn’t exhaustively describe the myriad of tasks that a BA must do. There are plenty more but you got the gist of it.
Your Valuable Assets As a Tester
As I said, if you’re a top-notch tester, you have some serious advantages compared to other starting points such as developers, UX designers, customer support engineers, sales/marketing, fresh graduates from business disciplines, etc. So what are your advantages as a tester?
- Congrats! You already ace requirement #1. Analyzing something just means examining each and every part of it thoroughly. Sounds familiar? As a tester, you have certainly analyzed a lot of software implementations with great attention to details to find bugs. This second-nature of yours is a big advantage.
- You often read, analyze and review software requirement specifications. A tester sometimes works with those documents as much as a BA. So you won’t find yourself lost in those document forest any more than a typical BA.
- You have great critical thinking. Testers and BAs alike must not gobble up information mindlessly. They stop and think, poke holes in customer requirements, and eliminate ambiguity.
- A core duty of a BA is performing acceptance tests before presenting the new features to the clients. So basically, a BA is a tester.
Communication skills (requirement #2) are hard to measure. I’ll let you evaluate your own communication skills. If people understand exactly what you mean and you also understand them, that’s enough.
You might not be as technical (requirement #3) as a developer transitioning to BA. But if you start out as an test automation engineer, you’re already familiar with IDEs, certain programming languages, and certain software patterns. This knowledge makes you a far better candidate than those business or UX people trying to be BA.
If you switch from tester to BA within the same project, you get ahead even more. Since the software you’re testing now becomes the software you analyze, you already know the inner workings of the software as well as the domain that the software is operating in.
You know what’s best? Becoming a BA of a software testing product!
I’m Confident. Where Do I Start?
After you make up your mind and understand your advantages, it’s now time to get started.
#1. Start learning
The body of knowledge you need to learn heavily falls into the category of skills and techniques, not so much about tools and technology.
Go to your local training center or sign up to an online courses. I’d prefer online learning since it’s cost-effective and convenient. Fundamental skills you should learn include: how to prototype, how to identify stakeholders and define responsibility matrixes, how to define SMART requirements, how to elicit information from the customers/clients, how to write and prioritize requirements, and more. Remember to practice any new skills you learn.
You should know nothing fancy but Word, Excel, and PowerPoint or any other word processing, spreadsheet and presentation alternatives. On top of that, you should learn to present your ideas visually using prototyping tools like Balsamiq, MS Paint, Inkscape or even the good old pencil sketches.
It depends largely on the industry and the technology of your product. Most BA nowadays work with web technologies such as ReactJS, Angular, VueJS, etc. and mobile technologies such as ReactNative, Android, iOS, etc. That’s not to say you should exclude other techs such as COBOL, ERP, Java, .NET, etc. Understanding these techs helps you appreciate the technical constraints you operate within.
#2. Earn BA certificates (optional)
Some big companies require you to acquire a CBAP (Certified Business Analysis Professional) certificate issued by IIBA (International Institute of Business Analysis) or other certificates such as CABA (Certified Associate Business Analyst) or CSBA (Certified Software Business Analyst). However, I’ve observed the decline in popularity of these certificates. Some experts even advise you to take an MBA course but I definitely doubt the benefits of an MBA degree. It’s simply an overkill.
#3. Earn industry-specific certifications (optional)
You are not required to spend too much money on these certifications. Those papers are nice to have. Unless your target industry is highly regulated, you might skip this step. That said, if you have these certificates, your candidacy greatly improves. For instance, you boost your credibility by having a CPHIMS certificate if you intend to work on healthcare information systems.
#4. Prepare for the interview
Brushing up your CV, aligning the specifics your career to the future job, sending your CV to potential employers, mental rehearsals, showing up in the interview, tell your story and get the job. If you got rejected, no problems. Start shooting down other job openings. Remember to focus on the advantages you got (reread the section above).
A business analyst is a bridge between the business and the development. The job is critical to the success of the software development and deployment. Besides the nice pay, it offers exciting challenges as well as learning and leading opportunities. If you have passion for business analysis, try your best to pursue it. Remember that you already got ahead of the game starting out as a software tester. Good luck!
Do you find this article useful? Leave your comments below. If you like what you read, subscribe to my newsletter here.