Many run into the problem of differentiating between a systems analyst and a business analyst. The differences in some organizations do not exist. In other companies, the comparison is almost an insult. Depending on the business or corporation, there are many differences. The job title is not the only thing with which to compare these two separate roles. The problem occurs when the title is not so conclusive. The business systems analyst or the systems business analyst can actually be one or the other or both. Job description is the only way to tell when this happens. There are differences, though.
Author: Tony de Bree
It has been just over a year since I published my book, and that makes it easier for me to measure what has happened since then.
I have spent this year visiting many companies and discussing their business analysis function. In some cases, I have performed an assessment on the business analysts as well as the business analysis function within many large Corporates.
It has now got to the point where I could document the findings before I start the investigation. The reason for this is that the problems are the same. From articles and discussions from other countries it appears the problems are similar the world over. These are the problems I encounter most often:
Agile analysis is being spoken of more and more frequently in the world of business analysts. This form of analysis is becoming more and more popular as the next generation of business owners comes into play. It is a more hands on approach to the business analysis. There is more communication. Face to face discussions occur more frequently. E-mails and faxes are becoming few and far between. So what is agile analysis?
There are several key points one needs to understand before deciding whether or not to become a business analyst. You may be qualified to do the job you were hired to do. Yet is it the job you wanted to do? Some analysts find themselves locked in a cubical writing reports all day, only to find the report was not used or even read. They realize they are in a dead end job going no-where fast. This is not the usual dream one has when becoming a business analyst.
A use case study is designed to describe a situation in which the program is being utilized by the end user. It will tell a story of sorts describing how the program works and the input of the user. It does not tell how the program was developed. The details of the programming are not included in the use case study. You are trying to express the concept behind the creation.
The role of a business analyst can be very difficult. He or she must wade through the mass of information presented to determine the underlying problems. This information may or may not be correct. The business analyst much research to comprehend the true situation of the business. The information supplied to the business analyst is given from many perspectives. Opinions can influence how one perceives the related issues. At times, the opinions can add unrelated information which only complicates the role of a business analyst.
Business analyst is not a new term in the business world. It has become extremely popular over the past few years. With businesses expanding world wide more emphasis has been put on the IT teams and departments to monitor and or expand with corporate peers. This has brought about changes in how business operates. A need for business analysis and systems analysts was born. Stakeholders wanted to know the money being spent was worth the expenditure. They needed someone to come in and tell them where to invest within the company to raise profits. The business analyst job was created.
Each day businesses call upon a business analyst to determine what must be done in order to accomplish a certain task. Each avenue must be explored and analyzed for a project proposal to be implemented. The project scope determines what the course of action may or may not be. Each person involved must answer to another until management is satisfied all has been done to rectify the situation. Everything stays on task. The project as a whole is coming together. Teams are co-ordinating with each other to apply the objective into the code. It is all going according to plan. At the end, it all falls apart. Nothing is as it seems. The project has failed to accomplish what it set out to do. The business analyst is hung out to dry. Every finger points to him or her. In actuality it is not the fault of the analyst.
Analysts used to be the ones who had a technology degree but were able to back it up with some basic business knowledge. Now the times are changing. Business analysts are business people who specialize in technology. They can work both spectrum's of the field.
The lack of proper education can be a major drawback for someone breaking into the business world. Many people study business management and other business related courses. There are many diplomas issued each year to hopeful business prospects. When it comes to being a business analyst all the rules change. Although a degree can be helpful, it is not necessary. Experience is the key to success when it comes to a business analyst.
There are times when a company must hire a business analyst. When searching from an outside source there are certain things an employer should determine when hiring the perfect business analyst. Some of these suggestions are common sense. Other items listed may be overlooked in the desperation to find a qualified business analyst.
There are times when a business starts to lose money and no-one is sure where the problem is located. Going over facts and figures only points to the bottom line. The bottom line continues to shrink. People start to get desperate. Strategies are planned and implemented to no avail. Tried and true measures are no longer working. It is time to call on the experts. The business analyst needs to be brought in. The problem is finding one who knows the company.
brought to you by enabling practitioners & organizations to achieve their goals using: