Agile business analyst

Agenda v The Business Analysis Body of Knowledge ® Version 3 v Waterfall and Agile project success rates v Difference in Working styles... 9 The Agile BABOK - Strategy Analysis v Wo

THE AGILE BUSINESS ANALYST

Agenda

v The Business Analysis Body of Knowledge ® Version 3

v Waterfall and Agile project success rates

v Difference in Working styles

3

BABOK3

Changes

Needs Solutions

Contexts

Value

Stake holders

v What is the kind of change

we're doing?

v What are the needs we're

trying to satisfy?

v What are the solutions

we're creating or changing?

v Who are the stakeholders

involved?

v What do stakeholders

consider to be of value?

v What is the context that we

and the solution are in?

The Business Analysis Body Of Knowledge® Version 3

BABOK3

Perspective

Management

Architecture

Intelligence Technology

5

What are problems of Product/System?

What is Agile Method?

We  are  uncovering  better  ways  of  developing  software  by  doing  it  

and  helping  others  do  it  

Through  this  work  we  have  come  to  value:

7

Waterfall and Agile project success rates

Introduction to SCRUM Framework

SPRINT

9

The Agile BABOK - Strategy Analysis

v Work with the customer to develop strategic goals and a product vision

v Identifying the “value stream” for the proposed product

v Brokering effective information exchange between the customer and the IT team

v The correct scope for Agile projects isn’t defined requirements, but the well articulated product vision

The Agile BABOK - Business Analysis Planning and Monitoring

v Requirements evolve with greater product exposure

v A lean principle: just enough, just in time

v Requirements are planned for delivery in time-boxed iterations

v BA’s help to negotiate standards and the specifics of product requirements

11

The Agile BABOK - Elicitation and Collaboration

v Understanding the customer’s needs is essential

v Who are your customers?

v How will your customer use your product?

v What are your customers priorities?

v User Stories capture requirements using the following form:

As a <user>,

I want <product requirement>,

so that <desired benefit>

Fibonacci Number Series

1,2,3,5,8,13,21,34

Top Stories for the Sprint Planning

Highest Business Value Highest Priority

Small Stories Testable Stories

No Dependencies Sized Stories

The Agile BABOK - Requirements Life Cycle Management

13

The Agile BABOK - Requirements Analysis and Design Definition

v Understanding “the why” can be as important as “the what”

Epics

Feature

Story

Task

Investment Themes

Program

Team

15

The Agile BABOK - Solution Evaluation

v Delivering the solution in small bites

v Reviewing requirements during planning

v Reviewing requirements during demo

v Requirements describe solution to business needs

v Determining requirements as late as possible

v Validating requirements through prioritizing delivery

Difference in Working styles

Focus

upfront

baseline Location

17

Agile Requirements

v Requirements are defined iteratively and incrementally

v Requirements are maintained in backlogs, not in paper

v Requirements do not go through a formal sign-off process

v Solution requirements are defined via conversations between the team and users

v Business analysis work is done in increments rather than all up-front

v More emphasis is placed on verbal and visual communications versus paper documents

v Just enough, just-in-time

v Requirements are collaborative

Q&A