Prototyping and Scrum

3,605 views

Published on

This presentation is about the challenges faced when doing prototypes and to make sure that these prototypes are useful for the developers.
It is about how the prototyping activity fits into the iterative implementation cycles (Scrum Sprints) and how the triangle of UX, development and visual design works together, in particular if external service providers are involved.

Published in: Design, Technology
3 Comments
8 Likes
Statistics
Notes
  • Thanks for the clarification. Totally agree with the term 'Sprint Zero' which can arouse wrong expectations about the length of the 'sprint'.

    Not only user research should be done up front but also iterative prototyping and testing. So because 'prototyping' is in the title of the talk also the Sprint Zero should be mentioned as being essential.

    I'm looking forward to your blog post!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Yes as the title says it, the focus is on prototyping. (Some attendees were also wondering why this was missing, so probably it was not really clear that it is essential)

    I totally agree that research is essential and has to take place before putting anything to paper. I'm not so happy with the Term 'Sprint Zero' though. We used that term too but it always rose the expectation of 'Research needs the length of one sprint'. Which is of course almost impossible to plan, foresee or guarantee, especially if you're handed a black-box where you have to figure out its scope.

    Thanks for the hint I will write about it when I'm back from Lisbon!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Thank you for the insteresting presentation!

    I found interesting, that you don't have much slides about using UX-Methods before the sprints start.

    At soultank were successful with using the Sprint Zero for UX-work. Doing User Research, Iterative Prototyping and Usability Testing to getting an idea if the main concept is usable. (We have also experience with 'Prep Sprints' but the Sprint Zero is even more important from our perspective).
    We even did a whole day Refresher Workshop last year about this topic.

    What is your experience with using UX-Methods up front? Would be great if could summarize some insights in a blog post.

    Regards
    Andreas
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
3,605
On SlideShare
0
From Embeds
0
Number of Embeds
40
Actions
Shares
0
Downloads
44
Comments
3
Likes
8
Embeds 0
No embeds

No notes for slide

Prototyping and Scrum

  1. 1. Agile Experience Meetup ZurichPrototyping and ScrumMemi Beltrame@bratwurstkomet April 3rd 2013
  2. 2. I Like MagicUX Designer for Founder of Less a Mess Content Strategy
  3. 3. 7 Challenges1. Know your audience2. Make it interactive3. Make it testable4. Get the right data5. Get it done6. Work on your process7. Cope with 3rd party designers
  4. 4. 1Know your audience
  5. 5. Knowing your audience meansDo your research!
  6. 6. User Research Methods Analysis Userstatistics What people did Observation Contextual User Diary Observation Inquiry What people do Focus Groups Structured Interviews Unstructured Surveys Inquiry interviews What people say Quantitative Quantitative Why and how? How many? How often?Source: Moser, Chistian „User Experience Design“. 2012, Springer Vieweg
  7. 7. Research helps definingthe relevant criteria to base your prototoype on
  8. 8. Relevant Criteria =High impact on Experience• Age.• Devices.• Location.• Homogeneity.• Education / Professional background.
  9. 9. Age
  10. 10. • Single Page • No Chrome • No adds • No wrong placesvisithttp://preview.liip.ch/zooon an iPad or iPhone.
  11. 11. Location
  12. 12. Züriwald App Educational HikingPlanning Offline = Download Closed Places Weather
  13. 13. 2Make it interactive
  14. 14. Jungfraubahnen Tourism Scribbles Balsamiq HTML-Web Prototype
  15. 15. Speed vs. Accuracy Pick one.
  16. 16. Neue Zürcher Zeitung Webpaper
  17. 17. 3Make it testable
  18. 18. The more interactive, the easier to test.
  19. 19. Testable prototypesanticipate behavior (as well as possible)
  20. 20. Fake it.
  21. 21. 4Get the right data
  22. 22. Do anything to get real data. Does it exist? How does it look like?
  23. 23. Prototype Data:(Fonds in an application for bankers) VF - European Mid and Small Cap Equity B (Lux) Real Data: Aberdeen Global - Emerging Markets Equity A Acc UBS (Lux) Medium Term Bond Fund - CHF P-acc UBS (Lux) Medium Term Bond Fund - EUR P-acc UBS (Lux) Medium Term Bond Fund - USD P-acc
  24. 24. 5Get it done
  25. 25. Pen and Paper or Clickables
  26. 26. What you needExtremely rudimentalAffordableFast and withoutelectricity
  27. 27. What you getExtremely rudimentalAffordableFast and withoutelectricity
  28. 28. Design StudioQuantity has its own quality
  29. 29. Design Studio
  30. 30. The Power of Pen & PaperDesign Studio• Fast and cheap.• Awesome to integrate stakeholders• Scribble with external Designers• Impressive start to signal „We get a lot done fast“
  31. 31. PoP - Prototyping on Paper http://popapp.in
  32. 32. ProtostrapCode: https://github.com/liip/ProtostrapDemo: http://preview.liip.ch/Protostrap/
  33. 33. Protostrap• Based on Boostrap• Library with CSS and Javascript Files• PHP Files to hold templates and snippets together• Documentation and examples in the package• Optimized for Mobile: - fast tap recognistion - iOS Tabbar for Prototyping of native apps - „Add to home“• Basic PHP knowledge needed• Not pretty, but functional!• Can get messy.
  34. 34. 6Work on Your Process
  35. 35. Crossfunctional Teams
  36. 36. Crossfunctional Teamshelp with:• Avoiding silos• Spreading knowledge• Making dialogue easier• displaying unity towards the client
  37. 37. Preparation
  38. 38. Prep-versionsEach Sprint has a precedingPrep version.
  39. 39. A Prep version for us is just a „FixFor“ version in JIRA.
  40. 40. If you can‘t prep it you can‘t do it.
  41. 41. One sprint ahead prep• User stories for the coming sprint• Prototyping: Tasks in the user stories• Not only Prototyping has to be prepped!• No commitment in Prep: too many unknown variables
  42. 42. Board = DailyRegular PrepBoard Board Board = Daily
  43. 43. Prototype - Demo
  44. 44. Demoing• Show the interaction, not the elements (Prototypes are about flow)• Go through user stories• Show to devs & visual designers before demo to get feedback• Make prototype available (web & git)• Add „How to demo“ in story if necessary• Make screencast if necessary
  45. 45. When are prototypesuseful for devs?• When they help devs anticipate the scope for implementation.• Prototypes have to be complete: - realistic data - complete interactions
  46. 46. 7 Cope with 3rdparty designers
  47. 47. 3rd party designers• Demand a visual designer with experience in web.• Communicate clear expectations.• Integrate them early. Scribble with them and let them be part.• Say no. Seriously.
  48. 48. Things that don‘t work• Design Briefings• Lists of deliverables• If they have to adapt to agile just for you. (if they are waterfall, you are waterfall too)
  49. 49. Questions?
  50. 50. Thank you! I‘m Memi Beltrame @bratwurstkomet on twitter

×