ALSTON HODGE, ENTERPRISE AGILE COACH

FEBRUARY 9 , 2012A PRESENTATION TO AGILE -CINCINNATI

The Evolution of the

Agile Business Analyst

A Quick Survey

Within your company:

Do you have Business Analysts?

When you transitioned from traditional waterfall to Agile

approach, what happened to your Business Analysts?

What role (product manager, process engineer, business

analyst, etc.) typically serves as the Product Owner?

Do you have multiple POs per project?

In 10 words or less….

What do you think is the role of a Business Analyst?

Consulting:

In the Beginning……

1970s – beginning of software application development Business Analyst role emerged Liaison between business and computer departments Goal of application development: increase revenue, reduce

cost 1980s – emergence of PCs

Need for distributed systems Client serve technologies Attempts to formalize SDLC methods Consulting Business Analysts

1990s – emergence of Internet IT department struggle to keep up Businesses do their own development Quality Movement

In the past decade….

Business Analysts found in IT and business areasCombined IT and business knowledge/skillCore task: Defining requirements

Shift from “software” to “business systems” Translator: Business-speak to Techno-babble

More offshoring Working with distributed, culturally diverse teams More detail required for some business sectors (insurance)

Agile was formally recognized No formal roles Team focus

Agile and the Business Analyst

Agile is Humanistic “Individuals and Interactions” Customer Collaboration”

Agile is Pragmatic Working software Highest business value first

Product Owner assignment is most important in Agile.What role should fill the job?

PO Core Responsibilities

Establish vision & goals for overall project

Represents the users or customers for the

project

One voice, even if not one person

Typically a person with product knowledge

More Responsibilities

Knowing what to build and in what sequence

Manage the return on investment (ROI) Establishes baseline target ROI Measures project against this baseline Prioritizes product backlog to maximize ROI

Calls for releases

Agile Business Analyst (ABA)

Traditional BA techniques become

even more important in Agile:

Liaison between Business and IT

Detailed Requirements

Gathering/Definition

Stakeholder analysis

Constant process re-engineering

Agile Business Analysis is:

About increasing the delivery of maximum business value

Ensuring the development team has: the right information The level of detail At the right time To build the right product

Product Owner

Scrum Master

Scrum Team

Simple Scrum

Product Owner

IT PM

ArchitectScrum Master

Scrum Team

Business PM

Product Owner

Product Owner

Product Owner

Lead PO/ABA

IT PM

ArchitectScrum Master

Scrum Team

Business PM

Product OwnerSystem C

Product Owner System A

Product OwnerSystem B

Misuses of an ABA in the PO role

The Un-empowered BA serving as Proxy PO BAs commonly used for PO role If not truly empowered, a proxy only adds to the length of

the feedback loop. Tendency to do all of the backlog (not prioritized)

The un-supported BA serving as Proxy PO New/inexperienced BA assigned to complex projects No current-state documentation

The un-trained BA No business knowledge No Agile training or experience

Business Analysis is commonly under-valued

What does it take to be a Great ABA?

Focus on delivering maximum business value

Business knowledge (of course)Facilitation skillsBusiness Analysis skills:

Story Mapping Personas/Stakeholder analysis Business Modeling Detail-oriented

Timing is everything

Agile business analysis delivers pretty much the same artifacts as traditional, but: Lightweight (avoiding waste) Just-in-time More frequent feedback loops Evolve over time

Recommendations for Becoming a Better ABA

Get certified in Scrum (CSM or CSPO)Lots of great books on Agile

practices/techniques User Stories Applied – Cohn Agile Modeling – Ambler Agile Estimating and Planning – Cohn Agile Product Management with Scrum - Pichler

Visit your local IIBA chapter BA Competency model Credentials model (CCBA, CBAP) Agile Extension to BABOK

BA Body of Knowledge

International Institute of Business AnalysisCertifications availableThe Agile Extension to the BABOK Guide

(Nov 2011)

The Agile Extension to the BABOK Guide

Agile Extension drafted - November 2011Business analysis primer for Agile SW

developmentIntro to business analysis practices/techniquesMapping traditional practices to Agile

practicesFor all team members, not just ABAs

Get the draft copy now, for free!

IIBA Agile Extension includes….

Business Analysis in different Agile lifecycles Scrum XP (eXtreme Programming) Kanban

Techniques Personas Value Stream Mapping Story Mapping Kano Analysis Backlog Management Agile estimating Collaborative Games Retrospectives Lightweight documentation

Questions?

Contact info:

Alston Hodge, Enterprise Agile Coach1613 Crosstimbers Drive

Louisville, KY 40245

309-531-0611

alstonehodge@gmail.com