Accelerating Agile by Adding Business Analysis
25
-
Upload
iiba-uk-chapter -
Category
Business
-
view
550 -
download
1
Transcript of Accelerating Agile by Adding Business Analysis
https://www.slalom.com/
www.RylandLeyton.com
www.Amazon.com
A Local Partner with Global Scale
A business and technology consulting firm
with more than 3,400 consultants across
17 offices in North America and London.
Slalom Consulting 2016
We design, build, and implement
strategies and systems to help
our clients solve their most
critical business challenges.
Our Offerings
•
•
Taken from The Agile Extension to the BABOK Guide, page 9.TEAM COMPOSITION
Product Owner 1
Scrum Master / Iteration Manager 1
Developer Disciplines, Designers
(SE, UIE, DevOps, DBE, UX)
4-8
Quality Analyst 1-2
TOTAL 7-12
Taken from The Agile Extension to the BABOK Guide, page 10.
Scrum Master
Product Owner Dev Team/Tech Lead
OVERALL:
• Maintains a clean and consistent supply of cards.
• Improves velocity through quality & prep work.
• Watches out for business impacts to the enterprise.
FOR THE PRODUCT OWNER:
• Serves as proxy PO. (Not full substitute!)
• Provides enterprise-level thinking & analysis.
• Writes stories with quality.
• Guides decomposition & prioritization.
• Coordinates with other disciplines (UX, copy, etc.)
FOR THE SCRUM MASTER:
• Maintains the analysis wall.
• Owns ensuring a clean flow of work to team.
FOR THE TECH LEAD & DEV TEAM:
• Preserves TL/team time & focus.
• Durable partner for the team.
• Time/availability
• Analysis skill
• Agile skill
• Cards/Decomposition
• Analysis skill
• Focused on dev team
• Not responsible beyond Agile cycles
• Non-technical analysis
• Dev focus only
CHALLENGES
Business Analyst neatly fills the
existing gaps in the Agile approach.
Number of developers 6developers
Time per developer per week saved
(Rework, consultation, etc.) 2hours
Weeks in a year 52weeks in a year
TOTAL 624hours in a year
Equivalent FTE based on 32H 0.38FTE
Assume you get 10% more useful
software than previously developed
Number of developers 6developers
Dev hours per week 32 hours
Weeks in a year 52 weeks in a year
Total hours 9984 hours in a year
Shift in value of delivered stories by
better analysis 10% more value
IMPROVEMENT 998 hours in a year
Equivalent FTE based on 32H 0.60 FTE
Assume you get 10% more useful QA
work than previously performed
Number of QA 2Quality analysts
QA hours per week 32 hours
Weeks in a year 52 weeks in a year
Total hours 3328 hours in a year
Shift in value of delivered stories by
better analysis 10% cleaner QA effort
IMPROVEMENT 333 hours in a year
Equivalent FTE based on 32H 0.20 FTE
Assume you get 10% better Product
Management work & organizational
benefit from analysis activities.
Number of product owners 1 Product owner
PO hours per week 32 hours
Weeks in a year 52 weeks in a year
Total hours 1664 hours in a year
Shift in value of delivered stories by
better analysis 10% more value
IMPROVEMENT 166 hours in a year
Equivalent FTE based on 32H 0.10 FTE
16
TELL THEM:
• What you’re good at
(and possibly, not good at).
• How you like to communicate
(written/verbal, bullets or
details).
• Anything on which you’re
particularly looking forward to
working collaboratively.
ASK THEM:
• What they’re good at.
• How they like to communicate
(written/verbal, bullets or
details).
• If there is anything on which
they would like help.
• If they have any concerns in
general or in specific about the
project or effort.
Here are some tasks & skills that the BA can either own by virtue of training
or can take on as a “lift” from another team member:
25
www.RylandLeyton.com
www.Slalom.com
