Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
How Can You Keep The CustomerInputs Flowing, The TeamsRunning And Still KnowWhere You Stand?Naama Gafni Lifshitz,SAP Labs IL
Introduction    SAP Scrum and Lean implementation    Multiple teams cross locations    Taking the methodology into daily  ...
Product Owner Role     Customers                          Product       Users                                         Team...
Inputs FlowProcesses and PO Deliverables                                       User            Release   Design           ...
The Traditional Backlog    Long    Missing big picture    Is not scenario oriented    Minimal scope    Communication tool?...
User Story What?!                                 A 2 dimensional map of theWhat                             product, driv...
User Story Map                                      Usage Sequence = Scenario                                      Persona...
User Story Map© 2012 SAP AG. All rights reserved.   8
User Story Map - Example                                      Setup    Request             Approve                        ...
User Story Map Benefits    Improves backlog quality    Focus on end-to-end customer Scenario    Easy to create    Visualiz...
Inputs FlowProcesses and PO Deliverables                                       User      Release   Design                 ...
Defining a Ready CriteriaREADY is when the team says: “Ah, we get it”.Must have                             Desirable   “W...
The Planning Problem    Coordinating user stories across multiple    teams is hard    PO is overloaded and needs to prepar...
Pre-Planning Per Team– NOT A One Man Show                                                          PO                     ...
Pre-Planning ProcessDevelopment Execution                                   Sprint 1   Sprint 2 Sprint 3 Sprint 4Sprint 1 ...
Pre-Planning Process Phases                                                  Phase 2Planning                              ...
Pre-Planning Benefits    Easy to establish    Shortens planning day    Increases team effectiveness during sprint    execu...
The Product Team          Chief PO                         Team POsPMO                              UX Lead   Chief Archit...
Product Team           Pre-Planning Teams
Thank you!Contact Information:Naama Gafni LifshitzLean and Scrum Mentor,SAP Labs ILNaama.Gafni.Lifshitz@sap.com
Upcoming SlideShare
Loading in …5
×

How can you keep the customer inputs flowing, the teams running and still know where you stand?

1,535 views

Published on

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-NaamaGafniLifshitz

Published in: Technology, Sports
  • Be the first to comment

How can you keep the customer inputs flowing, the teams running and still know where you stand?

  1. 1. How Can You Keep The CustomerInputs Flowing, The TeamsRunning And Still KnowWhere You Stand?Naama Gafni Lifshitz,SAP Labs IL
  2. 2. Introduction SAP Scrum and Lean implementation Multiple teams cross locations Taking the methodology into daily practice© 2012 SAP AG. All rights reserved. 2
  3. 3. Product Owner Role Customers Product Users Teams Stakeholders Owner Product Analysis & Execution Inputs Insights© 2012 SAP AG. All rights reserved. 3
  4. 4. Inputs FlowProcesses and PO Deliverables User Release Design Story Backlog Execution Thinking Mapping GroomingVision Scenario Estimated Sprint backlogPersonas User stories User stories RankingPoC HL Priorities PrioritiesMockup Release plan Completed stories© 2012 SAP AG. All rights reserved. 4
  5. 5. The Traditional Backlog Long Missing big picture Is not scenario oriented Minimal scope Communication tool?!© 2012 SAP AG. All rights reserved. 5
  6. 6. User Story What?! A 2 dimensional map of theWhat product, driven by a user scenario and ordered by prioritiesWhen 1-2 days at the beginning of the release planningWho Done by a group multidisciplinary team members© 2012 SAP AG. All rights reserved. 6
  7. 7. User Story Map Usage Sequence = Scenario Personas Usage Sequence High Level User Stories© 2012 SAP AG. All rights reserved. 7
  8. 8. User Story Map© 2012 SAP AG. All rights reserved. 8
  9. 9. User Story Map - Example Setup Request Approve Users Review Approve Reject Admin mgmt. request request request Create Submit GetEmployee status request request Add Via Via Via user Web Web Web Edit Via Via Via Via Via user Mobile Mobile Mobile Mobile Mobile Remove Via Via Via Via user Email Email Web Web© 2012 SAP AG. All rights reserved. 9
  10. 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 progressSource: Jeff Patton www.AgileProductDesign.com© 2012 SAP AG. All rights reserved. 10
  11. 11. Inputs FlowProcesses and PO Deliverables User Release Design Story Backlog Execution Thinking Mapping Grooming Sprint backlog Ranking© 2012 SAP AG. All rights reserved. 11
  12. 12. Defining a Ready CriteriaREADY is when the team says: “Ah, we get it”.Must have Desirable “What” and “Why” are Mockups ready clear Testing strategy User stories are reviewed Reviewed strings and fit in sprint Dependencies are identified User stories are ranked© 2011 SAP AG. All rights reserved. 12
  13. 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. 13
  14. 14. Pre-Planning Per Team– NOT A One Man Show PO UX KS PO Developer/ Architect Scrum Master© 2012 SAP AG. All rights reserved. 14
  15. 15. Pre-Planning ProcessDevelopment Execution Sprint 1 Sprint 2 Sprint 3 Sprint 4Sprint 1 Sprint 2 Sprint 3 Sprint 4Pre-Planning © 2012 SAP AG. All rights reserved. 15
  16. 16. Pre-Planning Process Phases Phase 2Planning Planning Phase 1 Phase 3 Detailed Day Day Scoping Finalization Definition POs POs POs POs POs POs Sync Sync Sync Sync Sync Sync Product Status Review Sniffing © 2011 SAP AG. All rights reserved. 16
  17. 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© 2011 SAP AG. All rights reserved. 17
  18. 18. The Product Team Chief PO Team POsPMO UX Lead Chief Architect Quality Lead© 2012 SAP AG. All rights reserved. 18
  19. 19. Product Team Pre-Planning Teams
  20. 20. Thank you!Contact Information:Naama Gafni LifshitzLean and Scrum Mentor,SAP Labs ILNaama.Gafni.Lifshitz@sap.com

×