Collaboration. Customers. Conflict? Bridging the Gap between Agile and UX

johanna kollmann
johanna kollmannFreelance product manager, user researcher, information architect.
Collaboration.	
  Customers.	
  Con0lict?

Bridging	
  the	
  gap	
  between	
  
Agile	
  &	
  UX
Johanna	
  Kollmann ~ @johannakoll
UX	
  Day	
  Graz,	
  2013

Photo	
  by	
  Jeffery	
  Scism	
  h1p://www.flickr.com/photos/jgscism/9216206232
Collaboration. Customers. Conflict?    Bridging the Gap between Agile and UX
Agile	
  is	
  becoming	
  standard
“Future	
  plans	
  to	
  implement	
  agile	
  grew	
  from	
  
59%	
  in	
  2001	
  -­‐>	
  83%	
  in	
  2012.	
  Nearly	
  half	
  
said	
  their	
  organization	
  has	
  5+	
  agile	
  teams	
  
(48%),	
  compared	
  to	
  only	
  33%	
  in	
  2011.	
  ”
VersionOne	
  State	
  of	
  Agile	
  Dev	
  Survey,	
  via	
  Lane	
  Halley	
  @thinknow
Backlog

User	
  story

Sprint
Scrum
Stand	
  up
Retrospective
Scrum	
  master

Kanban
Photo	
  by	
  Nigel	
  Howe	
  h1p://www.flickr.com/photos/40939157@N03/5315358341/

Sprint	
  Zero
The	
  Agile	
  Manifesto	
  (2001!)
Individuals	
  and	
  interactions	
  over	
  processes	
  and	
  tools
Working	
  software	
  over	
  comprehensive	
  documentation
Customer	
  collaboration	
  over	
  contract	
  negotiation
Responding	
  to	
  change	
  over	
  following	
  a	
  plan
While	
  basically	
  silent	
  about	
  UX	
  
design,	
  Agile	
  thinking	
  offers	
  a	
  
fundamental	
  paradigm	
  shift	
  about	
  
how	
  to	
  interact	
  and	
  communicate	
  
with	
  your	
  project	
  team	
  and	
  beyond.	
  
~	
  Anders	
  Ramsay	
  @andersramsay
Challenges
How	
  to	
  make	
  it	
  work
Challenges
Collaboration. Customers. Conflict?    Bridging the Gap between Agile and UX
Sprint	
  0
Planning
Data	
  gathering

Developers

Sprint	
  1

Interaction	
  Designers

Implement
high	
  dev
low	
  UI
features

Design	
  for	
  sprint	
  2
Gather	
  customer	
  input	
  for	
  
sprint	
  3
Code

Sprint	
  2

Implement
designs

adapted	
  from	
  a	
  diagram	
  by	
  Lynn	
  Miller

Implement
designs

Customer	
  data

Test	
  sprint	
  1	
  code
Design	
  for	
  sprint	
  3
Gather	
  input	
  for	
  sprint	
  4
Code

Sprint	
  3

Design

Design

Customer	
  data

Test	
  sprint	
  2	
  code
Design	
  for	
  sprint	
  4
Gather	
  input	
  for	
  sprint	
  5
Photo	
  by	
  FlackJacket2010	
  h1p://www.flickr.com/photos/47543932@N08/5976266093
Photo	
  by	
  Choo	
  Yut	
  Shing	
  h1p://www.flickr.com/photos/25802865@N08/10502482036/
Photo	
  by	
  Wendy	
  h1p://www.flickr.com/photos/7705025@N08/2463099768/
I	
  miss	
  research!

Photo	
  by	
  Wendy	
  http://www.flickr.com/photos/kalexanderson/5421517469/
How	
  to	
  make	
  it	
  work
Be	
  there:	
  you	
  are	
  
part	
  of	
  the	
  team
Photo	
  by	
  Boston	
  Public	
  Library	
  http://www.flickr.com/photos/boston_public_library/5703905054/
h1p://www.flickr.com/photos/45581782@N00/8035308650/
Make	
  your	
  
work	
  visible:	
  
you	
  are	
  part	
  of	
  
the	
  team
Champion	
  
collaboration:	
  
expand	
  your	
  
toolkit
h1p://www.flickr.com/photos/menlopics/3928252631/

Pairing
Instead	
  of	
  
“how	
  do	
  we	
  know	
  if	
  it’s	
  done”,	
  
ask	
  
“how	
  do	
  we	
  know	
  if	
  it’s	
  good”.	
  
~	
  Lane	
  Halley	
  @thinknow
RESEARCH!
DATA!

Photo	
  by	
  Jorgen	
  Kesseler	
  h1p://www.flickr.com/photos/58544688@N03/5393485546
Lean	
  Startup
is	
  about	
  learning
through	
  
experiments
with	
  customers

Photo	
  by	
  RDECOMh1p://www.flickr.com/photos/rdecom/7336886600
Build
Learn
Measure

Photo	
  by	
  RDECOMh1p://www.flickr.com/photos/rdecom/7336886600
Make	
  research	
  a	
  habit.
Qualitative	
  and	
  quantitative	
  (+	
  remote!)
‘5	
  users	
  every	
  friday’
Degine	
  research	
  questions	
  with	
  the	
  team
Be	
  clear	
  about	
  success	
  criteria	
  +	
  measures
Test	
  what	
  you	
  got
Train	
  other	
  people
Clean	
  up	
  your	
  debt.
Developers	
  refactor.
Developers	
  write	
  tests.
Key	
  aspects	
  of	
  quality.
Hold	
  a	
  design	
  retrospective.
Refactor	
  your	
  design	
  system.
Key	
  aspects	
  of	
  quality.

Photo	
  by	
  Wendy	
  h1p://www.flickr.com/photos/7705025@N08/2463099768/
Make	
  things	
  for	
  people,	
  with	
  people
Summary
Be	
  part	
  of	
  the	
  team.
Make	
  your	
  work	
  visible.
Collaborate,	
  pair.
Run	
  experiments,	
  make	
  research	
  a	
  habit.
Clean	
  up	
  your	
  debt.	
  
Refactor	
  your	
  design	
  system.

h1p://www.flickr.com/photos/hannahdonovan/5900445189/
It’s	
  about	
  the	
  team
Responsibilities	
  &	
  competencies	
  over	
  roles
Expertise	
  over	
  interest
Outcome	
  over	
  process
No	
  ego!

Photo	
  by	
  Jeff	
  Golden	
  h1p://www.flickr.com/photos/46868900@N00/2637637797/
Resources
Agile	
  and	
  UX:	
  Two	
  tastes	
  that	
  taste	
  great	
  together,	
  Lane	
  Halley,	
  UX	
  Week	
  2013,	
  http://vimeo.com/74944431
Sustainable	
  pace,	
  Agile	
  &	
  The	
  Big	
  Design	
  Refactor,	
  Jonathan	
  Berger,	
  Balanced	
  Team	
  Conference	
  2013,	
  http://
design.pivotallabs.com/jpb/jpb-­‐balteam2013-­‐talk/deck/
Case	
  Study	
  of	
  Customer	
  Input	
  For	
  a	
  Successful	
  Product,	
  Lynn	
  Miller	
  (2005)
5	
  Users	
  every	
  Friday,	
  Tom	
  Illmensee	
  &	
  Alyson	
  Muff,	
  Agile	
  2009	
  Proceedings
Learning	
  to	
  play	
  UX	
  rugby,	
  Anders	
  Ramsay,	
  http://slidesha.re/GPfK0w
Beyond	
  Staggered	
  Sprints:	
  Integrating	
  User	
  Experience	
  and	
  Agile,	
  Jeff	
  Gothelf,	
  http://slidesha.re/9Pq3qb
Designing	
  the	
  user	
  experience	
  in	
  an	
  agile	
  context,	
  Johanna	
  Kollmann,	
  http://bit.ly/p3NmWI
Design	
  Pairing,	
  Samuel	
  Bowles,	
  UXLX	
  2012,	
  https://speakerdeck.com/shmuel/design-­‐pairing-­‐uxlx
Test	
  everything	
  you	
  got	
  regardless	
  of	
  its	
  polish	
  or	
  Jidelity,	
  Jeff	
  Gothelf,	
  http://bit.ly/n6qjTI
It’s	
  Our	
  Research:	
  Getting	
  Stakeholder	
  Buy-­‐In	
  for	
  UX	
  Research	
  Projects	
  ,	
  Tomer	
  Sharon
Introduction	
  to	
  Design	
  Studio	
  Methodology,	
  Will	
  Evans,	
  http://uxmag.com/articles/introduction-­‐to-­‐design-­‐studio-­‐
methodology
The	
  KJ	
  Technique:	
  A	
  Group	
  Process	
  for	
  Establishing	
  Priorities,	
  Jared	
  M.	
  Spool,	
  http://www.uie.com/articles/
kj_technique/
The	
  new	
  user	
  story	
  backlog	
  is	
  a	
  map,	
  Jeff	
  Patton,	
  http://www.agileproductdesign.com/blog/the_new_backlog.html
Collaboration	
  games:	
  http://gogamestorm.com,	
  http://innovationgames.com/resources/the-­‐games/
Thank	
  you:
Konrad	
  &	
  Keith.
Lane	
  Halley,	
  Jonathan	
  Berger,	
  Jeff	
  Gothelf,	
  
Will	
  Evans,	
  Desiree	
  Sy,	
  Anders	
  Ramsay,	
  
Janice	
  Fraser,	
  William	
  Pietri,	
  Adrian	
  
Howard,	
  Shawn	
  Crowley	
  &	
  the	
  rest	
  of	
  
Balanced	
  Team.
1 of 32

More Related Content

Similar to Collaboration. Customers. Conflict? Bridging the Gap between Agile and UX

Agile OverviewAgile Overview
Agile OverviewAndy Birds
222 views38 slides
Successful Agile/UXSuccessful Agile/UX
Successful Agile/UXJeremy Kriegel
1.1K views115 slides

Similar to Collaboration. Customers. Conflict? Bridging the Gap between Agile and UX(20)

More from johanna kollmann(20)

Systems Thinking  for Product ManagersSystems Thinking  for Product Managers
Systems Thinking for Product Managers
johanna kollmann3.2K views
Systems Thinking for agile service designSystems Thinking for agile service design
Systems Thinking for agile service design
johanna kollmann6.3K views
Understanding systemsUnderstanding systems
Understanding systems
johanna kollmann3K views
We Love Change? Change is Scary!We Love Change? Change is Scary!
We Love Change? Change is Scary!
johanna kollmann10.2K views
Crowdsourcing innovation, version 2Crowdsourcing innovation, version 2
Crowdsourcing innovation, version 2
johanna kollmann1.8K views

Recently uploaded(20)

ThroughputThroughput
Throughput
Moisés Armani Ramírez25 views
METHOD AND SYSTEM FOR PREDICTING OPTIMAL LOAD FOR WHICH THE YIELD IS MAXIMUM ...METHOD AND SYSTEM FOR PREDICTING OPTIMAL LOAD FOR WHICH THE YIELD IS MAXIMUM ...
METHOD AND SYSTEM FOR PREDICTING OPTIMAL LOAD FOR WHICH THE YIELD IS MAXIMUM ...
Prity Khastgir IPR Strategic India Patent Attorney Amplify Innovation22 views
Green Leaf Consulting: Capabilities DeckGreen Leaf Consulting: Capabilities Deck
Green Leaf Consulting: Capabilities Deck
GreenLeafConsulting147 views
Liqid: Composable CXL PreviewLiqid: Composable CXL Preview
Liqid: Composable CXL Preview
CXL Forum114 views
ISWC2023-McGuinnessTWC16x9FinalShort.pdfISWC2023-McGuinnessTWC16x9FinalShort.pdf
ISWC2023-McGuinnessTWC16x9FinalShort.pdf
Deborah McGuinness80 views

Collaboration. Customers. Conflict? Bridging the Gap between Agile and UX

  • 1. Collaboration.  Customers.  Con0lict? Bridging  the  gap  between   Agile  &  UX Johanna  Kollmann ~ @johannakoll UX  Day  Graz,  2013 Photo  by  Jeffery  Scism  h1p://www.flickr.com/photos/jgscism/9216206232
  • 3. Agile  is  becoming  standard “Future  plans  to  implement  agile  grew  from   59%  in  2001  -­‐>  83%  in  2012.  Nearly  half   said  their  organization  has  5+  agile  teams   (48%),  compared  to  only  33%  in  2011.  ” VersionOne  State  of  Agile  Dev  Survey,  via  Lane  Halley  @thinknow
  • 4. Backlog User  story Sprint Scrum Stand  up Retrospective Scrum  master Kanban Photo  by  Nigel  Howe  h1p://www.flickr.com/photos/40939157@N03/5315358341/ Sprint  Zero
  • 5. The  Agile  Manifesto  (2001!) Individuals  and  interactions  over  processes  and  tools Working  software  over  comprehensive  documentation Customer  collaboration  over  contract  negotiation Responding  to  change  over  following  a  plan
  • 6. While  basically  silent  about  UX   design,  Agile  thinking  offers  a   fundamental  paradigm  shift  about   how  to  interact  and  communicate   with  your  project  team  and  beyond.   ~  Anders  Ramsay  @andersramsay
  • 8. How  to  make  it  work
  • 11. Sprint  0 Planning Data  gathering Developers Sprint  1 Interaction  Designers Implement high  dev low  UI features Design  for  sprint  2 Gather  customer  input  for   sprint  3 Code Sprint  2 Implement designs adapted  from  a  diagram  by  Lynn  Miller Implement designs Customer  data Test  sprint  1  code Design  for  sprint  3 Gather  input  for  sprint  4 Code Sprint  3 Design Design Customer  data Test  sprint  2  code Design  for  sprint  4 Gather  input  for  sprint  5
  • 12. Photo  by  FlackJacket2010  h1p://www.flickr.com/photos/47543932@N08/5976266093
  • 13. Photo  by  Choo  Yut  Shing  h1p://www.flickr.com/photos/25802865@N08/10502482036/
  • 14. Photo  by  Wendy  h1p://www.flickr.com/photos/7705025@N08/2463099768/
  • 15. I  miss  research! Photo  by  Wendy  http://www.flickr.com/photos/kalexanderson/5421517469/
  • 16. How  to  make  it  work
  • 17. Be  there:  you  are   part  of  the  team Photo  by  Boston  Public  Library  http://www.flickr.com/photos/boston_public_library/5703905054/
  • 19. Make  your   work  visible:   you  are  part  of   the  team
  • 22. Instead  of   “how  do  we  know  if  it’s  done”,   ask   “how  do  we  know  if  it’s  good”.   ~  Lane  Halley  @thinknow
  • 23. RESEARCH! DATA! Photo  by  Jorgen  Kesseler  h1p://www.flickr.com/photos/58544688@N03/5393485546
  • 24. Lean  Startup is  about  learning through   experiments with  customers Photo  by  RDECOMh1p://www.flickr.com/photos/rdecom/7336886600
  • 26. Make  research  a  habit. Qualitative  and  quantitative  (+  remote!) ‘5  users  every  friday’ Degine  research  questions  with  the  team Be  clear  about  success  criteria  +  measures Test  what  you  got Train  other  people
  • 27. Clean  up  your  debt. Developers  refactor. Developers  write  tests. Key  aspects  of  quality. Hold  a  design  retrospective. Refactor  your  design  system. Key  aspects  of  quality. Photo  by  Wendy  h1p://www.flickr.com/photos/7705025@N08/2463099768/
  • 28. Make  things  for  people,  with  people
  • 29. Summary Be  part  of  the  team. Make  your  work  visible. Collaborate,  pair. Run  experiments,  make  research  a  habit. Clean  up  your  debt.   Refactor  your  design  system. h1p://www.flickr.com/photos/hannahdonovan/5900445189/
  • 30. It’s  about  the  team Responsibilities  &  competencies  over  roles Expertise  over  interest Outcome  over  process No  ego! Photo  by  Jeff  Golden  h1p://www.flickr.com/photos/46868900@N00/2637637797/
  • 31. Resources Agile  and  UX:  Two  tastes  that  taste  great  together,  Lane  Halley,  UX  Week  2013,  http://vimeo.com/74944431 Sustainable  pace,  Agile  &  The  Big  Design  Refactor,  Jonathan  Berger,  Balanced  Team  Conference  2013,  http:// design.pivotallabs.com/jpb/jpb-­‐balteam2013-­‐talk/deck/ Case  Study  of  Customer  Input  For  a  Successful  Product,  Lynn  Miller  (2005) 5  Users  every  Friday,  Tom  Illmensee  &  Alyson  Muff,  Agile  2009  Proceedings Learning  to  play  UX  rugby,  Anders  Ramsay,  http://slidesha.re/GPfK0w Beyond  Staggered  Sprints:  Integrating  User  Experience  and  Agile,  Jeff  Gothelf,  http://slidesha.re/9Pq3qb Designing  the  user  experience  in  an  agile  context,  Johanna  Kollmann,  http://bit.ly/p3NmWI Design  Pairing,  Samuel  Bowles,  UXLX  2012,  https://speakerdeck.com/shmuel/design-­‐pairing-­‐uxlx Test  everything  you  got  regardless  of  its  polish  or  Jidelity,  Jeff  Gothelf,  http://bit.ly/n6qjTI It’s  Our  Research:  Getting  Stakeholder  Buy-­‐In  for  UX  Research  Projects  ,  Tomer  Sharon Introduction  to  Design  Studio  Methodology,  Will  Evans,  http://uxmag.com/articles/introduction-­‐to-­‐design-­‐studio-­‐ methodology The  KJ  Technique:  A  Group  Process  for  Establishing  Priorities,  Jared  M.  Spool,  http://www.uie.com/articles/ kj_technique/ The  new  user  story  backlog  is  a  map,  Jeff  Patton,  http://www.agileproductdesign.com/blog/the_new_backlog.html Collaboration  games:  http://gogamestorm.com,  http://innovationgames.com/resources/the-­‐games/
  • 32. Thank  you: Konrad  &  Keith. Lane  Halley,  Jonathan  Berger,  Jeff  Gothelf,   Will  Evans,  Desiree  Sy,  Anders  Ramsay,   Janice  Fraser,  William  Pietri,  Adrian   Howard,  Shawn  Crowley  &  the  rest  of   Balanced  Team.