Agile & UX

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

1 comments

Comments 1 - 1 of 1 previous next Post a comment

  • + arnoslide Jonathan Arnowitz 1 month ago
    To get some missing context I put an explanation in my blog. Here it is to be more user friendly than just provide a link (http://arnoland.blogspot.com/2009/10/agile-ux.html):
    The presentation below started out as a short talk at the UX Cocktail Hour. However, the presentation has been gaining in popularity. So I decided to post it here. Because it does not really stand alone to people not at the presentation some misunderstandings have resulted. I will record the presentation with audio, but in the mean time, let a few words here suffice:
    It is a design-centric view of Agile, or rather a War weary design centric view of agile.
    The main point being that Agile is not a development method as much as it is a way of setting aggressive deadlines. What happens in one Agile project does not predict success for another. Instead the designer needs to be Agile in figuring out how they can best fit in. However, that agility should not extend to your design process. Designs still need to be well thought out concepts not something grown together in piecemeal increments.
    The bottom line message (found on the last slide) is to be truly successful in Agile, you need to follow your own design process but be intimately involved in the Scrum process, preferably as a Scrum Master. This is essential for maintaining an overview of what is going on with your design. At the very least, own the user facing stories/requirements in the product backlog.
    And Sherlock Holmes and Dr. Watson were meant to personify regression testing.
Post a comment
Embed Video
Edit your comment Cancel

3 Favorites

Agile & UX - Presentation Transcript

  1. The Average Ideal Agile Method Jonathan Arnowitz The Devil’s Advocate
  2. First Meet the Patron Saints of Software Engineering
  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. Evil These ends do not justify the means Source Free as in Freedom website.
  5. Good: An Agile Primer Source http://effectiveagiledev.com/
  6. The Agile Safety Valves
  7. The Agile Safety Valves
  8. The Agile Safety Valves
  9. The Agile Safety Valves
  10. The Agile Safety Valves
  11. The Agile Safety Valves
  12. The Agile Safety Valves
  13. The Agile Safety Valves Inefficient
  14. The Agile Safety Valves Inefficient Disaffected
  15. The Agile Safety Valves Inefficient Time killing Disaffected
  16. The Agile Safety Valves Inefficient Time killing Disaffected Distracted
  17. The Agile Safety Valves Inefficient Time killing Disaffected Distracted Waste of time
  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. Agile Myths
  20. Agile Myths • Agile is iterative
  21. Agile Myths • Agile is iterative • (it’s incremental)
  22. Agile Myths • Agile is iterative • (it’s incremental) • Agile is design friendly
  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. 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. 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. 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. 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. The wrong picture
  29. Designed Geknutseld The wrong picture
  30. Focusing on the wrong things
  31. Focusing on the wrong things Essential for design Essential for evaluation
  32. Agile UX Primer
  33. Can I play?
  34. Rather not
  35. Play ball
  36. Whatever
  37. You’re kidding me
  38. Excuse me, you’re in the way
  39. Good news: you can’t play
  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. 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. Questions?
  43. Questions?

+ Jonathan ArnowitzJonathan Arnowitz, 1 month ago

custom

462 views, 3 favs, 1 embeds more stats

Agile Development and User Expereince: a primer

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 462
    • 430 on SlideShare
    • 32 from embeds
  • Comments 1
  • Favorites 3
  • Downloads 0
Most viewed embeds
  • 32 views on http://arnoland.blogspot.com

more

All embeds
  • 32 views on http://arnoland.blogspot.com

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories