Reasons Projects Fail for a Business Analyst

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.

It was a joint effort from the beginning. When the problem was recognized as such and something needed to be done is when the business analyst came into the scope of things.  Management said get it done.  IT said it is done.  Low end said it just isn't what we need anymore.  So what happened?  The first thing is failing to disclose all information necessary do make a proper assessment of the situation.

A business analyst is not a mushroom.  You can not keep them in the dark.  They have to know the in's and out's of the company.  He or she must be aware of the company vision or end goal.  A few facts and figures just will not do the job. Disclosure can close the project tighter than a drum.

 Acting as the liaison between departments and upper management, the business analyst must gather data from everyone involved in the project.  When someone feels they do not want to be a team player this can cause a disruption in the scheme of things.  Each team was delegated a task.  Upstarts who think they know what is the end result and rush to meet the goal, may find themselves dead wrong.  However there are times when up and coming management leaders do the same thing.  Instead of looking at the big picture and realizing all the intricate parts are necessary, they view a segment as the solution.  This can only lead to failure.  Communication is the key to success.

If someone does have a better plan, a good business analyst will listen to the idea.  He or she may find it a viable solution for one aspect of the entire project.  Unless the business analyst is told of the idea it can go unused or worse yet misconstrued as the proper solution.  Communication is most commonly the reason projects fail.

The business analyst is what holds the project together.  He or she is what makes the teams work together as teams.  The analyst is the one who takes all the pieces of the puzzle and puts it together so the end result is success.  Think of the business analyst as the nails in a house.  When you do not use nails to hold it all together you wind up with nothing more than kindling.

What Makes a Good Business Analyst

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 good business analyst is creative, a people person.  Someone wanting a more hands on approach to business and problem solving.  The good business analyst will look for opportunities to grow and learn.  He or she will listen attentively to what others are saying.  The good business analyst is like a walking encyclopedia about the company he or she works within.  They will know people from every department.

The good business analyst may be a part of the IT team or department.  He or she may even be able to produce usable code for practical remedies to small tasks.  He or she will understand technology and the jargon that leaves the common layperson confused.

What makes a good business analyst is the ability to listen to what is being said and hear what is not.  The good business analyst can read into the meaning of stakeholders words.  He or she can understand the needs being expressed when the stakeholders do not always know what they are.  The good business analyst will be able to determine if the requests from stakeholders or end users are viable.  In some cases they are not and it is up to the business analyst to inform what can be done versus what is wanted.

The good business analyst will have information available about the latest technology.  He or she will know the formulas or programs used by corporate peers.  The good business analyst will be able to recognize trends and differentiate between them and fads.  They will understand the end user market.

The good business analyst will understand people.  He or she will be a motivational person who can gear people into wanting to complete a project.  The good business analyst will be able to point out someone's strengths and help to build on those.  He or she will recognize when a person is having a conflict and try to help resolve the issue.  He or she may even be able to create teamwork within separate departments to meet a goal or deadline.

The good business analyst commands respect because he or she gives respect.  You will not find the good business analyst spreading rumors or gossiping.  He or she will squelch the first signs of trouble and stand up for what he or she believes in.  There is no room for garbage in the office.

The good business analyst is a visionary,  a creative thinker, and innovative. He or she is fun to work with and carries a positive attitude.  Very few people do not like the good business analyst.

Business Analyst Job Description

The job description of a business analyst is rather extensive.  He or she must first determine the needs for a company by using many tools.  The business analyst may conduct interviews with management and other department leaders.  He or she must analyze documentation, facts and figures.  The analyst should incorporate a site survey to determine applications being used and what may be needed for superior quality performance.  He or she will consider business applications currently being used which may or may not be working.  The business analyst will do a business analysis and a work flow analysis to assess difficulties in reaching goals and to determine a better strategy.

A qualified business analyst will be able to ascertain the true needs to be met by the project.  He or she will be able to transfer information from management into needed data.  Statistics from other sources will be assessed and turned into usable information.  The business analyst will be able to compile a report in an easily understood projected vision to be implemented.

The job description of a business analyst does not always but should include excellent communication skills.  He or she needs to be able to address a diverse group of inside and outside personnel.  He or she should be able to motivate the departments to challenge themselves and reach their goals.  The business analyst will be required to relay information from the IT team or department to the clients in easily understood terms for both groups.

The business analyst should have past experience to draw from when processing data and information.  He or she will possess knowledge used in case studies and transfer it into usable information.  Prior situations should be able to be compared to avoid counterproductive actions.

The business analyst will be able to draw from known resources when outsourcing or external interactions are needed.  He or she will be able to incorporate joint venture relations into the project scope when it is necessary.  Determining this critical point is instrumental in the job of a business analyst.

Acting as a liaison between clients and development departments, the business analyst shall distinguish requests from needs.  He or she will assess the proposed project plan to ensure all needs are met.  The verifiable solution shall be one which guarantees success.

A statement of purpose will be proposed by the business analyst to ensure the end results are satisfactory to all involved.  There will be a project goal integrating all data collected.  Documentation will be provided by the business analyst to determine which aspects of the project will be handled by outside sources.  These sources shall be listed with critical attention being paid to the specific task of each organization.

The business analyst will have a good understanding of what is expected.  There are many aspects of the project proposal.  He or she will involve themselves with each unit to instill continence and still maintain productive action.  The professional analyst will be able to focus on each department independently and maintain a broad vision of the project scope.  These are the duties of a business analyst.