The Community Blog for Business Analysts

Lee Grinberg, CBAP, PMP
Lee Grinberg, CBAP, PMP

Are you the first and only one?

Are you the first and only Business Analyst in your company?  If so, you know how hard it is to survive while doing your job and bringing about organizational change.  If not, you may be frantically thinking "How do I get out?!". 

This post is to share my experience in how to not only survive but thrive!

I joined a mid-size company where there was no Business Analysts or Project Managers.   On top of this, the IT team was new with little knowledge of the system.   There was an SDLC (sort of) that was being followed but the requirements gathering went something like this:

  1. Business user wants something but he's not so sure what

  2. He pops by the IT department and blurts it out to an unsuspecting developer

  3. Developer codes something the developer is sure the business user wants

  4. QA talks to the business user and developer to figure out what they really want to test (no test plan or testcases)

  5. Go live date and the next few days - chaos as bugs appear and no one quite knows how this happened (again and again)

So by now you're thinking I was marching off to the SVP of the company with a copy of BABOK in hand in a self righteous indignation, right?   WRONG.

Open confrontation would only create resentment on the part of the entrenched business and developer community.   Instead I laid low for a while, observing taking notes and thinking where I would make corrections.

I made changes slowly following the steps below in order:

  1. Developed relationships with influential stakeholders.  Relationships go a long, long, way towards acceptance.
  2. Started writing down requirements and showing them to the business stakeholders.  Reactions were "Wow, you really got it" or "This is not what I meant at all, here's what I really meant....".  That's the idea, get them to acknowledge what they really want.
  3. Learned the database structure so that my requirements could refer to tables and even specific fields.  I know, I know this is not what a BA should do but...  with a new IT team it was best.
  4. Produced a detailed spec which was the sole document used for development and QA.  All stakeholders were now on one page.

The above was done on a small project.  This way I didn't "rock the boat".   Since the results were much better than the status quo, my perceived value to the business and IT went up a notch.  Since I could now speak a little businessese and ITese I also got some respect.

There was much more to do of course and the four steps above are just general highlights.    More details on how to implement them in further posts.....

This entry was published on May 25, 2013 / Lee Grinberg, CBAP, PMP. Posted in Soft Skills, Leadership & Management, Career as a Business Systems Analyst. Bookmark the Permalink or E-mail it to a friend.
Like this article:
  7 members liked this article

Related Articles

COMMENTS

moverby posted on Monday, June 17, 2013 8:34 AM
This describes exactly how I got started as a BA! I started down this path not even knowing the role I was playing. I was not even a BA at the time but after taking this same path, my value as one really stood out.
Only registered users may post comments.


Blog Information

» What is the Community Blog and what are the Benefits of Contributing?

» Review our Blog Posting Guidelines.

» I am looking for the original Modern Analyst blog posts.



Modern Analyst Blog Latests

Jarett Hailes
Jarett Hailes
As we start a new year many of us will take the time to reflect on our accomplishments from 2012 and plan our goals for 2013. We can set small or large goals. goals that will be accomplished quickly or could take several years. For 2013, I think Business Analysts should look to go beyond our traditional boundaries and set audacious goals. Merriam-...
2 Responses
Howard Podeswa
Howard Podeswa
Recently, I was asked by the IIBA to present a talk at one of their chapter meetings. I am reprinting here my response to that invitation in the hope that it will begin a conversation with fellow EEPs and BAs about an area of great concern to the profession. Hi xx …. Regarding the IIBA talk, there is another issue that I am considering. It's p...
12 Responses
Adrian M.
Adrian M.
Continuing the ABC series for Business Analysts, Howard Podeswa created the next installment titled "BA ABCs: “C” is for Class Diagram" as an article rather than a blog post. You can find the article here: BA ABCs: “C” is for Class Diagram Here are the previous two posts: BA ABCs: “A” is for Activity Diagram BA ABCs: “B” is for BPMN
1 Responses
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC