Scribd
Upload
7 views

Ba KT

An Agile Business Analyst (Agile BA) helps stakeholders understand Agile methodology and assists the development team with business requirements. Key roles of an Agile BA include supporting the product owner, understanding business needs through discussions with stakeholders, analyzing the business domain, and maintaining and prioritizing the product backlog. An Agile BA also facilitates discussions to help the team understand the overall project strategy and requirements.

Uploaded by

sampath
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
7 views

Ba KT

An Agile Business Analyst (Agile BA) helps stakeholders understand Agile methodology and assists the development team with business requirements. Key roles of an Agile BA include supporting the product owner, understanding business needs through discussions with stakeholders, analyzing the business domain, and maintaining and prioritizing the product backlog. An Agile BA also facilitates discussions to help the team understand the overall project strategy and requirements.

Uploaded by

sampath
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 23

Who Is an Agile Business Analyst?

• An Agile Business Analyst (Agile BA) understands the Agile


methodology and can help a business use Agile principles. They work
with stakeholders to help them understand the benefits of Agile and
how it can help their business. They also help the development team
understand the business requirements and how they can be met using
Agile methods.
Role of an Agile Business Analyst

• One of the key roles of an Agile Business Analyst is to support the


product owner with the decision-making process so that they don’t go
rogue during the project. Here are some more roles and responsibilities
of an Agile Business Analyst:
Recognize the Business Needs

An Agile BA holds discussions with stakeholders to understand their


requirements and their vision of the product. This is then translated into
business needs and communicated to the team members to make them
understand the expectations of the project.
Analyse the Business Domain

An Agile BA needs to analyse the whole system in detail - from the first
iteration to the release phase of the project. They work closely with the
development team to understand the initial requirement of the project,
the scope of the project, and also identify automation areas of the
project.
Stock and Groom the Product Catelog

Stocking the product backlog refers to establishing user stories that


represent the overall scope of the project. Agile BA help the product
owner establish user stories from the requirement models created during
business analysis.

Grooming the product backlog refers to maintaining the product


backlog so that it does not become a burden on the product owner and
the team. Agile BA achieve this by considering purpose, organizing and
prioritizing user stories, and splitting epics into user stories.
Helps Team Understand the Big Picture

• An Agile BA helps the team to get a better grasp of the project and
where it fits within the organizational strategy. This can be done by
facilitating a number of discussions such as:
• What business processes should be created, eliminated, or revised?
• What stakeholders are involved in the project?
• What information should be tracked?
• What policies and rules should be followed that affect business behaviour and
decisions?
How to Become an Agile BA From a Traditional BA?

• There are many ways to become an Agile BA from a traditional BA.


• Join an Agile development team and learn from them.
• Attend Agile training courses or workshops.
• Read books or articles on Agile methodology.
• Analyze product graphs while taking important decisions.
• Develop crowd-pulling techniques.
• Whichever route you choose, the key is to have an open mind and be
willing to adapt your approach to fit the Agile framework.
What is an agile epic?
• An epic is a large body of work that can be broken down into a
number of smaller stories, or sometimes called “Issues” in Jira. Epics
often encompass multiple teams, on multiple projects, and can even be
tracked on multiple boards. Epics are almost always delivered over a
set of sprints.
User stories
• A user story is an informal, general explanation of a software feature
written from the perspective of the end user. Its purpose is to articulate
how a software feature will provide value to the customer.

• User stories are development tasks often expressed as “persona + need +


purpose.”
What Is a Good User Story?
1.Card: Written description of the story, used for planning and as a
reminder
2.Conversation: Conversations about the story that serve to flesh out
the details of the story
3.Confirmation: Tests that convey and document details that can be
used to determine when a story is complete.
User Story Template

• When writing a user story, remember that user stories follow a


standard template:

As a < type of user >, I want < some goal > so that < some reason >.

You might also like