Smarter ideas worth writing about.

How the Business Analyst Drives Value

As a Business Analyst, I commonly hear questions about how a Business Analyst adds value. What would a Business Analyst do on my project? Why do we need a Business Analyst? What value would a Business Analyst provide? 

These are all valid questions. And we, as Business Analysts, need to be prepared to advocate for ourselves. We know that we bring value to projects, but if we cannot articulate that value then our customers will not (and should not) pay to include our services on their projects.  

In order to understand the benefits that Business Analysts bring to a project, it is important to look at the general criteria for project success. Successful projects generally consist of four primary components: Completion within the Timeline, Adherence to Budget, Impact on Everyday Business, and Solution Adoption/Usefulness. In other words, a customer wants to know “Will I get what I want, within the approved time frame, for the amount of money we agreed to, and allow my staff to keep their day jobs?” 

Value to the Project:

The primary function of a Business Analyst is to identify and clarify the needs of the business group on the project. Once the customer identifies the overall project goal, it is the Business Analyst’s responsibility to develop a thorough understanding of that goal and ensure that the functionality will yield the desired result. 

What is often overlooked, however, is how a good Business Analyst maximizes the efficiency of the project team. While the development team works to define the technical direction and build the solution features, the Business Analyst works behind the scenes to provide timely information, clarify questions, remove roadblocks, and ensure that the functional development is moving the project toward a successful conclusion.

Value to the Customer:

From a customer’s point of view, a software project can be daunting. Every organization has competing priorities, limited budgets, and multiple stakeholders with differing opinions. Once a project is approved, there is immense pressure to successfully achieve the business objective on time and within the budget.  Additionally, employees will be asked to take time away from their usual tasks and obligations to contribute to the project through defining requirements, providing feedback to developers, and testing functionality as it is created. It is here where the Business Analyst can provide significant value in a number of ways.

  • Defining Scope – Whether it is completed before the project begins or during the discovery phase, a strong Business Analyst is adept at understanding the business objective(s) and the possible technical solutions. They provide valuable insight to ensure that the critical features are defined correctly and that unnecessary features are omitted to save time and money.  The Business Analyst will be able to articulate how business needs can be met with the greatest impact to productivity while ensuring the least impact to cost.
  • Facilitating Requirements Discussions – If multiple stakeholders are involved in the definition of a project, there will be some confusion or disagreement about the true priorities of the solution. The Business Analyst serves to clarify the needs of the project to ensure an overall prioritization is established, thus allowing all opinions to be heard, considered, and reconciled.  Additionally, the Business Analyst will facilitate and drive these discussions, ensuring that all of the stakeholders are represented equally. 
  • Serving as a Representative of the Business – During the project, it is inevitable that the stakeholders will need to maintain focus and commitment to their primary job and have the flexibility to focus on core business initiatives, which may divert their attention away from solution projects. In these times, the Business Analyst can serve as an advocate for the business stakeholder to limit the impact of their absence on the project.  The Business Analyst should be able to successfully represent the business group even during their absence.
  • Assisting with Testing & Documentation – The Business Analyst drives value through the testing and implementation phases to ensure the solution meets the customer’s requirements.  Their intimate knowledge of detailed business needs, strategic initiatives and technical functionality allows the BA to create test cases and execute test scripts which align with the customer’s business requirements.  The BA will deliver knowledge transfer and documentation targeted to the stakeholders.

Value for Software Developers:

  • Allow Developers to Focus on Development – Although the development team can work with customers to clarify requirement details, time spent refining requirements is time that is not spent developing. Business Analysts understand the level of detail that developers need to be successful so they can bridge the gap between the business requirements and the technical requirements.  This time management allows the developers to focus on what they do best -creating the solution.
  • Managing the Backlog – The optimal project will have the user stories and requirements defined at least 2 – 4 weeks in advance of when they will be developed.  When this occurs, the development team has time to become familiar with the requirements and properly plan their approach.  When a Business Analyst is involved on a project, they can build this backlog in advance, allowing time for clarification of questions which may arise around development approach, risks, or scope.

Value for Project Managers/SCRUM Masters:

  • Change Management – Business Analysts help Project Managers manage project scope, budget, and timeline by becoming experts on the requirements of the project.  This expertise ensures the team is focused on the goals and allows the BA to be the first to communicate when priorities may need to shift or when they see requests alter current scope. This results in a more effective project delivery approach that will ensure greater chances for success. If the business does want a feature that is outside of the original project objectives, the BA can help clarify and communicate the business value of the feature to help inform decision makers.
  • Confidence in the totality of the elicited requirements – The Business Analyst will ensure that requirements are understood, communicated, and thoroughly evaluated, which is critical to ensure the project stays on schedule and within budget. When requirements are not fully articulated with “success criteria”, there is a higher risk that something will be omitted during development or that an incorrect development approach is taken. By including a Business Analyst early in the project, Project Managers can trust that the work that we think should be done is actually the work that will satisfy the needs of the customer and the project.
  • Focused Conversations – The Business Analyst helps the Project Manager keep the team moving in the right direction by focusing conversations on the identified business objectives. This not only helps the team stay on track by minimizing distractions, but can also help prevent scope creep.

Business Analysts will effectively elicit and document requirements; however, their value to a project team far exceeds these tasks. They bring a sense of objectivity and perspective, ensuring that the business problem to be solved is so well understood that the solution is targeted, effective, and efficiently designed to meet the business need.  

Their value can be seen when:

  • BAs add value to the Project by increasing the team’s efficiency;
  • BAs add value to the Customer by clarifying scope and advocating for the business stakeholders;
  • BAs add value to Developers by managing the backlog and clarifying requirements, allowing developers to devote their time purely to development efforts; and
  • BAs add value to Project Managers by providing input for change management.


About The Author

Business Analyst
Phillip is a Senior Business Analyst on Cardinal's Raleigh/Durham Project Services team.  He leverages a broad depth of experience in requirements definition, requirements elicitation, scope management, and product backlog planning.