1. © 2014 BA Convention
Business Analysis In Agile – A Differentiated Narrative
Presented By: Praveen Kumar Benguluru
Associate Vice President – Business Solutions,
Scope International Private Ltd.

2. © 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

3. © 2014 BA Convention 3
Click to edit Master text styles
Click to edit header
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

4. © 2014 BA Convention 4
How Agile helps in addressing business and technology challenges
Understanding the need for Agile

5. © 2014 BA Convention 5
Click to edit Master text styles
Click to edit header
Business Challenges
Source: Open Compliance & Ethics Group

6. © 2014 BA Convention 6
Click to edit Master text styles
Click to edit header
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

7. © 2014 BA Convention 7
Click to edit Master text styles
Click to edit header
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

8. © 2014 BA Convention 8
How Business Analysis is Carried out in Agile World
Business Analysis In Agile Development

9. © 2014 BA Convention 9
Click to edit Master text styles
Click to edit header
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

10. © 2014 BA Convention 10
Click to edit Master text styles
Click to edit header
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.”

11. © 2014 BA Convention 11
Click to edit Master text styles
Click to edit header
Agile – Scrum Framework
Source: http://idimension.wordpress.com
Widely Used Framework

12. © 2014 BA Convention 12
Click to edit Master text styles
Click to edit header
Business Analysis In Agile
Solution Assessment & Validation
Functional Analysis
Creating Business Cases
Requirement Analysis & Management
Requirements Elicitation
HighLevel
Functional Architecture Functional Breakdown Structure
(FBS)
F1 F2 F3
Solution Assessment & Validation
Functional Analysis
Creating Business Cases
Requirement Analysis & Management
Requirements Elicitation
Detailed
User
Stories
I – Independent
N – Negotiable
V – Valuable
E – Estimable
S – Small
T – Testable
Solution Assessment
& Validation
Functional Analysis
Sprint
Functional Integration
F1 F2 F3
End Product

13. © 2014 BA Convention 13
Click to edit Master text styles
Click to edit header
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

14. © 2014 BA Convention 14
Click to edit Master text styles
Click to edit header
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.
Requirement Analysis &
Management
•Estimated volume of 10000 transactions / day converted from
branch to online @ savings of $5/ transactionCreating 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.
Solution Assessment &
Validation

15. © 2014 BA Convention 15
Click to edit Master text styles
Click to edit header
Funds Transfer – Functional Architecture
Source Systems
Bank Master
Data
Core Host
Systems
EDM
Payment
System
Rates System
TransfersBeneficiary
Management
Rules EngineLimits
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

16. © 2014 BA Convention 16
Click to edit Master text styles
Click to edit header
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
Priorities
Add
Bene
Delete
Bene Priorities
Booking History
Priorities
Authentic
ation Audit

17. © 2014 BA Convention 17
How can we bring a change
Our (BA) Role In Agile Implementation

18. © 2014 BA Convention 18
Click to edit Master text styles
Click to edit header
Identifying the Challenges
Organization Agile
Training &
Awareness
Industry

19. © 2014 BA Convention 19
Click to edit Master text styles
Click to edit header
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.

20. © 2014 BA Convention 20
Key Takeaways
Conclusion

21. © 2014 BA Convention 21
Click to edit Master text styles
Click to edit header
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

22. © 2014 BA Convention
Learn more. www.baconvention.com
Thank You!
Speaker Email:
Praveen.benguluru@gmail.com