how can you keep the customer inputs flowing, the teams running and still know where you stand?
DESCRIPTION
How can you keep the customer inputs flowing, the teams running and still know where you stand? By Naama Gafni Lifshitz @ AgileIL12 http://agilesparks.com/CustomerFlowing-NaamaGafniLifshitzTRANSCRIPT
How Can You Keep The Customer
Inputs Flowing, The Teams
Running And Still Know
Where You Stand?
Naama Gafni Lifshitz,
SAP Labs IL
© 2012 SAP AG. All rights reserved. 2
Introduction
SAP Scrum and Lean implementation
Multiple teams cross locations
Taking the methodology into daily
practice
© 2012 SAP AG. All rights reserved. 3
Customers Users
Stakeholders
Product
Inputs
Product Owner
Analysis &
Insights
Teams
Execution
Product Owner Role
© 2012 SAP AG. All rights reserved. 4
Inputs Flow
Processes and PO Deliverables
Design
Thinking
User
Story
Mapping
Release
Backlog
Grooming
Execution
Vision
Personas
PoC
Mockup
Scenario
User stories
HL Priorities
Release plan
Sprint backlog
Ranking Estimated
User stories
Priorities
Completed
stories
© 2012 SAP AG. All rights reserved. 5
The Traditional Backlog
Long
Missing big picture
Is not scenario oriented
Minimal scope
Communication tool?!
© 2012 SAP AG. All rights reserved. 6
User Story What?!
A 2 dimensional map of the
product, driven by a user scenario
and ordered by priorities
1-2 days at the beginning of the
release planning
Done by a group multidisciplinary
team members
What
When
Who
© 2012 SAP AG. All rights reserved. 7
User Story Map
Usage Sequence = Scenario
Personas Usage Sequence
High Level User Stories
© 2012 SAP AG. All rights reserved. 8
User Story Map
© 2012 SAP AG. All rights reserved. 9
User Story Map - Example
Setup Request Approve
Admin Users
mgmt. Review
request
Approve
request Reject
request
Via
Web
Via
Mobile Via
Mobile
Via
Web
Add
user
Edit
user
Remove
user
Via
Web
Via
Mobile
Via
Via
Web
Via
Mobile
Via
Employee Create
request
Submit
request
Get
status
Via
Mobile
Via
Web
© 2012 SAP AG. All rights reserved. 10
User Story Map Benefits
Improves backlog quality
Focus on end-to-end customer Scenario
Easy to create
Visualizes the release backlog
Validation with customers
Enables Big picture communication with team
Can be used to track progress
Source: Jeff Patton www.AgileProductDesign.com
© 2012 SAP AG. All rights reserved. 11
Inputs Flow
Processes and PO Deliverables
Design
Thinking
User
Story
Mapping
Release
Backlog
Grooming
Execution
Sprint backlog
Ranking
© 2011 SAP AG. All rights reserved. 12
Defining a Ready Criteria
Must have
“What” and “Why” are
clear
User stories are reviewed
and fit in sprint
Dependencies are identified
User stories are ranked
Desirable
Mockups ready
Testing strategy
Reviewed strings
READY is when the team says: “Ah, we get it”.
© 2012 SAP AG. All rights reserved. 13
The Planning Problem
Coordinating user stories across multiple
teams is hard
PO is overloaded and needs to prepare for planning day
User stories not always accepted by the teams
Planning meetings can be long and
ineffective
© 2012 SAP AG. All rights reserved. 14
Pre-Planning Per Team
– NOT A One Man Show
PO
UX
Architect
KS
Developer/
Scrum Master
PO
© 2012 SAP AG. All rights reserved. 15
Pre-Planning Process
Sprint 1
Development Execution
Pre-Planning
Sprint 2 Sprint 3 Sprint 4
Sprint 1 Sprint 2 Sprint 3 Sprint 4
© 2011 SAP AG. All rights reserved. 16
Pre-Planning Process Phases
Phase 1
Scoping
Phase 2
Detailed
Definition
Phase 3
Finalization
Planning
Day
POs
Sync
POs
Sync
POs
Sync
POs
Sync
POs
Sync
POs
Sync
Planning
Day
Product Status Review Sniffing
© 2011 SAP AG. All rights reserved. 17
Pre-Planning Benefits
Easy to establish
Shortens planning day
Increases team effectiveness during sprint execution
Early engagement of multidisciplinary team
Risks emerge early
Maintains the flow of the team activities
Gives structure for multiple team planning
© 2012 SAP AG. All rights reserved. 18
The Product Team
Team POs
UX Lead Chief Architect Quality Lead
Chief PO
PMO
Product Team
Pre-Planning Teams
Thank you! Contact Information:
Naama Gafni Lifshitz
Lean and Scrum Mentor,
SAP Labs IL