Day 1
Software Lifecycle Methods
- Agile, Waterfall, Incremental, RUP
- Agile Manifesto and Frameworks
– Scrum
– Kanban
– XP
IIBA Agile Business Analysis Principles and Framework
- Agile Business Analysis and Creating Value
- Roles of Agile Business Analysts
- Differences of Product Owners and Business Analysts
IIBA Agile Requirement Management
- Strategy Horizon
– Determining Product Vision
– Defining Business Need
– Portfolio Management and Creating Backlog
>> Epic/Feature - Initiative Horizon
– Stakeholder Analysis and Defining Personas
– Defining Feature
– Prioritization of the Features That Will Be Included in the Project
>> Story / Feature Mapping
Day 2
– Efor Estimation
– Defining MVP (Minimum Viable Product)
- Delivery Horizon
– Agile Gereksinim Analizi
>> Writing User Story and Acceptance Criteria
>> Rules of Writing Effective User Story and Acceptance Criteria
>> Common Patterns To Divide User Stories
>> Story Decomposition
>> Spike
>> Business Rules and Non-Functional Requirements
>> User Story Estimation Techniques
– Agile Requirement Documantation
>> Lightweight Documentation
>> User Story Canvas
– BDA (Behaviour Driven Analysis) and BDD (Behaviour Driven Development)
>> Defining Acceptance Criteria and Executable Specifications
>> Writing Scenarios with Gherkin Language (Given, When, Then)
>> Business Rules and Parameterized Scenarios
– Product Backlog Management and Prioritization Criteria
IIBA Agile Requirements Elicitation Techniques
- Requirements Workshops
- Brainstorming
- Design Sprints
Case Study
