ModevUX AgileUX

356 views

Published on

Published in: Design, Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
356
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • ModevUX AgileUX

    1. 1. AGILE UX
    2. 2. MICHAEL JOVEL• UI Developer at startapps• My mother tells people I am an international lawyer•Istopped correcting her because it is easier twitter: @mjovel• Worked with US Navy, email: mjovel@gmail.com Progressive, University of Chicago & University of MD
    3. 3. HISTORICALLY DESIGN HAS BEEN BASED ON THE WATERFALL METHOD
    4. 4. CREATIVE BRIEF > DESIGN > APPROVAL > PRINTER > DELIVERY
    5. 5. http://uxmag.com/articles/change-on-a-dime-agile-design
    6. 6. THAT IS NOT WHAT THEY WANTED
    7. 7. http://uxmag.com/articles/change-on-a-dime-agile-design
    8. 8. DON’T GET CAUGHT UP ON PROCESS
    9. 9. VALUE NOT REQUIREMENTS
    10. 10. “Eric Reis 4 thstate of agile: Astory does not end at acceptance but rather must be validated for value
    11. 11. WORK IS MEANINGLESSUNLESS YOU CREATE VALUE
    12. 12. LIVE AND BREATHE RESULTS
    13. 13. FROM HYPOTHESIS TO REQUIREMENTS
    14. 14. HYPOTHESIS• a tentative assumption made in order to draw out and test its logical or empirical consequences - merriam-webster
    15. 15. WHY HYPOTHESIS?• Rather than make assertions it puts forth a questions which must be then validated• Engages team creativity
    16. 16. WHAT ASSUMPTIONS DOYOU HAVE THAT IF PROVEN FALSE WILL CAUSE YOUR SOLUTION TO FAIL?
    17. 17. WE BELIEVE ___________ ANDIF THIS IS TRUE WE SHOULD SEE __________
    18. 18. COLLABORATION
    19. 19. DESIGN STUDIO
    20. 20. DESIGN STUDIO• Butcherpaper, painters tape, sharpies and stop watch, grid template sheets• Build small 3-4 person teams composed of designer, developers and business team.• Give each team a persona to focus on
    21. 21. SKETCH•5 minutes to create 6-8 sketches individually
    22. 22. PITCH•3 Minutes to pitch to group
    23. 23. CRITIQUE• two ways it accomplished goals• two ways it failed to accomplish goals
    24. 24. TEAM SKETCHING•5 minutes to iterate on best of individual sketches
    25. 25. TEAM PITCH•3 minute pitch to entire group
    26. 26. TOO MANY SECRETS
    27. 27. PROMOTE TRANSPARENCY
    28. 28. PROMOTE CODE LITERACY
    29. 29. CODE LITERACY IS NOT CODE FLUENCY
    30. 30. PAIR DESIGNING• Make sure designers and developers spend time working together• saves time on implementation• promotes ownership
    31. 31. PATTERN LIBRARY• Library of UI Patterns that developers can use (i.e. buttons, fields, etc.• Library of UI Components composed of multiple patterns (i.e. forms, video player, etc.)
    32. 32. VALIDATION
    33. 33. WHAT IS THE SMALLESTAMOUNT OF WORK WE CAN DO TO VALIDATE OUR CONCEPT?
    34. 34. GET IT IN USERS HANDS!
    35. 35. PROTOTYPE• Paper• Keynote / Powerpoint• Axure, iRise, etc.• Cordova (a.k.a Phonegap)
    36. 36. ITERATE

    ×