The Role of Business Analysis in Software Development: What Does a Business Analyst Do?
Why do I need a Business Analysis (BA)? Many business owners ask this when reviewing a comprehensive quotation from a software development agency. This article answers this and other questions, including what it is, when it's needed, and the role of Business Analysis in software development.
It's tough enough to define Business Analysis since it's a wide discipline with many objectives. Consider two ideas offered by the International Institute of Business Analysis (IIBA) and the Project Management Institute (PMI) to better grasp what business analysis entails.
According to the IIBA, "Business Analysis is the practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders". PMI, on the other hand, has a somewhat different definition. They describe business analysis as the use of information, skills, and methods to identify issues and solutions to satisfy company demands and manage stakeholder requirements, enabling the effective execution of a project concept.
These two definitions are almost similar in essence. However, IIBA emphasizes the BA's role in driving change within the organizational context, while PMI focuses on identifying customer needs. We agree with both of the above points of view. At CodeStringers, we believe that Business Analysis serves as a bridge between the development team and the client, aiming to provide unique solutions that meet customers' requirements and drive profitability.
To grasp the function of the BA in software development, we should first review the typical software development process. We've fine-tuned our agile development methods – Scrum and Kanban – to maximize team velocity, deliver superior quality, and enable the iteration that great software requires. Six steps are included in the software development process at CodeStringers:
Ideate
Understand your problems and needs through a series of workshops with stakeholders who articulate requirements and their value
Plan
Draft user stories (feature requirements), wireframes (low fidelity screen designs), evaluate user journeys, and style user interfaces
Architect
Select technologies, design architecture, estimate effort and duration, recommend team structure, and establish a budget
Develop
Build the application services and clients including database, API/web services, web and mobile client applications using Agile methodology (Scrum or Kanban)
Operationalize
Configure production environment, deploy application, host and manage, and rollout to the organization and/or end-customers
Iterate
Great software is the result of iteration based on user feedback and expanding and improving functionality and experience
BAs will have differing levels of engagement and scope of work in line with the stages of software development.
A BA evaluates the product's market potential and ways to achieve it at this stage, working closely with a solution architect and a UX researcher.
Investigating business issues.
The BA analyzes the owner's major causes of pain, as well as the market gap. These concerns will be reflected in the initial technical proposal as well as commercial requirements.
Generating a business value estimate.
The primary wireframes are generally influenced by understanding the product's trajectory and the projected market niche. This activity also entails determining how a future product will connect with its intended audience and how it will be monetized.
Preparing nonfunctional requirements.
The BA creates the description of how the system is and specifies the functionality's limitations. They incorporate the system's quality attributes, such as usability, security, dependability, performance, availability, and scalability, while creating this documentation.
Drafting functional requirements
Functional requirements must also be properly documented by a BA. These are the features that engineers build into products to help users meet their needs.
Creating the main backlog.
The project's broad outline is already in place in terms. A BA ensures that all of the previously stated business elements are reflected on the to-do list.
These are the stages in which the future product team has already conducted extensive preliminary research. When comparing the overall scope against expected business value, the BA plays an important role.
Story mapping. This is one of the BA's essential responsibilities. The story-mapping process involves several decision-makers, including the product/project manager, stakeholders, UX designers, and development team members. However, BA ensures that the intended user flow aligns with the approved business values.
Developing acceptance criteria.
These are the criteria used to assess if a feature meets the needs of both stakeholders and end-users. A product manager and a BA share this duty.
Prioritizing backlog items.
BA can assist in determining which cluster of tasks is more essential or relevant from a business point of view.
The business analyst's responsibility in this stage is to ensure that the development aligns with the previously approved business values and criteria.
Setting up preparation activities. The BA monitors the pre-development phase to ensure that each sprint adheres to the agreed-upon requirements and objectives.
Tracking the development process. Although the BA does not work directly with developers, they attend daily Scrum and Standup sessions to ensure that they meet all business needs.
The BA's responsibilities involve receiving customer feedback and analyzing the results to identify areas for potential improvement.
Collecting and analyzing customer feedback.
There are still some improvements to be made. One of the BA's tasks is identifying the final product's strengths and weaknesses from a business standpoint.
Making the plan for the next backlog.
The BA shapes the business issues to enhance, alter, complete, or delete based on customer feedback.
Reduce the cost of development. Although a business analyst isn't directly responsible for a project's finances, they can affect costs by clearly outlining requirements and reducing rework.
Release products on time. A business analyst prepares a plan that details each step and the time required to complete it. This allows us to manage our time better and ensures the delivery of a high-quality product on time.
Solve problems effectively. A business analyst's primary responsibility is to identify solutions to stakeholders' problems. It is critical to identify requirements and needs in this regard. However, needs may change during the development process. If this occurs, a business analyst must review stakeholders' requirements and objectives and propose appropriate solutions.
Business Analysis, as you can see, is a crucial part of software development. The advantages of having a BA on the project team are often greater than the costs. We strongly encourage our clients not to skip this part, as it can have severe consequences, which we will cover in more detail in future articles.
In a no-risk discovery we look at your CRM, finance and operations systems and who owns each part, and show what a connected system would do differently. You pay only if you proceed. Or see how we approach it.
More on the same problem:
Software Development Team Structure: The Roles, Models, and Right Size (article)
A Build vs Buy Analysis Framework (Stop Asking the Wrong Question) (article)
The Emerging Market for Integrated Business Solutions (video)
The product manager decides what to build and why, owning priorities and the business case. The business analyst works out exactly what that means: the detailed requirements, the rules, the data, the edge cases and the acceptance criteria. On a small project one person does both; on a larger one the product manager faces outward to the market and the analyst faces inward to the team.
Often, though the title varies. Someone must turn goals into stories with acceptance criteria, map the current process and chase down the rules that live in people's heads. In Scrum this work sits with the product owner, who rarely has time for all of it. A business analyst supporting the product owner is common on teams building for complex operations.
A documented current process, a list of stakeholders and their needs, functional and non-functional requirements, user stories with acceptance criteria, data definitions, a prioritized backlog and a traceability matrix linking requirements to goals and tests. On agile projects these are living documents updated each sprint rather than one specification signed off once.
When the project touches more than one department, replaces an existing system, involves business rules nobody has written down, or has stakeholders who disagree about what the software should do. Those are the conditions where requirements go wrong. A short engagement at the start, before the budget is committed, pays for itself in rework avoided.
The ability to ask questions until the real process appears, write requirements that can be tested, model data and workflows, and facilitate a room of people who disagree. Enough technical understanding to know what is feasible. And the discipline to keep documents current as decisions change. Domain knowledge helps but can be learned faster than the core skills.
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.