The document discusses the importance of 'design thinking' and agile development in creating innovative software at SAP, emphasizing employee motivation and creativity. It highlights the shift from traditional waterfall methods to agile practices, which enhance reliability, efficiency, and customer value. Key takeaways include the necessity for empathy towards end users, iterative design processes, and the role of cross-functional teams in fostering innovation.

1. DR. TOBIAS HILDENBRAND | SAP AG | 27. MÄRZ 2014
DAS RICHTIGE RICHTIG MACHEN
”DESIGN THINKING” UND AGILE ENTWICKLUNG
ALS SCHLÜSSEL ZU INNOVATIVER SOFTWARE

2. © SAP 2014 | 2
“Ich wollte Mitarbeiter so motivieren, dass sie mehr leisten
als der Durchschnitt. Freie Entfaltung und Kreativität, ohne
bürokratische Zwänge und Regeln. Dazu passt auch keine
Stempeluhr, die mir immer zuwider war.”
Dietmar Hopp (one of the founders of SAP)

3. © SAP 2014 | 3
WHAT DOES SAP
DO TODAY?

4. © SAP 2014 | 4 …A LOT MORE THAN 40 YEARS AGO WHEN WE STARTED
Cloud
HANA
Mobile
70k
Analytics
Applications

5. © SAP 2014 | 5
…AND WHERE DO
WE COME FROM?

6. © SAP 2014 | 6 40 YEARS OF SAP, ALMOST 40 YEARS OF WATERFALL
Source: SAP

7. © SAP 2014 | 7
AGILE = “QUICK, BUT WELL-COORDINATED”

8. © SAP 2014 | 8 TODAY, WE MANAGE OUR REQUIREMENTS THE AGILE WAY
fixed
estimated
Requirements
Requirements
Resources Release Date
Resources Release Date
Plan-driven (traditional) Customer value-driven (agile)

9. © SAP 2014 | 9 OUR DELIVERY IS MORE RELIABLE AND EFFICIENT TODAY
Chief Product
team
Release
Backlog
Sprint
Backlog
Product
Backlog
Scrum
Teams

10. © SAP 2014 | 10 SCRUM REDUCES PRODUCT RISKS DRAMATICALLY
Conduct regular
Retrospectives
Split organization
into teams
Split work
Split time
Deliver more
frequently
Risk
Risk

11. © SAP 2014 | 11
WHAT DID WE
LEARN FROM LEAN?

12. © SAP 2014 | 12 DELIVER MORE RELIABLY AND PREDICTABLY

13. © SAP 2014 | 13
…BUT WHAT ABOUT
INNOVATION?

14. © 2012 SAP AG. All rights reserved. 14© SAP 2014 | 14
Desirability
Feasibility
Viability
ENTERPRISE SOFTWARE PRODUCT INNOVATION

15. “Building something nobody
wants is the ultimate form
of waste.” – Eric Ries
© SAP 2014 | 15

16. © 2012 SAP AG. All rights reserved. 16© SAP 2014 | 16
?
SO, YOU START WITH YOUR END USERS

17. © 2012 SAP AG. All rights reserved. 17© SAP 2014 | 17 …AND PUTTING YOURSELVES IN THEIR SHOES

18. © SAP 2014 | 18
‘‘A DEVELOPER NEEDS TO BE CURIOUS AND
ALSO DEVELOP EMPATHY FOR END USERS“
Source: interview with SAP co-founder Hasso Plattner (2012)

19. © 2012 SAP AG. All rights reserved. 19© SAP 2014 | 19
Create
Choices
Make
Choices
…WITH A DESIGNER‘S APPROACH AND MINDSET
We don‘t
know yet!
Iterate

20. © 2012 SAP AG. All rights reserved. 20© SAP 2014 | 20 YOU NEED A DIVERSE, MULTI-DISCIPLINARY TEAM

21. “There Are No Facts
Inside Your Building,
So Get Outside.”
– Steve Blank
© SAP 2014 | 21

22. © SAP 2014 | 22
…AND WHAT ABOUT
VIABILITY?

23. © SAP 2014 | 23 UNDERNEATH AN INNOVATION, THERE IS A BUSINESS MODEL

24. © SAP 2014 | 25
CONCLUSION

25. © SAP 2014 | 26 DESIGN THINKING & AGILE DEVELOPMENT SHARE VALUES
Short Iterations Incremental
Delivery
Small Cross-Functional Teams
Focus on
Customer
Value
Fast Feedback
Continuous
Improvement

26. © 2012 SAP AG. All rights reserved. 27© SAP 2014 | 27
Innovation and Effectiveness,
i.e. building the right things
 First-hand empathy for end users
 Creative solution finding and ideation
 Validation of assumptions and
early prototypes with end users
Efficiciency and Delivery
i.e. building things right
 Process framework and
engineering practices
 Agile planning and estimation
 Continuous improvement
COMBINING SOFTWARE DESIGN AND DEVELOPMENT
= Building the right things right

27. © SAP 2014 | 28 OUTLOOK: CUSTOMER-CENTERED PRODUCT INNOVATION
Diverse
Product
Teams
Design
Thinking &
Customer
Co-Innovation
Agile Software
Engineering
Business Model Development

28. Thank You