logo


Forum: General

Forums->General->definition of business analyst


Anonymous
definition of business analyst


Hi! I'm excited this organisation exists. You say one of your purposes is to "- Define the profession of Business Analysis" - so where is this definition? I can't find it written anywhere?

I am a software developer and I have a friend who I think would be a great Business Analyst. She asked me what a BA is, and I can tell her what the people who fall into the BA category do at my company, but I wanted to point her to some other resources, since my view is very limited.

Any resources you can point would be helpful. I don't know how people would break into this profession. I assume BA's are people who did Software Engineering and decided to focus on Requirements Engineering rather than Software Development/Testing.

Thanks,
Diana.

 
on: Sat 08 of Mar, 2008 [08:36 UTC] reads: 6575

Posted messages


author message
Re: definition of business analyst
on: Sun 09 of Mar, 2008 [04:05 UTC] score: 0.00 Vote: 1 2 3 4 5
Hi Diana,

In answer to your question, there is a brilliant discussion paper contributed by Neil Timmins in the ABAA knowledge base area that covers off on this area. I've attached the link below.


Introduction to the Business Analysis Knowledge Framework
http://www.abaa.org.au/cms/tiki-download_file.php?fileId=30



Also thank you for the much valued feedback, while much time has been spent getting the website up and running in its new format, there is still much work to be done... to address your issue I will also endevour to make this information more prominent on the website and have added it to list of things to do during next revision of the website.

Regards,
Andrew






author message
Re: Re: definition of business analyst
on: Tue 22 of Apr, 2008 [13:24 UTC] score: 0.00 Vote: 1 2 3 4 5
A business analysts. Well, a business analyst needs to understand business. Or, at least they need to understand the business they are analyzing. How else can you understand the business problem that you are trying to solve, if you do not understand the business? Furthermore how is the business going to trust you and have confidence in your recommendation (requirement specification) when you do not understand their business?.

A case in point. Some 20 years ago I consulted for one of the big five accounting firms. I was sent on assignment to assess the business needs of a large plumbing retailer. And, as a young consultant my focus was on the how computing resources could enhance the client’s business prospects. I recall I've been on Site for about two weeks, could have been three, when on a particular day I noticed that the 60 year old managing director and a bunch of ladies, all in the 60s and older, were in the boardroom sorting paper while listening to Benny Goodman songs from the word war II era. I asked the business manager what they were doing. He replied, they were stapling copies off receipts onto customer invoices. Being a young gun and I must admit being rather naïve, I suggested that the computer only needs to print all the line items on the invoice and that would be sufficient proof of purchase. The business manager smiled, pulled me aside and said "You do not understand our business!” (ooh harsh words to an analyst, but its best to hear it then then later.) He said let's analyse our customer’s buying process. When a plumber needs a piece of copper pipe they come to our shop and purchase a piece of pipe. Sometimes they would send an apprentice to pick up the pipe and take it to the work site. And, the apprentice would pick up the pipe and the receipt. On most occasions the receipt would get lost. However, the plumber would get the pipe and complete the job. The Business manager continued to tell me that what happens in the boardroom was significant to their business. He said, since the receipt is most likely lost the plumber does not have any proof of purchase therefore we keep a copy, with the apprentice’ or his signature . The sorting and collating that we do is our competitive edge. Now this was well before inexpensive accounting packages like Quicken and others. So he proceeded to tell me that at financial year end the plumbing retailer would take all the paper copies with the supporting information and put it into a shoebox and gave it to the plumber. All the plumber now had to do was take his shoebox and gave it to his accountant. The contents of the shoe box were then used to create the plumber’s financial statements and tax returns. The business manager then said, "this is why a lot of plumbers buy from us, rather than from the competition across the road ". I, as a rather naïve consultant, completely missed the value ad and competitive advantage of what happened in the boardroom. Occasionally I’d drive past the head office of the plumbing retailer and wonder about those old ladies, the managing director and Bennie Goodman. I learned a valuable lesson that day.

Apologies for this rather long vignette; but it illustrates the very important point of being a business analyst. You need to understand the business before you complete your requirements.

warm regards,
Keith



author message
Re: definition of business analyst
on: Tue 22 of Apr, 2008 [12:33 UTC] score: 0.00 Vote: 1 2 3 4 5
> Hi! I'm excited this organisation exists. You say one of your purposes is to "- Define the profession of Business Analysis" - so where is this definition? I can't find it written anywhere?
>
> I am a software developer and I have a friend who I think would be a great Business Analyst. She asked me what a BA is, and I can tell her what the people who fall into the BA category do at my company, but I wanted to point her to some other resources, since my view is very limited.
>
> Any resources you can point would be helpful. I don't know how people would break into this profession. I assume BA's are people who did Software Engineering and decided to focus on Requirements Engineering rather than Software Development/Testing.
>
> Thanks,
> Diana.



author message
stevanz
Re: definition of business analyst
on: Thu 10 of Jun, 2010 [12:24 UTC] score: 0.00 Vote: 1 2 3 4 5
Don't mind the length keith, i love reading what you've shared from the beginning upto end. A very good example indeed. The role of a business analyst acts as a face of Customer to the Development team, most of the time. Be credible enough and the team should have absolute faith in him.




Show posts: