Thats it pretty much exactly.
Last edited:
Business Analyst Career Advice
- Thread starter DezUk
- Start date
Thats it pretty much exactly.
It just more efficient if the BA has some technical skills. Even if its the creation of user requirements or creating issue tracking spreadsheets and the like.
One of my favorite examples is the sub draft complaint. One BA on a system to capture complaints, decided that if a user was writing a complaint, and ran out of time they could save it as a draft complaint. Then come back and finish it later. Then they decide that there was a need for hierarchy of complaints where the there were numerous sub levels of complaints and a master complaint. Then they decided all of these had to have draft complaint functionality. Then a list of complex rules about when a draft complaint, was submitted what happened to the related sub complaints still in draft.
In the end it was so complex no one could understand it. They dropped all of it, and had one complaint, and if you didn't finish it, tough we didn't store draft complaints at all.
Another guy didn't realize the user requirements, and the feedback from the user groups was completely at odds with the how the system actually worked, because they didn't understand it, and had created completely inefficient process because of this. The BA modeled all of this inefficiency and then was completely lost when it didn't match the existing system or the data relationships within.
These are the risks when a BA is too detached from the technicalities of the process they are trying to define.
You are right to say in that this is rolling up tasks better given to someone like a system analyst, or technical pre-sales people. But in reality these often don't exist and the BA has to be adaptable.
I think all this technical discussion might put you off. That wasn't the intention.
There is a general move in IT to specialize and the technology stack in each role gets deeper and more specialized every year. BA's especially in IT have to decide if they want to move closer to development or move close to a generic BA as in business. Many would say there is no need for a BA (IT) that any BA should be able to provide the BA skills without having any IT skillset. I wouldn't agree. But you do see a lot of BA going the Prince2/Scrum and similar routes.
Personally I prefer to be closer to the development. But it sounds like you really don't know what you want to do. Your indecision means you are frozen into inaction. That's perfectly understandable. Perhaps you need to do some courses to explore what you like doing. That's what people I know in the same position have done. If your skilset it lacking then you need to work on it. What skillset that should be, is interesting to discuss.
I'm in a similar crossroads myself, but at a different starting position.
Soldato
Which industry?
As far as the technical side goes I'm not advocating much beyond basic IT skills and general technical knowledge. But if you can't even write a simple SQL query then you're going to look pretty stupid in the real world. In reality you've got to have some degree of independence and that means being somewhat self sufficient too. For the vast majority of actual BA roles out there there isn't room for someone who only wants to create process diagrams, that is pure fantasy. Also the idea that Business analyst, systems analyst, business systems analyst are all completely separate careers is a bit flawed - this isn't a regulated profession we're talking about - sure some BAs are more technical than others but the basics ought to be there else you're potentially excluding yourself from a lot of jobs and still at risk of making a bad impression at a large portion of the jobs you can get.
Then we've got the popularity of agile methods - no room for BA's in scrum if implemented properly. You transition to product owner if you're experienced or become a 'developer' - while a former BA in the dev team might be more focused on specs they're still going to have to muck in with other tasks likewise the former QA guy can't just wait till the end of the sprint before doing any work - coding skills, UX design etc.. could well be needed even if others in the team focus on those more. For the BA who doesn't have basic technical skills and has just been blagging it in the past this could mean they need to start looking for a new job.
I think constraining yourself into a narrow set of skills is a very bad idea in general not only are there fewer job opportunities but you're going to find it harder to demonstrate value and be seen as productive. On big complicated software projects a range of skills are needed, things go wrong stuff gets delayed people leave, the scope and requirements can change. You're not always going to have 'solutions experts' and whatever other people you believe should be responsible for stuff that you think BAs shouldn't be doing. It is such a bad idea to ignore the need for basic skills that could be very helpful, the OP is looking for advice on improving his skills and frankly a good knowledge of SQL and excel are very useful things to have (and depending on the system - basic unix skills too). Putting forth some hypothetical idea of a BA as having some narrow set of responsibilities just isn't helpful or realistic as most BA jobs simply aren't going to work like that and the sort of people who want to try and work as a BA in that way, in most cases, are likely going to be time wasters.
Last edited:
In a large business and on complex Projects I would not expect a BA to be performing the sort of activities you're talking about. They would be focused on deriving the business requirements and processes and then working with the architects and technical specialists to ensure they are translated into the solution.
I agree about it being very valuable for a BA to have a broad skill set and technical understanding, but I don't agree they need to be able to write code etc.
Different worlds perhaps..
To the OP - Looking at your post again it sounds like you want to be in a more focused development role in which case I'd start trying to do less BA so you can improve your technical skills.
Well I think your expectations differ somewhat from reality in so far as in plenty of large business and especially on large complex projects basic things like the ability to write a simple SQL query by themselves will be expected of the BAs. It is a 'skill' that can be picked up in an afternoon so someone presenting the inability to be self sufficient in that way is throwing up an immediate red flag to their colleagues.
Maybe it is a different worlds thing - do you work in or in close collaboration with the government/public sector perhaps? My perspective comes from IT projects in collaboration with banks and companies like BP, IBM etc..
Maybe it is a different worlds thing - do you work in or in close collaboration with the government/public sector perhaps? My perspective comes from IT projects in collaboration with banks and companies like BP, IBM etc..
In a large business and on complex Projects I would not expect a BA to be performing the sort of activities you're talking about. They would be focused on deriving the business requirements and processes and then working with the architects and technical specialists to ensure they are translated into the solution.
I agree about it being very valuable for a BA to have a broad skill set and technical understanding, but I don't agree they need to be able to write code etc.
Different worlds perhaps..
I don't know why you keep saying able to "write code"....
For me being able to know you way around a database or more specifically data and querying it, (finding the information you need) is not coding. Similarly knowing your way around excel, access and other tools. You'll need those even to collate all the information you'll be using and analyzing the process.
What DezUk WAS indeed talking was veering into coding and development. That is a different conversation.
I do not agree at all with either of you, I think we've got completely different views of a BA role. I have no experience in the Finance sector so things may be different there, my experience is in complex engineering and manufacturing.
I would not expect a BA to be writing DB queries and analysis data and in my position would not employ one to do that. As I've said they are there mostly there to engage with the business and understand and capture requirements, which can then be translated into a solution, they would not be performing technical work.
We've got different views and experiences clearly so let's leave it at that. It's a broad role that differs across organisations
I would not expect a BA to be writing DB queries and analysis data and in my position would not employ one to do that. As I've said they are there mostly there to engage with the business and understand and capture requirements, which can then be translated into a solution, they would not be performing technical work.
We've got different views and experiences clearly so let's leave it at that. It's a broad role that differs across organisations
This thread has grown arms and legs, lots of opinions and some good feedback. I should try and clear things up a little from my original post. I am down on paper as a BA working with an Agile software development team. We create a mobile solution for the public sector and my daily job involves the following:
This is a general overview of my daily job as a BA. In other projects I have been heavily involved in using SoapUI to fire requests at an API to try and figure out how links could be made between entities stored within a database, so quite technical for a BA IMO. In the past I have worked in places where I write full blown functional specs with functional and non functional requirements working in a waterfall model. But the reason for my post is that when I am looking at other BA job specs I always see requirements for Excel and mySQL which I know I can probably learn in my own time.
I just want to keep all avenues open when it comes to career progression and have a solid coverage of all skills required for a BA. I know I mentions coding skills but this is more for my personal development as I ideally want to pursue the route of a UX designer but to do that I need a portfolio. For that I need to brush up on my coding skills to create some websites.
- Creating user stories which includes the overview, requirements, acceptance criteria and any supporting documents i.e. wireframes, excel mapping docs and so forth
- Holding 3 amigo sessions with developers and testers
- Managing the sprint planning and reporting on progress and burn down of the sprint as well as holding retrospective meeting at the end of each sprint
- Getting involved with testing, recently rearranging cucumber test scripts and reviewing manual and automates tests to make sure they cover all scenarios
This is a general overview of my daily job as a BA. In other projects I have been heavily involved in using SoapUI to fire requests at an API to try and figure out how links could be made between entities stored within a database, so quite technical for a BA IMO. In the past I have worked in places where I write full blown functional specs with functional and non functional requirements working in a waterfall model. But the reason for my post is that when I am looking at other BA job specs I always see requirements for Excel and mySQL which I know I can probably learn in my own time.
I just want to keep all avenues open when it comes to career progression and have a solid coverage of all skills required for a BA. I know I mentions coding skills but this is more for my personal development as I ideally want to pursue the route of a UX designer but to do that I need a portfolio. For that I need to brush up on my coding skills to create some websites.
Associate
I work as a Senior Business Analyst for a company that specialises in Phase 1 clinical trial EDC software for Biotech, CRO & Pharmaceutical companies. I started my career as a Tester before making the jump across to being a BA back in 2009.
I spend most of my time making sure that upcoming software modules are being developed correctly based on my functional specification. This covers the actual writing of code and the testing. I will also do some PM.
I've got good industry knowledge that I have picked up over the years but most of the skill involved in being a BA is making sure the solution you design is fit for purpose and everybody knows what the hell they are building/testing. I use UML diagrams to assist with this.
I'm average at best with SQL and hate coding but it's never held me back.
I spend most of my time making sure that upcoming software modules are being developed correctly based on my functional specification. This covers the actual writing of code and the testing. I will also do some PM.
I've got good industry knowledge that I have picked up over the years but most of the skill involved in being a BA is making sure the solution you design is fit for purpose and everybody knows what the hell they are building/testing. I use UML diagrams to assist with this.
I'm average at best with SQL and hate coding but it's never held me back.
That is almost entirely different question to what you originally posted.
I started out in design, and at one point (a very long time ago) had a half decent portfolio. I'm kinda interested in UI/UX design myself, and have dabbled in it. If I want to switch back to it now, I'd have to start all over. If I was doing it, I'd go do some formal training and work on having a very good portfolio. Its becomes competing with other people and your portfolio will have to stand out from every one else. I would have assumed that UX design wouldn't pay as much as BA. Unless you were a UX rock star. But I'm only guessing. I don't know much about the current market.
Most places I've worked, almost never put any effort in the UX design. Bit soul destroying tbh. Be nice to work somewhere that was interested in it.
Last edited:
Yup, I know there are also strategy BAs working in management consulting who might have a similar lack of technical skills. Though I'm not sure that I'd consider being able to run a simple SQL query in order to get the data you need to do your job 'performing technical work' as the other poster seemed to phrase it.
Most BA jobs however involve working on IT/software related projects and so will often need basic technical skills. While people can claim that in theory these skills aren't part of 'business analysis*' the reality is that without them you're probably excluding yourself from a large portion of available BA roles.
*though this is hardly a regulated profession we're talking about so opinions re: what falls within its domain will vary.
Last edited:
neither will take long to pick up both are useful and very commonly required for BA roles as you've seen. I'd strongly recommend the books by Walkenbach for Excel. For SQL you basically just want to be self sufficient in so far as you can get the data you need - doesn't have to involve being able to write particularly complicated queries.
Excel is a good general purpose skill to have but it is also the sort of thing that you can blag to some extent, get your foot in the door and then skillup on as there is so much information and training materials out there. My Excel skills are average at best (formatting things neatly always takes me far longer than it should) but it's not a massive part of my job. One of the best (and occasionally worst!) things about Excel is it is quite flexible and powerful for such a ubiquitous tool, most companies have it installed on every desktop.
As for mySQL which you've mentioned a couple of times I would just focus on SQL in general rather than a specific 'brand'. Don't just focus on query language though, as a BA data modelling concepts can be just as important.
Associate
After around 7 years of BA roles across the financial , technology and retail sectors I transitioned into PM around a year and a half ago, having reached a similar crossroads to yourself.
From my own personal experience, the transition to senior BA isn't so much about technical skills or business knowledge, its your ability to agree or set strategy/approach, knowing your methodologies for analysis and sticking to it, whilst guiding and coaching others on the same. If you've spent time working with senior stakeholders and are comfortable in doing so then that's a key step in the process.
You also referenced a number of agile terminologies in your last post, which suggests you're familiar with agile which a lot of places are keen on, which is a plus point.
My advice would be to worry less about what other people can do, they might be excellent coders but their softer skills which are absolutely vital for a BA might be shocking. If you feel like you want to be more comfortable when using excel or Sql then give yourself a better grounding in it, but unless you're looking for technical analyst style BA roles then I really wouldn't worry too much. As others have said, it differs between companies and even projects the skills that are required of a BA.
From my own personal experience, the transition to senior BA isn't so much about technical skills or business knowledge, its your ability to agree or set strategy/approach, knowing your methodologies for analysis and sticking to it, whilst guiding and coaching others on the same. If you've spent time working with senior stakeholders and are comfortable in doing so then that's a key step in the process.
You also referenced a number of agile terminologies in your last post, which suggests you're familiar with agile which a lot of places are keen on, which is a plus point.
My advice would be to worry less about what other people can do, they might be excellent coders but their softer skills which are absolutely vital for a BA might be shocking. If you feel like you want to be more comfortable when using excel or Sql then give yourself a better grounding in it, but unless you're looking for technical analyst style BA roles then I really wouldn't worry too much. As others have said, it differs between companies and even projects the skills that are required of a BA.
I always found most BA get the role because they get on with people. The better ones have better technical skills or project management or BA skills. I don't think I've ever met a BA with poor people skills.
Well other than that their other skills let them down, and that might cause conflict.
Well other than that their other skills let them down, and that might cause conflict.