I get a lot of Resumes from Business Analysts and students who want to become Business Analysts. I want to capture the information that should be clearly highlighted in every Business Analyst’s Resume. Please note that most Resumes are read by computers and unless you have the right jargon and details your Resume will not be picked.
So, what do Business Analysts do? Almost everything I will say.
Business Analysis is often a common name used for most support roles, however a Business Analyst often has three major responsibilities:
- Requirements Gathering
Now let’s look at what these roles and responsibilities are:
During the initial stages of every project the requirements of the project is gathered from business and technical teams in order to finalize the scope, size, timeline and budget of the project.
This is done through various techniques such as:
- Document Review
- JAD Sessions
- Brainstorming sessions
Business Analyst may use one or multiple of these techniques to gather requirements. Often times they are asked to analyze process maps, processes, applications and data to understand the requirements.
A good Business Analyst should be able to analyze and map processes with minimum input. Based on their area of expertise Business Analysts often act as SMEs in large projects analyzing current state, possible solutions/recommendations, future state visualization and testing of possible solutions.
Business Analyst resumes should list the types of analysis experience they have, including the domain and industry expertise. This information should include details such as the size of the project, application, Business and Technical involvement and specific role of the Business Analyst.
One of the core responsibilities of the Business Analyst is providing documentation. Here is the list of most common documents:
- Requirement Management Plan
- User stories
- Use cases
- Business Requirement Document
- Requirement traceability matrix (RTM)
- Functional requirement specification (FRS)/ Functional Specification Document (FSD)
- System requirement specification (SRS)/ System Requirement Document (SRD)
- Test cases
- Process flow documents
- Project specific documents
It is also important to list the methodologies you are familiar with and project tools that you used such as MS Project and JIRA.
Here is a detailed article that I found useful: