Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  General  What I have noticed in my career as a BA
Previous Previous
Next Next
New Post 2/28/2015 10:06 PM
User is offline vlookup
39 posts
9th Level Poster

What I have noticed in my career as a BA 

That most of the time, these formalized processes can be sort of helpful, but for the most part it's strictly about delivery.  

I've created use cases before and most of the time they fall on blind eyes. 

It seems like to me the most documentation I have created that was used was change request forms for changes in the environment.  BRD and FRD forms and I use the term loosely to describe there forms.  A technical document usually drafted up by the development team and a test document to follow and track changes, errors etc.  

That's about it, sometimes we use a GANTT chart if there are a lot of moving parts and resources etc.  

Is this normal?  I see the CBAP - BABOK framework and it just seems like a ton of needless paperwork.

New Post 3/1/2015 3:31 PM
User is offline gh05
19 posts
9th Level Poster

Re: What I have noticed in my career as a BA 
I agree... I think that a lot of the time, the business analyst profession is needlessly overcomplicated. It's all about communication're asking questions...maybe performing some analysis on the result of the responses and then communicating the result to developers. The BABOK is with respect one of the most long winded and boring things i've ever cast my eyes upon.
New Post 3/2/2015 5:33 AM
User is offline unreqs
1 posts
No Ranking

Re: What I have noticed in my career as a BA 

Needless paperwork is an epidemic in our field ... at least I think it is. The techniques and artifacts that CBAP - BABOK teaches are not flawed. Depending on the situation many of those tools are relevant and helpful. 

The problem is that so many projects start with a Statement of Work that specifies what types of requirements documentation needs to be captured. Piled on top of that you have SDLC processes in larger organizations that demand additional, unnecessary documentation.

It is a case-by-case basis, but most of the time we are either (1) asked to create too much or (2) we fall into the trap of thinking we need to crank out more documentation.

The first one is often an impossible situation that you cannot overcome without changing the culture of your or your client's organization. The second one is something we have control over, but often don't do anything about.

New Post 3/3/2015 2:03 AM
User is offline Kimbo
453 posts
5th Level Poster

Re: What I have noticed in my career as a BA 

Hence the move to Agile


Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  General  What I have noticed in my career as a BA

Community Blog - Latest Posts

Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...
So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...


Upcoming Live Webinars


Copyright 2006-2021 by Modern Analyst Media LLC