The document discusses how design thinking and scrum can be combined for product development. It proposes that the design thinking process can be used to generate product backlog items for scrum, with users' needs and proposed solutions identified through design thinking activities like empathy interviews and prototyping. The document outlines one approach where design thinking teams focus on understanding user needs and developing prototypes, while scrum teams work on building solutions. It suggests the teams could be interdisciplinary and that the product owner communicates between the teams.

1. *interactive cologne 2013
DESIGN THINKING &
AGILE DEVELOPMENT*
W. Alex Jansen
alex@wajansen.co
@phaoust

2. WHO?
consultant / trainer for lean, agile,
business modelling
degrees in computer science
and music
experience in multiple industries

3. FOUNDER
1st at age 18, followed by more, IT
and others
Current: Materials for Scrum,
Design Thinking, and Business
Modelling

4. WHAT IS THIS ABOUT ?

5. SCRUM

6. SCRUM
Framework for agile, iterative product development
On top of that, it‘s about autopoiesis, transparency, team
processes and responsibility

7. DESIGN THINKING

8. DESIGN THINKING
Way of finding solutions to complex questions
Common attributes are: empathy, fail fast, iterate,
interdisciplinary work, prototyping

9. WHY SHOULD YOU
WANT TO COMBINE IT ?

10. THE IDEA BEHIND
WITH DT
figure out possible solution(s) for a question / situation
create prototypes
WITH SCRUM
build the solution

11. CAN THOSE TWO WORK
TOGETHER?

12. GOOD NEWS,
EVERYONE!

13. THERE ARE MANY
OPTIONS
I‘m going to show you one approach, two possibilities ...

14. THERE ARE MANY
OPTIONS
I‘m going to show you one approach, two possibilities ...
.... and a half.

15. LET‘S START WITH THE
PROCESS AND DO THE
"WHO" LATER

16. THE DT PROCESS

17. THE SCRUM PROCESS

18. WHERE DO THE
STORIES COME FROM?

19. WHAT IF THE BACKLOG
IS THE OUTPUT OF A DT
PROCESS?

20. SOURCE: DT
As a user I would
like to achieve X
to have Y ...

21. HOW ABOUT EXISTING
STORIES IN THE
BACKLOG?

22. SOURCE: STORY, DT
...
...

23. ADVANTAGES
Prototyped AcceptedVerified
User centricPlayed out

24. NOT ALL STORIES NEED
TO GO THROUGH A DT
PROCESS

25. DESIGN
THINKING
SCRUM
POSSIBLE
COMBINATION

26. OVERVIEW

27. STORY
As a user I would like to
achieve X to have Y ...

28. SO FAR, SO GOOD.
WHAT ABOUT THE
PEOPLE?

29. THE TEAM
interdisciplinary
experts
self organising
committed
communicating with stakeholders
iterating
SCRUM
TEAM
DESIGN THINKING
TEAM

30. THE PRODUCT OWNER
communicates a clear vision
the team's first contact for questions
responsible for a well written, prioritised backlog
responsible for the stories in the backlog
PRODUCT
OWNER

31. SCRUM MASTER
protects the team
keeps the process going
hosts the meetings
SCRUM
MASTER

32. PO
PROCESS
SCRUM
TEAM
DESIGN THINKING
TEAM
QUESTIONS VISIONS
BACKLOG
COACH SM
ROLES OVERVIEW

33. CONCLUSION
mindsets in DT and Scrum are very similar
processes can be combined
"make the customer / user happy" is essential
.... and the devil's in the details.

34. THANK YOU!
QUESTIONS?
W. Alex Jansen
alex@wajansen.co
@phaoust

35. CREDITS
Photos:
© olesiabilkei - Fotolia.com
© SergiyN - Fotolia.com
© Ingo Vollenberg
© W. Alex Jansen
Artwork:
© Caroline Schmidt, Munich Prinzessin
© Business Visuals GbR