From User Research to Product Backlog - Design Thinking in der Praxis

  • 1,356 views
Uploaded on

Presentation held for Software Engineering Association in Karlsruhe, Germany (7 March 2012) - drafted together with Jochen Guertler

Presentation held for Software Engineering Association in Karlsruhe, Germany (7 March 2012) - drafted together with Jochen Guertler

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,356
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. From User Research to Product Backlog“Design Thinking in der Praxis”Dr. Tobias Hildenbrand (SAP)VKSI Sneak Preview, 7 March 2012
  • 2. SAP„s “Lean Way”How Can Design Thinking Complement Lean Software Product Development?
  • 3. Some “Fast Facts” on SAP‟s Products© 2012 SAP AG. All rights reserved. 3
  • 4. Process-Wise, it has been a Long Journey…© 2012 SAP AG. All rights reserved. 4
  • 5. It„s about Scaling...© 2012 SAP AG. All rights reserved. 5
  • 6. Approach: From Lean Thinking to XP Practices... XP Concreteness Scrum Agile Lean Thinking Scope© 2012 SAP AG. All rights reserved. 6
  • 7. Agile Software Engineering Practices from XP "However, concrete software engineering techniques are among the key success factors in agile software projects" (Chow and Cao, 2008). Scrum Pair Refac- TDD Mocking Programming toring IntegContin Retro- Unit Clean A-TDD uous spectives Test Code ration Exploratory Team Automated Backlog Planning Testing Work UI Testing Estimation© 2012 SAP AG. All rights reserved. 7
  • 8. The Four Principles of a Lean Enterprise© 2012 SAP AG. All rights reserved. 8
  • 9. SAP‟s Lean Approach – Key PrinciplesSplit your organization –small, cross-functional, self-organizing Split your work – small list, rankedteams together with customer, effort relatively estimated $$$ $ Split time – fixed length iterations (1-4 weeks) deliver potentially shippable increments, fast feedback from customer April JanOptimize the release plan – update Continuously Improve –priorities in collaboration with the customer, based on retrospective after each iterationinsights gained by inspecting the release after eachiteration© 2012 SAP AG. All rights reserved. 9
  • 10. SAP‟s Lean Approach in a Nutshell Instead of a large group we have small teams spending a long time spending a short time building a big thing, building small things. …while integrating regularly to see the whole.© 2012 SAP AG. All rights reserved. 10
  • 11. Here comes Design ThinkingWhat is Design Thinking in the First Place?
  • 12. Design Thinking Follows a Basic Process© 2012 SAP AG. All rights reserved. 12
  • 13. Design Thinking is also about Iterations Solution Finding Problem Space© 2012 SAP AG. All rights reserved. 13
  • 14. It„s NOT just a Process Bringing together a good approach, with the right people, in the right environment.© 2012 SAP AG. All rights reserved. ©SAP AG 2010 | 14 14
  • 15. Design Thinking Value Proposition© 2012 SAP AG. All rights reserved. 15
  • 16. Design Thinking and Lean Can Complement Each Other Lean Thinking – Focus on Time-to-Market and Speed Desire SpeedDesign Thinking – Focus on Customer Value and Desire© 2012 SAP AG. All rights reserved. 16
  • 17. (Lean + Design) * Thinking = STOP TO THINK!Lean Thinking Stop to find out which development processes induce direct value Stop to eliminate waste Stop to continuously improve...Design Thinking Stop to observe the customer Stop to develop empathy Stop to ideate and restart…© 2012 SAP AG. All rights reserved. 17
  • 18. SAP‟s Sailing ProgramHow Can Both Thinking Schools be Combined and Applied in Practice?
  • 19. Design Challenge and Methodological ApproachChallenge: How might we provide software forsailors and coaches that helps them to performbetter and win at the Olympic Games 2012?First Goal: Develop product vision and backlog forsailor and coach solution based on user researchconducted at home and at actual venue (Kiel)Method: Design Thinking plus Lean and agilesoftware development practices at SAPTeam:TIP Innovation Center development team, UX andmobile experts, chief dev architect, mentors forDesign Thinking, LEAN, and agile methods (us)© 2012 SAP AG. All rights reserved. 19
  • 20. Sail Better Team Works in an „Open Space“ Environmentbased on ‚Office Space for Teams„ concept © 2012 SAP AG. All rights reserved. 20
  • 21. © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 21
  • 22. Our approach combines design thinking and lean/agile... LEAN & Agile Practices Phase 1: Phase 2: Phase 3 (ongoing): Research, Synthesis Development with Scrum incl. Continuous Envisioning  Vision Backlog Refinement („Grooming“) and & Trainings Refinement, Prototyping Sessions (Scrum Mode) Story Map & Backlog Elaboration 360° Research Kiel German World ... Olympic Games Week Championship Championship 2012 (venue: Travemuende) (venue: Perth) (venue: London)Design Thinking Methods© 2012 SAP AG. All rights reserved. 22
  • 23. © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 23
  • 24. Our Goal: Conduct 360° User Research and Understand... Some Facts & Figures...  15 interviews with various sailors, coaches, and other experts  Observation of race preparation at venue site  Immersion by actual sailing  Study of article and books  Sailing simulation games  Scanning of existing sailing content on web sites  ...© 2012 SAP AG. All rights reserved. 24
  • 25. The Development Team Spent 8 Days at Sailing Event© 2012 SAP AG. All rights reserved. 25
  • 26. © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 26
  • 27. Synthesis of Results © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 27
  • 28. Synthesis – „Story Telling“Goal: capture and channel experience,empathy, and spirit from user research atKiel Week in order to develop productvision, personas, and first prototypesApproach: actual statement on „post-its“© 2012 SAP AG. All rights reserved. 28
  • 29. Collaborative Story Telling Led to a First Collection ofResearch Findings...© 2012 SAP AG. All rights reserved. 29
  • 30. Silent Clustering Brought Up 19 Categories...© 2012 SAP AG. All rights reserved. 30
  • 31. Based on our Findings, We Developed Personas pic© 2012 SAP AG. All rights reserved. 31
  • 32. © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 32
  • 33. ...And Conducted Initial Ideation & Prototyping© 2012 SAP AG. All rights reserved. 33
  • 34. © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 34
  • 35. Development of an Overall Product Vision© 2012 SAP AG. All rights reserved. 35
  • 36. Towards a Backlog: Map for Sailors & Coaches© 2012 SAP AG. All rights reserved. 36
  • 37. User Story Example from Story Map [6.1.01] As TINA I Iwant to know the [6.1.01] As TINA Iwant to know the [6.1.01] As TINA Iwant to knowan [6.1.01] As TINA Iwant to knowthe latest weather /TINA forecasts knowthe latest weather /wind forecasts(in an [6.1.01] As /wind want to (in an the easy toweather /windalong with (inalong latest weather windforecasts an an latest read format) along with (in latesttoread format) forecasts an easy toweather & wind forecasts an easy toread format) along with an with an read format) along besttrim easy (automated)(automated) proposal for thewith proposal for the best trim (automated) proposal for the best trim (automated) proposal for the best settings, so that I Ihavesobest-guesstrim (automated)settings, for the proposal settings,trimthat Ihaveaaathat I have a best so that have best-guess settings, sosupporthave abest-guess settings, sosupportfor support for my best-guessthat I formybest-guess decision decision mytrim decision support for mytrim decision support for mytrim decision trim trim settings prior to the race…© 2012 SAP AG. All rights reserved. 37
  • 38. © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 38
  • 39. Results of Post-Kiel Workshop  We had a clear product vision and backlog – aligned with customer  The team decided on a working model (Scrum, 3-week sprints, etc.)  Story mapping helps us to see the whole and continuously refine it  Personas keep us focussed on the users and facilitate communication within the team  Paper prototypes and other cheap artifacts enable fast feedback from customers and colleagues © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 39
  • 40. © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 40
  • 41. First High-Fidelity Mock-Ups in Sprint 2© 2012 SAP AG. All rights reserved. 41
  • 42. © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 42
  • 43. Usable Software with Latest Technology from Sprint 3…© 2012 SAP AG. All rights reserved. 43
  • 44. Feedback from the Sail Better Team (Quotes) “What? We “We had no clue only do design at the beginning thinking at the “Our story map and were ready beginning – helped me to to develop after let’s do it each communicate Kiel...” (SM) sprint!” (Dev) with our customers” (PO) “Having the team “What the team built write the user goes way beyond our stories based on own thinking and will Design Thinking improve our preparation was a tremendous for the Olympic Games boost!” (PO) 2012.” (STG)© 2012 SAP AG. All rights reserved. 44
  • 45. © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 45
  • 46. Conclusions and Roadmap “Design Thinking and Lean Development helped us creating and delivering products that customers love” Both “thinking schools” go hand in hand very well Design Thinking rather focuses on building the right products, i.e. generating desire on the customers’ side Lean Thinking, including agile practices, tells us how to build the product right, i.e. how to achieve speed at scale Sail Better shipped a first version of the software for the German sailing championships in Travemuende (Sept 2011) Upcoming events: Olympic Games 2012 and 2016© 2012 SAP AG. All rights reserved. 46
  • 47. © Tobias Hildenbrand© 2012 SAP AG. All rights reserved. 47
  • 48. Thank You – Any Questions?Contact informationDr. Tobias HildenbrandDevelopment Project Consultant/Continuous Improvement ExpertSAP CPO Lean CenterWalldorf, Germanytobias.hildenbrand@sap.com