The Average
Ideal Agile Method
                      Jonathan Arnowitz
                     The Devil’s Advocate
First Meet the Patron Saints
  of Software Engineering
First Meet the Patron Saints
                     of Software Engineering




    Lorenzo II de Medici                    ...
Evil




These ends do not justify the means
         Source Free as in Freedom website.
Good: An Agile Primer




Source http://effectiveagiledev.com/
The Agile Safety Valves
The Agile Safety Valves
The Agile Safety Valves
The Agile Safety Valves
The Agile Safety Valves
The Agile Safety Valves
The Agile Safety Valves
The Agile Safety Valves


    Inefficient
The Agile Safety Valves


    Inefficient


    Disaffected
The Agile Safety Valves


    Inefficient            Time killing


    Disaffected
The Agile Safety Valves


    Inefficient            Time killing


    Disaffected           Distracted
The Agile Safety Valves


    Inefficient                Time killing


    Disaffected               Distracted



       ...
Agile


• Agile is for small co-located teams
• Favored by large companies with low
  confidence in their process
• Agile i...
Agile Myths
Agile Myths



• Agile is iterative
Agile Myths



• Agile is iterative
  •   (it’s incremental)
Agile Myths



• Agile is iterative
  •   (it’s incremental)



• Agile is design friendly
Agile Myths



• Agile is iterative
  •   (it’s incremental)



• Agile is design friendly
  •   (it is cut-throat enginee...
Agile Myths



• Agile is iterative
  •   (it’s incremental)



• Agile is design friendly
  •   (it is cut-throat enginee...
Agile Myths



• Agile is iterative
  •   (it’s incremental)



• Agile is design friendly
  •   (it is cut-throat enginee...
Agile Myths



• Agile is iterative
  •   (it’s incremental)



• Agile is design friendly
  •   (it is cut-throat enginee...
Agile Myths



• Agile is iterative
  •   (it’s incremental)



• Agile is design friendly
  •   (it is cut-throat enginee...
The wrong picture
Designed   Geknutseld
                        The wrong picture
Focusing on the wrong things
Focusing on the wrong things


Essential for design




        Essential for evaluation
Agile UX Primer
Can I play?
Rather not
Play ball
Whatever
You’re kidding me
Excuse me, you’re in
     the way
Good news:
you can’t play
• Agile is just a new flavor of Machiavellian
  Software Engineering:
  •   the only rule is what works for this particular...
Nevertheless, Some Agile Specific
              Strategies

• Strive to become the SCRUM Master or at
  least co-SCRUM Mast...
Questions?
Questions?
Upcoming SlideShare
Loading in...5
×

Agile & UX

4,105

Published on

Agile Development and User Expereince: a primer

Published in: Design
2 Comments
6 Likes
Statistics
Notes
  • The solution is for the Designer to become the Scrum Master? That sounds roughly equivalent to the project manager being the designer. Oh wait - I guess some RIlly Big Companies do it that way... I certainly appreciate the problem, and your comment that success in one Agile product is no predictor for success in another depends on many factors including organizational design, process ownership, general politics, depth of detail in design documentation, whether the project is a new 'from scratch' development or additional features on a mature code base, etc. In my experience Agile is simply developer management and has nothing to do with design. I would really like to see some Agile Design methods that can work hand-in-hand with this movement toward incremental development.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • 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.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
4,105
On Slideshare
0
From Embeds
0
Number of Embeds
33
Actions
Shares
0
Downloads
0
Comments
2
Likes
6
Embeds 0
No embeds

No notes for slide

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?

×