Business Analysis In Agile – A Differentiated Narrative€¦ · Business Analysis in Agile –...

© 2014 BA Convention

Business Analysis In Agile – A Differentiated Narrative

Presented By: Praveen Kumar Benguluru

Associate Vice President – Business Solutions,

Scope International Private Ltd.

© 2014 BA Convention 2

Click to edit Master text styles

Click to edit header

Key Takeaways.....

• Understanding the need for Agile

– Business challenges

– Technology challenges

– How Agile Helps

• Business Analysis in Agile

– Business Analysis – Key Steps

– Approach for Business Analysis in Agile Methodology

– How Functional Architecture helps

• Our (BA) Role In Implementing Agile

– Identifying challenges & issues in implementing agile

– Managing the Change




Agenda

• Business Challenges

• Technology Challenges

• How Agile Helps

Understanding the need for Agile

• Business Analysis – Key Steps

• Functional Architecture

• Agile – Scrum Framework

• Business Analysis In Agile & User Stories

• Business Case – Funds Transfer

Business Analysis In Agile Development

• Identifying the Challenges

• Managing Change

Your (BA) Role in implementing Agile


How Agile helps in addressing business and technology challenges

Understanding the need for Agile




Business Challenges

Source: Open Compliance & Ethics Group




Technology Challenges

Requirements Volatility

Scope Changes

Too Many People & Processes from Build to Deployment

Regulatory Changes

Time to Market

Lack of Documentation

Environmental Issues

Organizational & Functional Silos




How Agile Helps

• Improves Time to Market

• Reduces cost and increases ROI

• Absorbs requirement changes easily

• Reduces the gap between Business & Technology

• Allows business to see the system functionality earlier in the life cycle

Business

• Minimizes the cost of requirements volatility

• Eliminate Waste Processes & Improves Productivity

• Build Strong Teams & Collaboration

• Promotes Iterative & Incremental Development

• Ensures quality & quicker delivery

Technology


How Business Analysis is Carried out in Agile World

Business Analysis In Agile Development




Business Analysis – Key Steps

Big Picture

Capture Business Requirements & Non Functional Requirements. Use various elicitation techniques like probing, survey., brainstorming, .etc Document emerging requirements

Prioritize Requirements Translate Business Requirements into functionality Feasibility Study

Measure & communicate project benefits Case for Standardization Think of big picture

Analyze the impact and dependencies between functions & systems Data/ Impact/Migration..etc Analysis

Arrive at Functional Solution Assess & validate the proposed solution How to support the implementation of solution




Functional Architecture – An Overview

“ Functional Architecture provides holistic view of functional components that needs to be developed as part of the system along with the actors (users) who will be using the system via access point. It also depicts any interaction required with other interfaces.”




Agile – Scrum Framework

Source: http://idimension.wordpress.com

Widely Used Framework

http://idimension.wordpress.com/




Business Analysis In Agile

Solution Assessment & Validation

Functional Analysis

Creating Business Cases

Requirement Analysis & Management

Requirements Elicitation

Hig

h L

evel

Functional Architecture Functional Breakdown Structure (FBS)

F1 F2 F3


Functional Analysis

Creating Business Cases


Requirements Elicitation

Det

aile

d

User Stories I – Independent N – Negotiable V – Valuable E – Estimable S – Small T – Testable


Functional Analysis

Spri

nt

Functional Integration

F1 F2 F3

End Product




Business Analysis in Agile – User Stories

Prioritization

Sprint 1 Sprint 2 Sprint 3

High Value Low Value High Value Low Value High Value Low Value

High Value Low Value

Detailed

Story Mapping

-No Ambiguity -Clear & Precise Statements -Detailed enough to proceed with shippable product -Independent enough to be delivered in a sprint

-Map user stories to provide holistic view -Able to easily identify dependent user stories -Easily readable -Easily Maintainable




Business Case – Funds Transfer

“ Provide funds transfer capabilities in online banking that enables customers to do funds transfer between their own accounts, between the accounts within the same bank and inter-bank funds transfer”

•How to manage beneficiaries

• Is there limit management required

•Handling of standing orders & scheduled transfers Requirements Elicitation

•Beneficiaries to be retrieved from EDM

• Limits should be configured by Back-Office

•Providing transfers features is high priority followed by beneficiary management & limits.


•Estimated volume of 10000 transactions / day converted from branch to online @ savings of $5/ transaction Creating Business Case

•Beneficiary registration is required to do inter bank funds transfer

•Alerts & Notification can be implemented as common functionality Functional Analysis

• Get customer data, accounts, standing orders from host systems.

•Get Bank Details from Bank Master data and use the information to enrich transfer information with settlement bank details.





Funds Transfer – Functional Architecture

Source Systems

Bank Master

Data

Core Host

Systems EDM

Payment

System Rates System

Transfers Beneficiary

Management Rules Engine Limits

Management

Reporting

Bank

Details

Multiple

Details

Standing

Orders FX

Bene

Details

Booking Enrichment Settlement

Standing Orders & Scheduled

Transfers

Enquiry

Maintenance

Enquiry

Maintenance

Validations

Cross Currency

Rules

Product Rules

Settlement

Rules

Transaction

Reports

Limits

Reports

Beneficiary

Reports

Exception

Reports

Standing

Order

Reports

Audit

Reports

Interface Systems

Custom

Reports

Validations

Common Functionality Alerts &

Notifications

Exception

Management

History

Authentication

Regulatory

Rules

Audit &

Reporting

Source Account Management

Host Integration

Customers

Ops User

Ops Manager

Production Support User




Funds Transfer – Functional Breakdown Structure

Functional Breakdown Structure (FBS)

Beneficiary Management

Transfers Common Functions

Early Sprints Early Sprints Early Sprints

Later Sprints Later Sprints Later Sprints

Sprint1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6

High Value F1 F2 F3

Low Value F1 F2 F3

Prioritization Matrix

Pri

ori

ties

Add Bene

Delete Bene P

rio

riti

es

Booking History

Pri

ori

ties

Authentication Audit


How can we bring a change

Our (BA) Role In Agile Implementation




Identifying the Challenges

Organization Agile

Training & Awareness

Industry




Managing the Change

Make all your stakeholders understand about agile

Set the expectations upfront and challenges in implementing agile

Adapt your business analysis approach to agile methodology

Establish continuous feedback loops to fix any issues that are cropping up

Document learnings & shortcomings and work for resolution (Retrospection)

Highlight the importance of team discipline and self managed teams.


Key Takeaways

Conclusion




We (BAs) hold the key

• Understanding the need

– Understanding the challenges and identifying the need for agile

– Looking at how agile helps (identify right tools & frameworks)

• Business Analysis in Agile

– Understand the approach of business analysis in agile

– Understand importance of functional architecture and how it helps in FBS

– Adapt for iterative & incremental change with continuous functional integration

• Our (BA) Role In Implementing Agile

– Make stakeholders understand the benefits & challenges in implementing agile

– Stress the importance of prioritization & continuous integration

– Bring all stakeholders into common understanding

– Make a transition plan for agile implementation

Business Analysis In Agile – A Differentiated Narrative€¦ · Business Analysis in Agile –...

Documents

Transcript of Business Analysis In Agile – A Differentiated Narrative€¦ · Business Analysis in Agile –...