The evolving role of Business Analysts: adapting to Agile and driving project success
The key role of Business Analysts in complex projects
It is commonly accepted that Business Analysts (BAs) bring their expertise in the delivery of complex projects, more generally focusing on the following topics.
- Scope definition and management
- Requirements elicitation
- Requirements management
- Requirements analysis and documentation
- Defining functional solutions
The emergence of Agile approaches in Business Analysts’ missions
A Shift with Agile Frameworks
Around the year 2000, many frameworks promoting a more Agile approach to project management were created, aiming at disrupting the traditional plan-driven – aka “Waterfall” – delivery of projects.
The Agile manifesto
In 2001, the Agile manifesto was published, which summarized the key characteristics of the various Agile frameworks and methodologies as follows:
- Individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.
Ever since this period, the day-to-day work of Business Analysts has evolved adding new responsibilities and offering new techniques for Business Analysts to successfully support projects.
Scope definition and management with Business Analyst
Traditionally, Business Analysts have always been working closely with the various stakeholders to define the project scope upfront. With Agile, this has become an ongoing effort, as the priorities keep shifting to stay aligned with the end business goals and the delivery of a Minimum Viable Product. Fortunately, tools facilitating the backlog management are extremely helpful here. Most frameworks insist on the role of the Product Owner, and the importance of having this “voice of the business” making efficient decisions while fully available to support the Agile team.
Requirements elicitation
Through document reviews, system analysis and regular workshops with stakeholders, Business Analysts gather critical requirements, insights and expectations that guide the project’s direction. Agile proposes to streamline the interactions and the communication with the various stakeholders. The Product Owner’s availability guarantees that it is not always necessary to organize large workshops with many stakeholders, therefore massively speeding up the requirements elicitation process. In the past few years, new tools have emerged that facilitate the elicitation of requirements in some specific areas. For example, Figma has completely transformed the way of building or updating User Interfaces, allowing to quickly build interactive mock-ups, through which a very detailed feedback can be obtained. More recently, the emergence of IA has offered new techniques to scan through large volume of documentation, extracting key words or key concepts that can be analysed by the Business Analysts.
Requirements management
As projects evolve, requirements will change. Business Analysts track and update requirements throughout the project life cycle to ensure that requirements reflect the up-to-date stakeholder views.
Thanks to the tools that were introduced to facilitate the adoption of Agile principles, the constant evolution of the requirements and the shifting priorities are easily managed by the BAs.
Requirements analysis and documentation by Business Analysts
Business Analysts meticulously analyse the collected information to identify patterns and insights, documenting requirements clearly and accessibly. This documentation serves as a vital reference for the project team and stakeholders alike.
Agile frameworks encourage the usage of User Stories, or something equivalent, to document valuable software features. In the early days of Agile, these were written on post-its plastered on the walls of the team’s area. This then shifted to User Stories managed via the tools used to handle the Product Backlog, simplifying the process even more.
Defining functional solutions
Finally, BA leverage their analytical skills to propose tailored solutions that directly address the identified needs. This includes collaborating with technical teams to ensure that the solutions are feasible and aligned with the business objectives.
This aspect of the Business Analysts work has also dramatically changed with the shift to an Agile approach. Successful project teams have to include both technical and functional profiles. The Business Analysts usually have a very deep functional understanding while at the same time understanding the complexities and the constraints of the technical development. Agile guarantees that the alignment between the business objectives and the technical solution is always under close scrutiny.
Share your insights!
How do you think the role of business analysts has evolved with the rise of Agile methodologies? Share your insights in the comments!
More about us ?
Check our Linkedin Profile : ‘ESCENT | LinkedIn
Check our Instagram Profile: ‘escent s.a. (@escent.consulting)
Find more articles on: News | Escent