BA 200 - Agile Business Analysis
How to begin a new Agile project as a Business Analysis
-
-
02
-
Objectives:
-
Who should attend?
-
03
-
Introduction To Business Analysis
-
BA Attributes
-
04
-
SOFTWARE DEVELOPMENT LIFECYCLE (SDLC)
-
05
-
Agile Principles
-
Agile Values
-
Scrum Ceremonies
-
Scrum Roles
-
Scrum Artefacts
-
06
-
Requirements Elicitation
-
Requirement Modelling
-
Requirement Management
-
Managing Change Requests
-
07
-
User Story Creation
-
Product Backlog/ User Story Prioritization
-
Refinement/ Backlog Grooming
-
08
-
Release planning
-
Story Decomposition Technique
-
Selecting Themes for Releases
-
Prioritizing Stories for Release Planning
-
Prioritizing Stories for Release Planning
-
Story Mapping Technique
-
Supporting Testing Activities
-
09
-
Stakeholder Management
-
Who are Stakeholders?
-
Importance of Stakeholders
-
Identifying Stakeholders
-
Working with Stakeholders
-
Handling Stakeholders Concerns
-
How to Build Good Rapport with Stakeholders?
-
How to Avoid Conflicts with Stakeholders?
-
Risk Management
-
Requirements Monitoring and Control
-
Sign Off
-
10
-
AS-IS Study
-
To-Be Proposal
-
What is TO-BE State?
-
SWOT Analysis
-
Process Engineering
-
Proposing Solutions
-
Adding Value to Business
-
11
-
Requirement Elicitation Techniques
-
Classic Techniques
-
Contextual Techniques
-
Group Techniques
-
Usages, Challenges, Pros and Cons
-
Practical Scenarios
-
Process of Eliciting the Requirements
-
12
-
Case Study and Hands-on Practice
-
-