Your SlideShare is downloading. ×
Design thinking and agile development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Design thinking and agile development

3,463
views

Published on

Talk at Interactive Cologne 2013.

Talk at Interactive Cologne 2013.

Published in: Business, Technology

0 Comments
10 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,463
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
101
Comments
0
Likes
10
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. *interactive cologne 2013DESIGN THINKING &AGILE DEVELOPMENT*W. Alex Jansenalex@wajansen.co@phaoust
  • 2. WHO?consultant / trainer for lean, agile,business modellingdegrees in computer scienceand musicexperience in multiple industries
  • 3. FOUNDER1st at age 18, followed by more, ITand othersCurrent: Materials for Scrum,Design Thinking, and BusinessModelling
  • 4. WHAT IS THIS ABOUT ?
  • 5. SCRUM
  • 6. SCRUMFramework for agile, iterative product developmentOn top of that, it‘s about autopoiesis, transparency, teamprocesses and responsibility
  • 7. DESIGN THINKING
  • 8. DESIGN THINKINGWay of finding solutions to complex questionsCommon attributes are: empathy, fail fast, iterate,interdisciplinary work, prototyping
  • 9. WHY SHOULD YOUWANT TO COMBINE IT ?
  • 10. THE IDEA BEHINDWITH DTfigure out possible solution(s) for a question / situationcreate prototypesWITH SCRUMbuild the solution
  • 11. CAN THOSE TWO WORKTOGETHER?
  • 12. GOOD NEWS,EVERYONE!
  • 13. THERE ARE MANYOPTIONSI‘m going to show you one approach, two possibilities ...
  • 14. THERE ARE MANYOPTIONSI‘m going to show you one approach, two possibilities ....... and a half.
  • 15. LET‘S START WITH THEPROCESS AND DO THE"WHO" LATER
  • 16. THE DT PROCESS
  • 17. THE SCRUM PROCESS
  • 18. WHERE DO THESTORIES COME FROM?
  • 19. WHAT IF THE BACKLOGIS THE OUTPUT OF A DTPROCESS?
  • 20. SOURCE: DTAs a user I wouldlike to achieve Xto have Y ...
  • 21. HOW ABOUT EXISTINGSTORIES IN THEBACKLOG?
  • 22. SOURCE: STORY, DT......
  • 23. ADVANTAGESPrototyped AcceptedVerifiedUser centricPlayed out
  • 24. NOT ALL STORIES NEEDTO GO THROUGH A DTPROCESS
  • 25. DESIGNTHINKINGSCRUMPOSSIBLECOMBINATION
  • 26. OVERVIEW
  • 27. STORYAs a user I would like toachieve X to have Y ...
  • 28. SO FAR, SO GOOD.WHAT ABOUT THEPEOPLE?
  • 29. THE TEAMinterdisciplinaryexpertsself organisingcommittedcommunicating with stakeholdersiteratingSCRUMTEAMDESIGN THINKINGTEAM
  • 30. THE PRODUCT OWNERcommunicates a clear visionthe teams first contact for questionsresponsible for a well written, prioritised backlogresponsible for the stories in the backlogPRODUCTOWNER
  • 31. SCRUM MASTERprotects the teamkeeps the process goinghosts the meetingsSCRUMMASTER
  • 32. POPROCESSSCRUMTEAMDESIGN THINKINGTEAMQUESTIONS VISIONSBACKLOGCOACH SMROLES OVERVIEW
  • 33. CONCLUSIONmindsets in DT and Scrum are very similarprocesses can be combined"make the customer / user happy" is essential.... and the devils in the details.
  • 34. THANK YOU!QUESTIONS?W. Alex Jansenalex@wajansen.co@phaoust
  • 35. CREDITSPhotos:© olesiabilkei - Fotolia.com© SergiyN - Fotolia.com© Ingo Vollenberg© W. Alex JansenArtwork:© Caroline Schmidt, Munich Prinzessin© Business Visuals GbR