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

Design thinking and agile development

on

  • 2,396 views

Talk at Interactive Cologne 2013.

Talk at Interactive Cologne 2013.

Statistics

Views

Total Views
2,396
Views on SlideShare
2,227
Embed Views
169

Actions

Likes
7
Downloads
55
Comments
0

3 Embeds 169

http://lanyrd.com 106
http://www.scoop.it 55
https://twitter.com 8

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Design thinking and agile development Design thinking and agile development Presentation Transcript

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