Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
The Secret Of Agile UX



         James O’Brien
      james@sparrk.co.uk
The Secret Of Agile UX
   Or, How to avoid Big Design Up Front
by pretending not to do Big Design Up Front




           ...
Who is this guy anyway?
Who is this guy anyway?
  UX Freelancer for 10 years
Who is this guy anyway?
   UX Freelancer for 10 years
Agile UX practitioner for 5 years
Who is this guy anyway?
   UX Freelancer for 10 years
Agile UX practitioner for 5 years
 Sideline in Agile Enablement
Who is this guy anyway?
   UX Freelancer for 10 years
Agile UX practitioner for 5 years
 Sideline in Agile Enablement
  I ...
Who is this guy anyway?
   UX Freelancer for 10 years
Agile UX practitioner for 5 years
 Sideline in Agile Enablement
  I ...
๏   No magic bullets contained within
๏   No magic bullets contained within
๏   Do not attempt to implement by rote
๏   No magic bullets contained within
๏   Do not attempt to implement by rote
๏   Not guaranteed to work with Enterprise
 ...
๏   No magic bullets contained within
๏   Do not attempt to implement by rote
๏   Not guaranteed to work with Enterprise
 ...
๏   No magic bullets contained within
๏   Do not attempt to implement by rote
๏   Not guaranteed to work with Enterprise
 ...
“No Big Design Up Front”
i1   i2   i3   i4   i5
Design
 for i1




          i1   i2   i3   i4   i5
Design    Design
 for i1    for i2




           i1       i2   i3   i4   i5
Design    Design    Design
 for i1    for i2    for i3




           i1        i2       i3   i4   i5
Design    Design    Design    Design
 for i1    for i2    for i3    for i4




           i1        i2        i3       i4 ...
Design    Design    Design    Design    Design
 for i1    for i2    for i3    for i4    for i5




           i1        i2...
Have a
Design    Design    Design    Design    Design
                                                  fucking
 for i1   ...
Have a
Design    Design    Design    Design    Design
                                                  fucking
 for i1   ...
i0   i1   i2   i3   i4   i5




Agile’s Dirty Secret: i0
i0   i1   i2   i3   i4   i5
Design
 for i1




          i0   i1   i2   i3   i4   i5
Design
Design
           for i1
 for i1
            & i2




           i0       i1   i2   i3   i4   i5
Design    Design
Design
           for i1    for i2
 for i1
            & i2      & i3




           i0        i1       i...
Design    Design    Design
Design
           for i1    for i2    for i3
 for i1
            & i2      & i3      & i4




 ...
Design    Design    Design    Design
Design
           for i1    for i2    for i3    for i4
 for i1
            & i2      ...
Design
          Design    Design    Design    Design
Design                                            for i5,
          ...
Design
          Design    Design    Design    Design              Have a
Design                                          ...
Design
          Design    Design    Design    Design              Have a
Design                                          ...
Agile’s Other Dirty Secret:
  Planning
Gather
Requirements




 Agile’s Other Dirty Secret:
   Planning
Gather        Analyse
Requirements   Requirements




 Agile’s Other Dirty Secret:
   Planning
Gather        Analyse      Write
Requirements   Requirements   Epics




 Agile’s Other Dirty Secret:
   Planning
Gather        Analyse      Write   Scope
Requirements   Requirements   Epics     R1




 Agile’s Other Dirty Secret:
   Pl...
Gather        Analyse      Write   Scope    Write
Requirements   Requirements   Epics     R1    Stories




 Agile’s Other...
Gather        Analyse      Write   Scope    Write    Plan
Requirements   Requirements   Epics     R1    Stories    R1




...
Gather        Analyse      Write   Scope    Write    Plan
Requirements   Requirements   Epics     R1    Stories    R1




...
Write
Epics
Wait... isn’t that how
   design works?
Wait... isn’t that how
          design works?
✦   Pair with BAs during analysis
Wait... isn’t that how
          design works?
✦   Pair with BAs during analysis
✦   Wireframe based on requirements and f...
Wait... isn’t that how
          design works?
✦   Pair with BAs during analysis
✦   Wireframe based on requirements and f...
Wait... isn’t that how
          design works?
✦   Pair with BAs during analysis
✦   Wireframe based on requirements and f...
Wait... isn’t that how
          design works?
✦   Pair with BAs during analysis
✦   Wireframe based on requirements and f...
Wait... isn’t that how
          design works?
✦   Pair with BAs during analysis
✦   Wireframe based on requirements and f...
Gather        Analyse      Write   Scope    Write    Plan
Requirements   Requirements   Epics     R1    Stories    R1
Gather        Analyse      Write   Scope    Write    Plan
Requirements   Requirements   Epics     R1    Stories    R1




...
Gather        Analyse        Write   Scope    Write    Plan
Requirements   Requirements     Epics     R1    Stories    R1
...
Gather        Analyse       Write      Scope    Write    Plan
Requirements   Requirements    Epics        R1    Stories   ...
Gather        Analyse       Write   Scope       Write    Plan
Requirements   Requirements    Epics     R1       Stories   ...
Gather        Analyse      Write   Scope     Write     Plan
Requirements   Requirements   Epics     R1     Stories     R1
...
Gather        Analyse      Write    Scope     Write    Plan
Requirements   Requirements   Epics      R1     Stories    R1
...
Align Your Strategies Early
Align Your Strategies Early
✦   Mobile First == Agile Minimum Valuable Product
Align Your Strategies Early
✦   Mobile First == Agile Minimum Valuable Product
✦   User Testing fits with frequent demos a...
Align Your Strategies Early
✦   Mobile First == Agile Minimum Valuable Product
✦   User Testing fits with frequent demos a...
Align Your Strategies Early
✦   Mobile First == Agile Minimum Valuable Product
✦   User Testing fits with frequent demos a...
Align Your Strategies Early
✦   Mobile First == Agile Minimum Valuable Product
✦   User Testing fits with frequent demos a...
Align Your Strategies Early
✦   Mobile First == Agile Minimum Valuable Product
✦   User Testing fits with frequent demos a...
Support Story Writing
Support Story Writing
✦   Feed Wireframes into stories as functional artefacts
Support Story Writing
✦   Feed Wireframes into stories as functional artefacts
✦   Develop your personas with BAs so they ...
Support Story Writing
✦   Feed Wireframes into stories as functional artefacts
✦   Develop your personas with BAs so they ...
Support Story Writing
✦   Feed Wireframes into stories as functional artefacts
✦   Develop your personas with BAs so they ...
Support Story Writing
✦   Feed Wireframes into stories as functional artefacts
✦   Develop your personas with BAs so they ...
During Development
Prepare to Refactor
Prepare to Refactor
✦   Organise your files to prepare for change
Prepare to Refactor
✦   Organise your files to prepare for change




           http://photoshopetiquette.com/
Prepare to Refactor
✦   Organise your files to prepare for change
Prepare to Refactor
✦   Organise your files to prepare for change
✦   Use design/UX patterns wherever possible
Prepare to Refactor
✦   Organise your files to prepare for change
✦   Use design/UX patterns wherever possible
✦   Use stu...
Prepare to Refactor
✦   Organise your files to prepare for change
✦   Use design/UX patterns wherever possible
✦   Use stu...
Prepare to Refactor
✦   Organise your files to prepare for change
✦   Use design/UX patterns wherever possible
✦   Use stu...
Prepare to Refactor
✦   Organise your files to prepare for change
✦   Use design/UX patterns wherever possible
✦   Use stu...
Digression:
Digression:
Digression:
We Need To Rethink The Way
    We Do Deliverables
The web is not flat images
       any more
The web is not flat images
       any more
✦   We need to be able to show multiple states and
    animations easily
The web is not flat images
       any more
✦   We need to be able to show multiple states and
    animations easily
✦   We...
The web is not flat images
       any more
✦   We need to be able to show multiple states and
    animations easily
✦   We...
The web is not flat images
       any more
✦   We need to be able to show multiple states and
    animations easily
✦   We...
Hannah Donovan
✦   What does our 3/4 view look
    like?
✦   http://www.webdirections.org/
    resources/hannah-donovan-
 ...
Jan Srutek




http://www.slideshare.net/JanSru/communicating-and-
           selling-ux-design-deliverables
Project Meteor




http://projectmeteor.org/
Stubbed Designs?
Stubbed Designs?
✦   Stubbed Designs act as placeholders for
    features that haven’t been designed yet
Stubbed Designs?
✦   Stubbed Designs act as placeholders for
    features that haven’t been designed yet
✦   They can also...
Stubbed Designs?
✦   Stubbed Designs act as placeholders for
    features that haven’t been designed yet
✦   They can also...
You can flag stubs too
.stub:before{
width : 64px; height : 64px;

background : url(/core/images/nodeploy/flag-stub.png)
r...
You can flag stubs too
.stub:before{
width : 64px; height : 64px;

background : url(/core/images/nodeploy/flag-stub.png)
r...
UX Debt?
UX Debt?
“Good enough” or “quick fix”
solutions that get you past a
       problem quickly
UX Debt?
“Good enough” or “quick fix”
solutions that get you past a
       problem quickly
But too much debt can choke a
 ...
UX Debt?
“Good enough” or “quick fix”
solutions that get you past a
       problem quickly
But too much debt can choke a
 ...
Defining “Done”
Defining “Done”
✦   Don’t be precious about signoff
Defining “Done”
✦   Don’t be precious about signoff
✦   If it works well enough, sign it off and raise an
    enhancement ...
Defining “Done”
✦   Don’t be precious about signoff
✦   If it works well enough, sign it off and raise an
    enhancement ...
Defining “Done”
✦   Don’t be precious about signoff
✦   If it works well enough, sign it off and raise an
    enhancement ...
Continuous Availability
Continuous Availability
✦   Is horrible and makes it difficult to get into the zone
    and you can’t listen to music and ...
Continuous Availability
✦   Is horrible and makes it difficult to get into the zone
    and you can’t listen to music and ...
Upcoming SlideShare
Loading in …5
×

of

Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 1 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 2 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 3 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 4 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 5 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 6 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 7 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 8 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 9 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 10 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 11 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 12 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 13 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 14 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 15 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 16 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 17 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 18 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 19 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 20 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 21 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 22 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 23 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 24 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 25 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 26 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 27 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 28 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 29 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 30 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 31 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 32 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 33 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 34 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 35 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 36 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 37 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 38 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 39 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 40 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 41 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 42 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 43 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 44 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 45 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 46 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 47 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 48 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 49 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 50 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 51 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 52 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 53 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 54 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 55 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 56 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 57 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 58 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 59 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 60 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 61 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 62 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 63 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 64 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 65 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 66 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 67 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 68 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 69 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 70 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 71 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 72 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 73 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 74 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 75 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 76 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 77 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 78 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 79 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 80 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 81 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 82 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 83 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 84 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 85 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 86 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 87 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 88 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 89 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 90 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 91 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 92 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 93 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 94 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 95 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 96 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 97 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 98 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 99 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 100 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 101 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 102 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 103 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 104 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 105 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 106 Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front Slide 107
Upcoming SlideShare
Relation achat grands groupes / startups : explication du projet de Deal Memo
Next
Download to read offline and view in fullscreen.

102 Likes

Share

Download to read offline

Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front

Download to read offline

My talk from UX Camp London 2011, about the lie of "No Big Design Up Front," the opinion that UX people need to be less lazy and feckless, and finding the gap between the two where Agile UX can flourish.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Agile UX – How To Avoid Big Design Up Front By Pretending Not To Do Big Design Up Front

  1. The Secret Of Agile UX James O’Brien james@sparrk.co.uk
  2. The Secret Of Agile UX Or, How to avoid Big Design Up Front by pretending not to do Big Design Up Front James O’Brien james@sparrk.co.uk
  3. Who is this guy anyway?
  4. Who is this guy anyway? UX Freelancer for 10 years
  5. Who is this guy anyway? UX Freelancer for 10 years Agile UX practitioner for 5 years
  6. Who is this guy anyway? UX Freelancer for 10 years Agile UX practitioner for 5 years Sideline in Agile Enablement
  7. Who is this guy anyway? UX Freelancer for 10 years Agile UX practitioner for 5 years Sideline in Agile Enablement I HAVE DONE WRONG THINGS
  8. Who is this guy anyway? UX Freelancer for 10 years Agile UX practitioner for 5 years Sideline in Agile Enablement I HAVE DONE WRONG THINGS But you can learn from my mistakes
  9. ๏ No magic bullets contained within
  10. ๏ No magic bullets contained within ๏ Do not attempt to implement by rote
  11. ๏ No magic bullets contained within ๏ Do not attempt to implement by rote ๏ Not guaranteed to work with Enterprise Agile, Cargo Cult Agile or Scrumbut
  12. ๏ No magic bullets contained within ๏ Do not attempt to implement by rote ๏ Not guaranteed to work with Enterprise Agile, Cargo Cult Agile or Scrumbut ๏ Requires interaction with BAs and Developers
  13. ๏ No magic bullets contained within ๏ Do not attempt to implement by rote ๏ Not guaranteed to work with Enterprise Agile, Cargo Cult Agile or Scrumbut ๏ Requires interaction with BAs and Developers ๏ Risk of improved delivery and morale
  14. “No Big Design Up Front”
  15. i1 i2 i3 i4 i5
  16. Design for i1 i1 i2 i3 i4 i5
  17. Design Design for i1 for i2 i1 i2 i3 i4 i5
  18. Design Design Design for i1 for i2 for i3 i1 i2 i3 i4 i5
  19. Design Design Design Design for i1 for i2 for i3 for i4 i1 i2 i3 i4 i5
  20. Design Design Design Design Design for i1 for i2 for i3 for i4 for i5 i1 i2 i3 i4 i5
  21. Have a Design Design Design Design Design fucking for i1 for i2 for i3 for i4 for i5 party i1 i2 i3 i4 i5
  22. Have a Design Design Design Design Design fucking for i1 for i2 for i3 for i4 for i5 party i1 i2 i3 i4 i5 THIS NEVER WORKS
  23. i0 i1 i2 i3 i4 i5 Agile’s Dirty Secret: i0
  24. i0 i1 i2 i3 i4 i5
  25. Design for i1 i0 i1 i2 i3 i4 i5
  26. Design Design for i1 for i1 & i2 i0 i1 i2 i3 i4 i5
  27. Design Design Design for i1 for i2 for i1 & i2 & i3 i0 i1 i2 i3 i4 i5
  28. Design Design Design Design for i1 for i2 for i3 for i1 & i2 & i3 & i4 i0 i1 i2 i3 i4 i5
  29. Design Design Design Design Design for i1 for i2 for i3 for i4 for i1 & i2 & i3 & i4 & i5 i0 i1 i2 i3 i4 i5
  30. Design Design Design Design Design Design for i5, for i1 for i2 for i3 for i4 for i1 & i2 & i3 & i4 & i5 plan fucking party i0 i1 i2 i3 i4 i5
  31. Design Design Design Design Design Have a Design for i5, for i1 for i2 for i3 for i4 fucking for i1 & i2 & i3 & i4 & i5 plan fucking party party i0 i1 i2 i3 i4 i5
  32. Design Design Design Design Design Have a Design for i5, for i1 for i2 for i3 for i4 fucking for i1 & i2 & i3 & i4 & i5 plan fucking party party i0 i1 i2 i3 i4 i5 THIS NEVER WORKS
  33. Agile’s Other Dirty Secret: Planning
  34. Gather Requirements Agile’s Other Dirty Secret: Planning
  35. Gather Analyse Requirements Requirements Agile’s Other Dirty Secret: Planning
  36. Gather Analyse Write Requirements Requirements Epics Agile’s Other Dirty Secret: Planning
  37. Gather Analyse Write Scope Requirements Requirements Epics R1 Agile’s Other Dirty Secret: Planning
  38. Gather Analyse Write Scope Write Requirements Requirements Epics R1 Stories Agile’s Other Dirty Secret: Planning
  39. Gather Analyse Write Scope Write Plan Requirements Requirements Epics R1 Stories R1 Agile’s Other Dirty Secret: Planning
  40. Gather Analyse Write Scope Write Plan Requirements Requirements Epics R1 Stories R1 Agile’s Other Dirty Secret: Planning ~= Design
  41. Write Epics
  42. Wait... isn’t that how design works?
  43. Wait... isn’t that how design works? ✦ Pair with BAs during analysis
  44. Wait... isn’t that how design works? ✦ Pair with BAs during analysis ✦ Wireframe based on requirements and feed those into epics
  45. Wait... isn’t that how design works? ✦ Pair with BAs during analysis ✦ Wireframe based on requirements and feed those into epics ✦ Refine your wireframes as the epics are validated by the business
  46. Wait... isn’t that how design works? ✦ Pair with BAs during analysis ✦ Wireframe based on requirements and feed those into epics ✦ Refine your wireframes as the epics are validated by the business ✦ Some IA and UX artefacts will pop out of this process naturally
  47. Wait... isn’t that how design works? ✦ Pair with BAs during analysis ✦ Wireframe based on requirements and feed those into epics ✦ Refine your wireframes as the epics are validated by the business ✦ Some IA and UX artefacts will pop out of this process naturally ✦ Develop your modular design language
  48. Wait... isn’t that how design works? ✦ Pair with BAs during analysis ✦ Wireframe based on requirements and feed those into epics ✦ Refine your wireframes as the epics are validated by the business ✦ Some IA and UX artefacts will pop out of this process naturally ✦ Develop your modular design language ✦ Only go hi-fi when the release is scoped
  49. Gather Analyse Write Scope Write Plan Requirements Requirements Epics R1 Stories R1
  50. Gather Analyse Write Scope Write Plan Requirements Requirements Epics R1 Stories R1 Identify UX Requirements
  51. Gather Analyse Write Scope Write Plan Requirements Requirements Epics R1 Stories R1 Define Identify UX large-scale IA Requirements (to feed into epics)
  52. Gather Analyse Write Scope Write Plan Requirements Requirements Epics R1 Stories R1 Define Identify UX large-scale IA Wireframe Requirements (to feed Epics into epics)
  53. Gather Analyse Write Scope Write Plan Requirements Requirements Epics R1 Stories R1 Define Begin Identify UX large-scale IA Wireframe site Requirements (to feed Epics design into epics) language
  54. Gather Analyse Write Scope Write Plan Requirements Requirements Epics R1 Stories R1 Define Begin Identify UX large-scale IA Wireframe site Wireframe Requirements (to feed Epics design Stories into epics) language
  55. Gather Analyse Write Scope Write Plan Requirements Requirements Epics R1 Stories R1 Define Begin Identify UX large-scale IA Wireframe site Wireframe Hi-Fi Requirements (to feed Epics design Stories i1 of R1 into epics) language
  56. Align Your Strategies Early
  57. Align Your Strategies Early ✦ Mobile First == Agile Minimum Valuable Product
  58. Align Your Strategies Early ✦ Mobile First == Agile Minimum Valuable Product ✦ User Testing fits with frequent demos and releases
  59. Align Your Strategies Early ✦ Mobile First == Agile Minimum Valuable Product ✦ User Testing fits with frequent demos and releases ✦ Browser Testing fits with Continuous QA
  60. Align Your Strategies Early ✦ Mobile First == Agile Minimum Valuable Product ✦ User Testing fits with frequent demos and releases ✦ Browser Testing fits with Continuous QA ✦ Accessibility exposes a layer that automated testing can exploit
  61. Align Your Strategies Early ✦ Mobile First == Agile Minimum Valuable Product ✦ User Testing fits with frequent demos and releases ✦ Browser Testing fits with Continuous QA ✦ Accessibility exposes a layer that automated testing can exploit ✦ Feedback from the business validates your design
  62. Align Your Strategies Early ✦ Mobile First == Agile Minimum Valuable Product ✦ User Testing fits with frequent demos and releases ✦ Browser Testing fits with Continuous QA ✦ Accessibility exposes a layer that automated testing can exploit ✦ Feedback from the business validates your design ✦ Share knowledge with BAs wherever possible
  63. Support Story Writing
  64. Support Story Writing ✦ Feed Wireframes into stories as functional artefacts
  65. Support Story Writing ✦ Feed Wireframes into stories as functional artefacts ✦ Develop your personas with BAs so they can frame stories around the personas
  66. Support Story Writing ✦ Feed Wireframes into stories as functional artefacts ✦ Develop your personas with BAs so they can frame stories around the personas ✦ Define your UX principles as NFRs
  67. Support Story Writing ✦ Feed Wireframes into stories as functional artefacts ✦ Develop your personas with BAs so they can frame stories around the personas ✦ Define your UX principles as NFRs ✦ Let developers know that the wireframes are canonical
  68. Support Story Writing ✦ Feed Wireframes into stories as functional artefacts ✦ Develop your personas with BAs so they can frame stories around the personas ✦ Define your UX principles as NFRs ✦ Let developers know that the wireframes are canonical ✦ Feed hi-fis if you have them, but keep the developers focused on the wireframes
  69. During Development
  70. Prepare to Refactor
  71. Prepare to Refactor ✦ Organise your files to prepare for change
  72. Prepare to Refactor ✦ Organise your files to prepare for change http://photoshopetiquette.com/
  73. Prepare to Refactor ✦ Organise your files to prepare for change
  74. Prepare to Refactor ✦ Organise your files to prepare for change ✦ Use design/UX patterns wherever possible
  75. Prepare to Refactor ✦ Organise your files to prepare for change ✦ Use design/UX patterns wherever possible ✦ Use stubbed design and UX debt
  76. Prepare to Refactor ✦ Organise your files to prepare for change ✦ Use design/UX patterns wherever possible ✦ Use stubbed design and UX debt ✦ Build a reusable asset library early on
  77. Prepare to Refactor ✦ Organise your files to prepare for change ✦ Use design/UX patterns wherever possible ✦ Use stubbed design and UX debt ✦ Build a reusable asset library early on ✦ Use a preprocessor like LESS to ensure your CSS can be quickly refactored
  78. Prepare to Refactor ✦ Organise your files to prepare for change ✦ Use design/UX patterns wherever possible ✦ Use stubbed design and UX debt ✦ Build a reusable asset library early on ✦ Use a preprocessor like LESS to ensure your CSS can be quickly refactored ✦ Focus on high-friction targets first - the UX debt will be less painful for users on the low-friction ones
  79. Digression:
  80. Digression:
  81. Digression: We Need To Rethink The Way We Do Deliverables
  82. The web is not flat images any more
  83. The web is not flat images any more ✦ We need to be able to show multiple states and animations easily
  84. The web is not flat images any more ✦ We need to be able to show multiple states and animations easily ✦ We need the rest of the team to be able to understand the scope of a design unambiguously
  85. The web is not flat images any more ✦ We need to be able to show multiple states and animations easily ✦ We need the rest of the team to be able to understand the scope of a design unambiguously ✦ We need to be able to refactor our deliverables quickly, and have the refactoring cascade through the whole project
  86. The web is not flat images any more ✦ We need to be able to show multiple states and animations easily ✦ We need the rest of the team to be able to understand the scope of a design unambiguously ✦ We need to be able to refactor our deliverables quickly, and have the refactoring cascade through the whole project ✦ We need to have a tool that supports patterns and modularity
  87. Hannah Donovan ✦ What does our 3/4 view look like? ✦ http://www.webdirections.org/ resources/hannah-donovan- designing-without-the-browser/ ✦ http://www.webdirections.org/ resources/hannah-donovan- telling-stories-through-design/ ✦ @han
  88. Jan Srutek http://www.slideshare.net/JanSru/communicating-and- selling-ux-design-deliverables
  89. Project Meteor http://projectmeteor.org/
  90. Stubbed Designs?
  91. Stubbed Designs? ✦ Stubbed Designs act as placeholders for features that haven’t been designed yet
  92. Stubbed Designs? ✦ Stubbed Designs act as placeholders for features that haven’t been designed yet ✦ They can also be your progressive enhancement baseline
  93. Stubbed Designs? ✦ Stubbed Designs act as placeholders for features that haven’t been designed yet ✦ They can also be your progressive enhancement baseline ✦ They should be simple, but they don’t need to be ugly
  94. You can flag stubs too .stub:before{ width : 64px; height : 64px; background : url(/core/images/nodeploy/flag-stub.png) right top no-repeat; display : block; content:" "; position : absolute; right : 0; top : 0;} .stub{position : relative;}
  95. You can flag stubs too .stub:before{ width : 64px; height : 64px; background : url(/core/images/nodeploy/flag-stub.png) right top no-repeat; display : block; content:" "; position : absolute; right : 0; top : 0;} .stub{position : relative;}
  96. UX Debt?
  97. UX Debt? “Good enough” or “quick fix” solutions that get you past a problem quickly
  98. UX Debt? “Good enough” or “quick fix” solutions that get you past a problem quickly But too much debt can choke a project further down the line
  99. UX Debt? “Good enough” or “quick fix” solutions that get you past a problem quickly But too much debt can choke a project further down the line So you must address UX debt periodically - during i zero or UAT are good times
  100. Defining “Done”
  101. Defining “Done” ✦ Don’t be precious about signoff
  102. Defining “Done” ✦ Don’t be precious about signoff ✦ If it works well enough, sign it off and raise an enhancement - let the client decide how important design perfection is
  103. Defining “Done” ✦ Don’t be precious about signoff ✦ If it works well enough, sign it off and raise an enhancement - let the client decide how important design perfection is ✦ Or track imperfections as defects or UX debt and raise tasks to fix them
  104. Defining “Done” ✦ Don’t be precious about signoff ✦ If it works well enough, sign it off and raise an enhancement - let the client decide how important design perfection is ✦ Or track imperfections as defects or UX debt and raise tasks to fix them ✦ Be open to developers’ suggestions but stand firm on the really important stuff
  105. Continuous Availability
  106. Continuous Availability ✦ Is horrible and makes it difficult to get into the zone and you can’t listen to music and YOU HAVE TO DO IT
  107. Continuous Availability ✦ Is horrible and makes it difficult to get into the zone and you can’t listen to music and YOU HAVE TO DO IT ✦ If developers think you’re unapproachable, they’ll guess at implementation – THIS IS BAD
  108. Continuous Availability ✦ Is horrible and makes it difficult to get into the zone and you can’t listen to music and YOU HAVE TO DO IT ✦ If developers think you’re unapproachable, they’ll guess at implementation – THIS IS BAD ✦ Be available with your body language as well as your speech: “My time is infinite and you can have as much as you want”
  109. Continuous Availability Strategies
  110. Continuous Availability Strategies ✦ The Sacrificial Lamb – when there are >1 people in a role, they rotate their availability
  111. Continuous Availability Strategies ✦ The Sacrificial Lamb – when there are >1 people in a role, they rotate their availability ✦ The Scary Face – a physical flag you can raise when you need to focus, but it requires a lot of discipline
  112. Continuous Availability Strategies ✦ The Sacrificial Lamb – when there are >1 people in a role, they rotate their availability ✦ The Scary Face – a physical flag you can raise when you need to focus, but it requires a lot of discipline ✦ No-meeting Hours – you stay available to the team but no meetings can be booked, reduces the chance of being pulled away
  113. Continuous Availability Strategies ✦ The Sacrificial Lamb – when there are >1 people in a role, they rotate their availability ✦ The Scary Face – a physical flag you can raise when you need to focus, but it requires a lot of discipline ✦ No-meeting Hours – you stay available to the team but no meetings can be booked, reduces the chance of being pulled away ✦ Be careful not to overuse these and drive devs away!
  114. Leverage QA and Showcases
  115. Leverage QA and Showcases ✦ Don’t let the devs destroy the showcase environment - use it for guerilla user testing!
  116. Leverage QA and Showcases ✦ Don’t let the devs destroy the showcase environment - use it for guerilla user testing! ✦ Ensure the devs focus on making deployment simple so you can incorporate rapid prototyping (but you probably don’t want to do this on the showcase environment)
  117. Leverage QA and Showcases ✦ Don’t let the devs destroy the showcase environment - use it for guerilla user testing! ✦ Ensure the devs focus on making deployment simple so you can incorporate rapid prototyping (but you probably don’t want to do this on the showcase environment) ✦ You can automate some UI and accessibility testing using Selenium: http://code.google.com/p/web- accessibility-testing/downloads/list
  118. Leverage QA and Showcases ✦ Don’t let the devs destroy the showcase environment - use it for guerilla user testing! ✦ Ensure the devs focus on making deployment simple so you can incorporate rapid prototyping (but you probably don’t want to do this on the showcase environment) ✦ You can automate some UI and accessibility testing using Selenium: http://code.google.com/p/web- accessibility-testing/downloads/list ✦ While you’re automating, ensure that test data is structured so as to stress the UI
  119. There’s more How do we estimate UX effort? Leveraging Test Data Reusable Brainstorming UX and Automation UX and Spikes Optimising Research with Agile UX on the card wall
  120. Agile Won’t Wait http://www.flickr.com/photos/uriel1998/
  121. Now go and build incredible things.
  122. Thank You James O’Brien james@sparrk.co.uk
  • ArtPagsuyoin

    Jun. 4, 2021
  • return001

    Aug. 22, 2020
  • MaraAchaGonzlez

    Apr. 17, 2020
  • GOBUG

    Mar. 6, 2018
  • kennethowino9

    Feb. 4, 2018
  • kimberlyjohansen

    Oct. 24, 2017
  • getjins

    Oct. 10, 2017
  • KevinCelsoAlvarado

    Sep. 14, 2017
  • GeraldYeo2

    Sep. 7, 2017
  • UnaTeng

    Aug. 23, 2017
  • puxbanget

    Jul. 7, 2017
  • DominikDomaradzki

    Jun. 25, 2017
  • williammdavis

    Dec. 3, 2016
  • KellyLothbrookSmith

    Oct. 16, 2016
  • jcvigo

    Oct. 7, 2016
  • GeorgeStavrides

    Sep. 12, 2016
  • midorichan2

    Aug. 30, 2016
  • NicholasTenhue

    Jun. 18, 2016
  • zarthustra7

    May. 18, 2016
  • larboz

    Apr. 13, 2016

My talk from UX Camp London 2011, about the lie of "No Big Design Up Front," the opinion that UX people need to be less lazy and feckless, and finding the gap between the two where Agile UX can flourish.

Views

Total views

46,969

On Slideshare

0

From embeds

0

Number of embeds

2,241

Actions

Downloads

518

Shares

0

Comments

0

Likes

102

×