Why do Business Analysts Fail in Projects

The study says on an average only 30% of projects get success globally. The remaining projects are either go obsolete or on hold for some or other reason. As we have discussed earlier, the business analyst is the liaison between the customer or business user and the remaining team members. He/she is one kind of link between all of them who need to keep communicating with everyone till the successful deployment of the project.

Here are the few things I have listed out a business analyst fail which may land a project in trouble.

  • Poor Requirement Understanding
  • Lack of communication among the team members and customer
  • Ignoring the stakeholders
  • Making Assumption

Poor Requirement Understanding : 

A project starts with requirement gathering. So it is important for a business analyst to understand the business processes and its requirements thoroughly. Any kind of misunderstanding leads to big trouble. A business analyst is also responsible for preparing requirement documents and writing use cases for the application. So if he/she is not clear with requirement then there are high chances of the wrong documentation.

    The purpose of a software development application is to serve the business need. A failure can be avoided at a very primary stage by understanding and gathering the requirements properly.

Lack of communication among the team members and customer:

A frequent scrum meeting with team members is a must. A role of a business analyst is to explain the requirements and business processes to the developers and testers. And also he is responsible to answer and discuss all the questions asked by the team members. But if this communication fails then there will be a big mess up with the project. 

Ignoring Stakeholders: 

A very common mistake business analysts do is to avoid communication with stakeholders. Stakeholder analysis is usually neglected by analysts because they expect project managers to complete this task but It is a combined effort of the project manager and business analyst, and more importantly, it should be revised very often.

Revision should also be the responsibility of the business analyst. Generally, in requirement analysis phase stakeholders are missing. So ignoring stakeholders means ignoring the requirements.

Making Assumptions:

It is quite a common human tendency to assume a few things. Automatically the person talks “I think”, “I wonder”, “It is like that”, etc. A business analyst must not start any work based on assumptions. He must ask proper questions if is not satisfied after listening to the business user.

For example, If you assume something and explained developers and again he assumed something else and developed the application accordingly then it is a big mismatch and leads to huge chaos.

Remember there is always an excuse for not delivering a successful end product

but thousands of efforts go into the successful delivery of the project. So being a business analyst you always have to keep track of all the things which all are required to get the desired outcome.

Recent Posts

What is the Average Salary of a Business Analyst

Hi Friends, being an aspiring business analyst you must be curious about the salary packages…

What are Some Agile Estimation Techniques

There must be some sort of reasonable estimation for managing or planning a project. Study…

What is the Difference Between a Business Analyst and a Scrum Master

Hello friends!! So far we have seen the different methodologies of SDLC and the role…

What are the Different Types of Backlogs

We have seen in my earlier blog that how the agile methodology evolved with the…

What is the Difference Between Scrum and Kanban

Agile methodology witnessed that software development is fast-paced and quality delivery in a short time…

What is the Difference Between the Test Case and the Test Scenario?

As we are very much aware that testing is an integral part of the SDLC…