IT Dev to Tech Business Analyst

[jonathanOnshore2010]

Hello,
As a senior dev who has for many years worked 40% hands off using UML, writing use cases, being involved in Agile process and running standups, retrospectives, performing user testing, prioritisation etc, I'm wondering how best to make the transition to a hands-off technical BA? (within IB since that's where I've always worked)

Are there certifications worth doing, or should I re-examine my previous work history and write a new CV highlighting the BA aspects of my knowledge and experience. (Im from an engineering background than computer science so have always had an interest in process). Then wait for a favourable interview?

I'm not sure what the gaps are between what I've been doing previously, and what the full scope of a typical BA would involve. Any ideas how best to find out? (ie. gap analysis)

[northernladuk]

Mind me asking why you are wanting to swap to something that you don't actually fully understand by your own admission??

[jonathanOnshore2010]

Mind me asking why you are wanting to swap to something that you don't actually fully understand by your own admission??

I agree I don't fully understand. However I've previously worked alongside BA's and there was a cross over of our role as I helped them out. I've also used extensively Rational Rose and UML for large parts of my career, along with implementing Agile practices (not just technically by setting up a build server). Sometimes I've sat with end users and gathered their requirements, and presented solutions to directors.

So, I wondered what are the BA's doing that I don't, so I can then think about acquiring those skills and making a full switch. I'd like a tech focused job where my skills appreciate with time (ie. process/people focused) instead of the interviews being focused on language features of .Net 4.0 et al.

(I realise this may sound mad to those die-hard programmers)

[SueEllen]

So, I wondered what are the BA's doing that I don't, so I can then think about acquiring those skills and making a full switch. I'd like a tech focused job where my skills appreciate with time (ie. process/people focused) instead of the interviews being focused on language features of .Net 4.0 et al.

You know when you work with people in specific areas?

It's always a good idea to ask their background and then ask subtle questions about their job for areas which you don't understand.

[cojak]

They're not Tech Business Analysts, they're Systems Analysts! FFS.

The BA and SA are not the same people, they have different skills and emphasis.

This is a personal gripe of mine.

[MarillionFan]

They're not Tech Business Analysts, they're Systems Analysts! FFS.

The BA and SA are not the same people, they have different skills and emphasis.

This is a personal gripe of mine.

I tend to do both parts bit I haven't got a clue about what a Business Analyst or Systems Analyst does.

[malvolio]

I tend to do both parts bit I haven't got a clue about what a Business Analyst or Systems Analyst does.

The clue is in the job title. They sit between business and techie geeky people and translate the former's requests into something the latter aren't going to be insulted by, and the latter's response into something real people can understand.

It is interesting to note the OP uses his awareness of process methodologies as the way to justify the move, which is part of the problem he faces. Analysis is not about process, it's about understanding, questioning and soft people skills. Processes only make sure you don't miss anything (and waste 30% of your time drawing pictures to impress the management).

And the thing to remember is that IT is not a means to itself, it's only of value if it solves business problems and delivers service-level solutions. I know how an enterprise SAN works in some detail, but you will never find it referred to as anything other than "resilient storage" in my outputs.

And don't get me started on Agile. Fine for localised development, trouble shooting or in fast-moving environments such as a trading floor. Everything else needs a formal baselined plan first.

[jonathanOnshore2010]

It is interesting to note the OP uses his awareness of process methodologies as the way to justify the move, which is part of the problem he faces. Analysis is not about process, it's about understanding, questioning and soft people skills. Processes only make sure you don't miss anything (and waste 30% of your time drawing pictures to impress the management).

I'm sorry if I mixed up terminology. Yes, I am facing some problems making the switch. I've also done 3 years of therapy training with a consulting/coaching focus. So I do have soft skills. I'm not a through and through tech trying to make a wild switch. But I am having trouble wording my skills appropriately to ensure they are 1). received well, and 2). represent my new title of "systems analyst".

Any ideas how best to workout any gaps in my previous experience as a hands-off something or other, and my new analyst direction? That way I can undertake specific training and make sure I'm presenting myself accurately and ethically.

[jonathanOnshore2010]

It's always a good idea to ask their background and then ask subtle questions about their job for areas which you don't understand.

I agree, but being on the bench for 5 months due to IB cuts isn't helping.

[northernladuk]

You are going to really struggle to change roles completely AND cover up a 5 month bench. Remember as a contractor you are valuable because of your pervious experience and knowledge. You cannot just pick and chose with role you want and hope a few certs are going to cut it. You are going to be behind a line of people with 10-15 years in the role and actually know what the role is!!!!

This is the type of move you make when you are in contract and have access to these types of people to learn. Trying a career change whilst on the bench and expect to be in the running for a role is a very very long shot IMO.

I am sure someone will follow my post up and claim they have done it but I would say you need to sit down and think about why you are on the bench and what exactly you need to do to realistically get off it quickly.

By all means go for it but don't make this your one and only path off the bench!!!