Agile Development and User Expereince: a primer

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?