practicing agile as a ba - ba convention · 2015-08-02 · scrum master •proxy po stakeholders at...
TRANSCRIPT
© 2014 BA Convention
Practicing Agile As a BA
Presented by: Jagruti Shah Associate Business Consultant Mastek Ltd
© 2014 BA Convention 2
Click to edit Master text styles
Click to edit header
Role of BA in Agile
• What is Agile?
• What does Agile mean for a Business Analyst?
• What does Business Analyst aim for?
• How to achieve 3 C’s (Card, Conversation & Confirmation)?
© 2014 BA Convention 3
Click to edit Master text styles
Click to edit header
Key Takeaways.....
• Agile Atmosphere
• Grooming product backlog
• INVEST understood and practiced
• Lean UX collaborative designs with UED
• Encourage collaboration
© 2014 BA Convention 4
Click to edit Master text styles
Click to edit header
Project Background
About Identity & Access Management (IAM) with one of the
UK clients in Health care domain
A bespoke development covering
User Registration & Access Management Services
Credential Management Services
Self-service Applications
Audit & Reporting Services
© 2014 BA Convention 5
Click to edit Master text styles
Click to edit header
Over 875,000 Registered users
670,000 Users with smartcards
400,000 Digital signature based authentications a
day
Registered users across 20,000 organizations
70,000 concurrent users
500 New smartcards per day
2,000 Smartcard renewals per day
About IAM
EFFORTS – 600MM
DURATION – 18M
© 2014 BA Convention 6
Click to edit Master text styles
Click to edit header
Business Needs
3.
Build Reusable Platform
Across Government Projects
© 2014 BA Convention 7
Click to edit Master text styles
Click to edit header
Project Challenges
Team of 50 -
most of them new to agile
Aggressive timelines
with 4 releases planned
Technically challenging
due to use of open source
Zero downtime to migrate
from old to new system
Integration with
smartcard readers & printers
Dependency of
two more applications on it
© 2014 BA Convention 8
Click to edit Master text styles
Click to edit header
My Agile Journey
On Board
Foundation
Detailing User Story
© 2014 BA Convention 9
Click to edit Master text styles
Click to edit header
On Board
AGILE ATMOSPHERE
© 2014 BA Convention 10
Click to edit Master text styles
Click to edit header
- Forming the Agile Atmosphere
White Board
Release Wall Projector
Scrum Board
Open Desk
Avatar
The Room
© 2014 BA Convention 11
Click to edit Master text styles
Click to edit header
Agile Atmosphere - Benefits
• Focused teams
• Continuous & quick collaboration
• Teams with transparency & visibility
• Facilitating & preparing the team to perform their tasks
effectively in Agile
© 2014 BA Convention 12
Click to edit Master text styles
Click to edit header
Foundation
GROOMING
PRODUCT BACKLOG
© 2014 BA Convention 13
Click to edit Master text styles
Click to edit header
Product Backlog – Initial Structure & Challenges
Initial Product Backlog
Multiple BA’s &
multiple product
backlogs
Technical
complexity &
team confidence
not known
Non-
functional
requirements
missing
Dependencies
not clear
Development
team’s
involvement
missing
© 2014 BA Convention 14
Click to edit Master text styles
Click to edit header
Product Backlog - Our Approach
Story Gathering Workshop
Before After
Added Fields
© 2014 BA Convention 15
Click to edit Master text styles
Click to edit header
Value Effort Map (VEM)
© 2014 BA Convention 16
Click to edit Master text styles
Click to edit header
Product Backlog - Benefits
• Identification of
− Dependency
− Technical complexity & Team confidence
− Spike stories, UI stories
− Non-functional stories
• Single & DEEP product backlog
• Transparency & visibility within the team
• Simplify the activity of planning & prioritization
© 2014 BA Convention 17
Click to edit Master text styles
Click to edit header
Detailing a User Story
‘INVEST’
UNDERSTOOD
&
PRACTICED
© 2014 BA Convention 18
Click to edit Master text styles
Click to edit header
• Time-boxing
• Definition of done
• Collaborative design
/grooming sessions
• Design review
workshops with users
• Using white board
extensively
• Preparing user
journeys, portlets.
• Limited acceptance
criteria
• Focus more on
conversation
• Slicing & dicing
• Fringe cases with
PO's agreement
Over-described
user stories Not enough
backlog reserve
User Stories – Challenges v/s Approach
Design
change
UX behavior to be
aligned with user
story • Early grooming
• BA-UED
Pairing
© 2014 BA Convention 19
Click to edit Master text styles
Click to edit header
User Stories - Benefits
• Quality user stories with better designs
• Enough backlog reserve
• Engaging end users, development team
• Smart team with more conversation & ownership
© 2014 BA Convention 20
Click to edit Master text styles
Click to edit header
Detailing a User Story
LEAN UX
COLLABORATIVE DESIGN
WITH UED
© 2014 BA Convention 21
Click to edit Master text styles
Click to edit header
Discrepancy
between
wireframe &
criteria
Align UX behavior
with user story
Requirement Force 5 -
3 Pairs of BA-UED +
2 UI developers -
working for 4 scrum
teams
• UX war room
• Central repository for
business rules, validations,
error messages
• Requirement team meeting
Design
dependency
BA-UED Pairing – Challenges v/s Approaches
Multiple BA-UED
pairs
• Continuous
collaboration
• Support teams
during development
• Peer/PO reviews
• Exploratory testing
• Collaborative design
sessions using white
board
© 2014 BA Convention 22
Click to edit Master text styles
Click to edit header
BA-UED Pairing – Benefits
• Better design solutions
• Central repository for UX artifacts
• Shared responsibility
• Splitting functional & non-functional requirements
• Ensuring quality delivery
Note:- This technique is only for projects having user interface.
© 2014 BA Convention 23
Click to edit Master text styles
Click to edit header
UX War Room
UX War Room Living Style Guide
© 2014 BA Convention 24
Click to edit Master text styles
Click to edit header
Collaboration
ENCOURAGE COLLABORATION
© 2014 BA Convention 25
Click to edit Master text styles
Click to edit header
Collaboration with
• Relevant discussion
points
• Time-boxing
Lengthy/unwanted
discussion in Agile
ceremonies
Collaboration – Challenges v/s Approaches
• Following
‘HEARTBEAT’
• Ensured availability
with the help of
scrum master
• Proxy PO
Stakeholders
at different
location
Unavailability
of important
stakeholders Hesitation to
approach
POs/SMEs
• Culture with no
hierarchy
• Discouraging
emails
• Continuous
conversation
• Take a photo &
• Collaboration
using tools
© 2014 BA Convention 26
Click to edit Master text styles
Click to edit header
Collaboration – Benefits
• Building shared understanding
• DEEP product backlog
• INVEST user stories
• Better design approaches
• Leading to fast development & quality delivery
© 2014 BA Convention 27
Click to edit Master text styles
Click to edit header
• More than 60000 connection established using
smartcards on 1st day of Go-live
• Connections with Zero failures
• Printing time reduced by 75%
Realising Success..Performance...Usability...
“Amazed
by
Speed
&
Simplicity”
Testimonial
© 2014 BA Convention 28
Click to edit Master text styles
Click to edit header
Key Takeaways
Agile Atmosphere
Grooming Product Backlog
INVEST Understood & Practiced
Lean UX Collaborative Designs with
UED
Encourage Collaboration
© 2014 BA Convention
Learn more. www.baconvention.com
© 2014 BA Convention
Learn more. www.baconvention.com
Thank You!
Speaker : Jagruti Shah Email ID : [email protected]