Paperprototyping
Download as ODP, PDF0 likes704 views
Paper prototypes and wireframes help debug applications before coding by clarifying specifications and reducing risk through prototyping. Prototyping improves communication and team building. Usability testing of prototypes reveals hidden requirements, establishes common understanding, and confirms application ownership while building the team. Keeping prototypes unfinished prevents wrong impressions of progress that could occur if prototypes look too polished.
![Thank you! Stephan H. Wissel Lotus Technology & Productivity Advisor [email_address]](https://image.slidesharecdn.com/paperprototyping2009-090226044435-phpapp02/85/Paperprototyping-53-320.jpg)
Paperprototyping
- 1. Paper Prototypes and Wire Frames Debug your applications before you write code
- 3. Prototyping helps to clarify specifications, reduce risk Paper Prototyping - is fast, fun, effective improves on team building and communication - needs proper facilitation Executive Summary
- 4. Definitions Prototype: an individual that exhibits the essential features of a later type (Merriam Webster) Usability: The extend to which a product can be used by specific users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use." (ISO 9241:11)
- 5. The Problem
- 7. Best Quality Shortest Time Lowest Cost Pick any 2
- 8. Cost of Software Fixes UAT Prototyping
- 9. 40% Patterns of large software systems: failure and success (Capers Jones)
- 14. Team Building
- 15. World Peace! At least no more opinion wars!
- 16. Your Toolbox HTML Visio Visual Basic Photoshop Prototyping Software Denim (Berkeley University) Balsamic Mockups
- 17. Demo Time: BALSAMIC MOCKUPS
- 18. If it looks to good it took too long!
- 19. Now it needs to work!
- 20. Problem here: Effort similar to full application Change cycles to long Wrong impressions about progress
- 21. Paper?
- 22. Looking good is bad!
- 23. If it looks good, users expect it to be completed and available!
- 24. So how does it actually work?
- 26. But it is Paper? You are the CPU!
- 28. Demo Time (Video on Youtube)
- 29. What can you test?
- 30. This works: Concepts Terminology Navigation Workflow Task flow Content Functionality Layout Brand
- 31. Other tests required: Micro actions Keyboard/Mouse errors Size Timing Long term use Compatibility Looks?
- 32. Setting up a prototype
- 33. Breath & Depth
- 35. 2 Distinct Steps! Create! Test!
- 36. Create!
- 37. Test! Get your story right! Breath Look Depth Interaction
- 38. Keep the unfinished look!!!!
- 39. Overcome Objections It doesn’t look real Waste of time Not scientific Unprofessional
- 40. Session Preparation Location, Setup Participants Facilitator Computer (max. 0.00001 MHz) Observers Tester Introduction, Ground Rules
- 41. Observers The developers The system architect The project manager NOT the boss of the test person
- 42. The Session Introduce the session Introduce to observers Ask for consent if you tape it Introduce the tasks: Scheduled duration Think aloud No spoon feeding!!!
- 43. The Facilitator's Roles Flight Attendant Sports Caster Scientist
- 44. Findings Watch what users do Listen what users say Give feedback only AFTER the session and only about the prototype Use creativity techniques to sort out your findings
- 45. Debriefing The debriefing session is as important as the test Affinity diagrams Mind maps Action plan
- 47. Screen estates
- 48. More Pitfalls Selection of testers Session disruptions Available scope Guidance (too much / too little) User goals incomplete
- 49. Resources http://www.paperprototyping.com http://www.useit.com http://www.upassoc.org/ http://www.formsthatwork.com http://www.origami.com/ Your local papershop
- 52. Q&A
- 53. Thank you! Stephan H. Wissel Lotus Technology & Productivity Advisor [email_address]