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.

Agile & UX

4,752 views

Published on

Agile Development and User Expereince: a primer

Published in: Design
  • Login to see the comments

Agile & UX

  1. 1. The Average Ideal Agile Method Jonathan Arnowitz The Devil’s Advocate
  2. 2. First Meet the Patron Saints of Software Engineering
  3. 3. First Meet the Patron Saints of Software Engineering Lorenzo II de Medici Niccolò Machiavelli The first pointed hair manager The first Dilbert What The can I do? ends justify the means
  4. 4. Evil These ends do not justify the means Source Free as in Freedom website.
  5. 5. Good: An Agile Primer Source http://effectiveagiledev.com/
  6. 6. The Agile Safety Valves
  7. 7. The Agile Safety Valves
  8. 8. The Agile Safety Valves
  9. 9. The Agile Safety Valves
  10. 10. The Agile Safety Valves
  11. 11. The Agile Safety Valves
  12. 12. The Agile Safety Valves
  13. 13. The Agile Safety Valves Inefficient
  14. 14. The Agile Safety Valves Inefficient Disaffected
  15. 15. The Agile Safety Valves Inefficient Time killing Disaffected
  16. 16. The Agile Safety Valves Inefficient Time killing Disaffected Distracted
  17. 17. The Agile Safety Valves Inefficient Time killing Disaffected Distracted Waste of time
  18. 18. Agile • Agile is for small co-located teams • Favored by large companies with low confidence in their process • Agile is for and about Engineering • It started out as a Designer-hostile movement • Improving waterfall makes much more sense from a design perspective
  19. 19. Agile Myths
  20. 20. Agile Myths • Agile is iterative
  21. 21. Agile Myths • Agile is iterative • (it’s incremental)
  22. 22. Agile Myths • Agile is iterative • (it’s incremental) • Agile is design friendly
  23. 23. Agile Myths • Agile is iterative • (it’s incremental) • Agile is design friendly • (it is cut-throat engineering, with a forest of potholes, traps and other gotcha’s)
  24. 24. Agile Myths • Agile is iterative • (it’s incremental) • Agile is design friendly • (it is cut-throat engineering, with a forest of potholes, traps and other gotcha’s) • Agile clarifies
  25. 25. Agile Myths • Agile is iterative • (it’s incremental) • Agile is design friendly • (it is cut-throat engineering, with a forest of potholes, traps and other gotcha’s) • Agile clarifies • (it obfuscates via the backlog and the divorce of design from process/requirements)
  26. 26. Agile Myths • Agile is iterative • (it’s incremental) • Agile is design friendly • (it is cut-throat engineering, with a forest of potholes, traps and other gotcha’s) • Agile clarifies • (it obfuscates via the backlog and the divorce of design from process/requirements) • Agile is sound
  27. 27. Agile Myths • Agile is iterative • (it’s incremental) • Agile is design friendly • (it is cut-throat engineering, with a forest of potholes, traps and other gotcha’s) • Agile clarifies • (it obfuscates via the backlog and the divorce of design from process/requirements) • Agile is sound • (loose cannons pressured for quick results who throw out every known Agile safety valve)
  28. 28. The wrong picture
  29. 29. Designed Geknutseld The wrong picture
  30. 30. Focusing on the wrong things
  31. 31. Focusing on the wrong things Essential for design Essential for evaluation
  32. 32. Agile UX Primer
  33. 33. Can I play?
  34. 34. Rather not
  35. 35. Play ball
  36. 36. Whatever
  37. 37. You’re kidding me
  38. 38. Excuse me, you’re in the way
  39. 39. Good news: you can’t play
  40. 40. • Agile is just a new flavor of Machiavellian Software Engineering: • the only rule is what works for this particular company/organization • but requires new strategies • No one Agile Development method fits all
  41. 41. Nevertheless, Some Agile Specific Strategies • Strive to become the SCRUM Master or at least co-SCRUM Master • Attend all meetings especially so-called useless ones • Design hostility keeps you on your toes • Agile means agile for developers not you • Own the backlog or at least the user-facing issues (including so-called non-UI ones)
  42. 42. Questions?
  43. 43. Questions?

×