be inspired by design thinking… - sap

Be Inspired by Design Thinking…André Stern, Ariane Skutela, Tobias HildenbrandWalldorf, 4 April 2013

© 2013 SAP AG. All rights reserved. 2

The development for the Deployment Cockpit became a DesignThinking project because the team wanted it!

Setup: Entire scrum team plus guests, all based in WDF; late nomination and member of DT initiativeWave 2

Order: Create a deployment cockpit

Timeline: February – September 2012 (details next slide)

Result: A tool to enable project teams, including partners and customers, to easily understand andcollaboratively manage the execution of their tasks when deploying solution packages at customersites heavily appreciated by our customers.

© 2013 SAP AG. All rights reserved. 3

Parallel architecture alignments and partly implementation of basic back bone needs plus support of other dev activities

• Creation of SAP ID infrastructure, login- and homepage of RDC• WBS infrastructure• Interface alignments…

MarchFebruary

CW 06 CW 10 CW 11 CW 12 CW 13 CW 14 CW 15 CW 16

I. Understand

• Request Interviewees• Plan high level DT activities• Problem definition statement• Plan DT activities• Recruit participants, get budget, etc.• High level storyboard• Sign-Off by project sponsor

CW 17

April

III. Synthesis

• Prepare findings for synthesis• Storytelling workshop• Clustering results (Tasks, requirements,

environment, personas, etc.) workshop• Capture synthesis results (task flows,

requirements, etc.)• Create personas

IV. Ideation

• Several half and/or one day workshops• Come up with product concept/ ideas

II. Research

• Write interview guide• Conduct interviews• Prepare and conduct focus group(s)• Collect interview results (Brown paper, notes)

and material

Synthesisresults

May

• Storyboard workshop Storyboard evaluation• Write user stories, Create 1st version paper user story map• Define UI architecture• Create wireframes Paper prototype testing session• Create visual designs Gain end user and stakeholder feedback• Create interactive prototype Usability testing

V & VI. Prototyping + validation

ScopeChange

August

CW 31 CW 33 CW 34CW 32

Go LiveV 1.0

• Security Audit• Testing and bug fixing• Usability tests and last minute changes (usability

improvements)

VII. 2 sprints testing and bug fixing

Standard Approach

CW 18 CW 19 CW 20 CW 21 CW 35

• Finalizing user story map in LEAN manner• Description of requirements for Backlog (technical requirements, frontend requirements• Test case description• Scrum development activities (6 sprints)• Minor scope changes

Milestone TodayProject phase Critical MilestonesCritical activitiesIteration SprintLegend:

Prototype andScope Sign off

VII. 6 sprints implementation

RETROSPECTIVE – actual timeline with many parallel activities

© 2013 SAP AG. All rights reserved. 4

AGENDA

Why Design Thinking?

How to Apply Design Thinking?

Conclusion

WHY DESIGN THINKING?

© 2013 SAP AG. All rights reserved. 6

Design Thinking

HOW TO ACHIEVE INNOVATION?

© 2013 SAP AG. All rights reserved. 7

“What innovation boils down tois one per cent inspiration andninety-nine per centperspiration.” – Thomas Edison

© 2013 SAP AG. All rights reserved. 8

Inspiration and Ideation Implementation

THERE’S NO INNOVATION WITHOUT IMPLEMENTATION!

HOW TO APPLY DESIGN THINKING?

© 2013 SAP AG. All rights reserved. 10

DESIGN THINKING

© SAP 2013 | 10

Diverse PEOPLE + Creative SPACE + Iterative APPROACH

Diverse People Iterative ApproachCreative Space

© 2013 SAP AG. All rights reserved. 11

© 2013 SAP AG. All rights reserved. 12© SAP 2012 | 12

Diverse PEOPLE

© 2013 SAP AG. All rights reserved. 13© SAP 2012 | 13

Creative SPACE

© 2013 SAP AG. All rights reserved. 14

Think like DESIGNERS and Solve the Problem as a TEAM

PROBLEM SPACE SOLUTION SPACE

© 2013 SAP AG. All rights reserved. 15© SAP 2013 | 15

iterative APPROACH: COMBINING DESIGN THINKING & SCRUM

© 2013 SAP AG. All rights reserved. 16

UNDERSTAND

© 2013 SAP AG. All rights reserved. 17

UNDERSTAND – Try to understand the problem before you start.

© 2013 SAP AG. All rights reserved. 18

OBSERVE

© 2013 SAP AG. All rights reserved. 19

OBSERVE – Try to dive into your users’ problem space…

© 2013 SAP AG. All rights reserved. 20

DEFINE POINT-OF-VIEW

© 2013 SAP AG. All rights reserved. 21

“How might we help Marie and her team to efficiently and collaborativelyimplement a rapid deployment solution on- and off shore?”

DEFINE POINT-OF-VIEW – Focus on concrete end user needs.

© 2013 SAP AG. All rights reserved. 22

IDEATE

© 2013 SAP AG. All rights reserved. 23

IDEATE – Go for many ideas addressing single end user needs.

© 2013 SAP AG. All rights reserved. 24

PROTOTYPE

© 2013 SAP AG. All rights reserved. 25

PROTOTYPE – Make your ideas tangible and feedback-ready.

© 2013 SAP AG. All rights reserved. 26

TEST

© 2013 SAP AG. All rights reserved. 27

TEST – Go back to your end users and validate the prototypes.

© 2013 SAP AG. All rights reserved. 28

IMPLEMENT

© 2013 SAP AG. All rights reserved. 29

IMPLEMENT – User story maps can bridge the gap to development.

CONCLUSION

© 2013 SAP AG. All rights reserved. 31

ProductVision

Product Backlog

Understandthe Problem End User Research

Storytelling& Synthesis

Define Personas& Point-of-View

Testing withEnd Users

User Story MappingImplementation

SprintBacklog

FROM DESIGN THINKING TO LEAN/AGILE DEVELOPMENT

© 2013 SAP AG. All rights reserved. 32

Summary and Conclusion – Top 3 Learnings

Design Thinking is not rocket science!

It not only helps to create right products,it also will build your team!

Eventually it makes SAP working daysmore enjoyable, creates a collaborativeenvironment and simplifies learningabout end users!

Thank you

Tobias HildenbrandSAP CPO Software Engineeringtobias.hildenbrand@sap.com

Contact information:

Ariane Skutela & André SternDT Coaches @ Packaging Frameworkwww.rapid.sap.comTeam Blog / Flipbook

© 2013 SAP AG. All rights reserved. 34

© 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth inthe express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.