Talk about Prototyping for Microsoft's RIAction day 2009

1. Paper Prototypes and Wire Frames Debug your applications before you write code

5. The Problem

6. Telling vs. Doing

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)

10. Prototyping Results

11. Hidden Requirements

12. Application Ownership

13. Common Understanding

14. Team Building

15. World Peace! At least no more opinion wars!

17. Demo Time: BALSAMIC MOCKUPS

18. If it looks to good it took too long!

19. Now it needs to work!

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?

25. Let user interact!

26. But it is Paper? You are the CPU!

28. Demo Time (Video on Youtube)

29. What can you test?

32. Setting up a prototype

33. Breath & Depth

34. Interaction Model

35. 2 Distinct Steps! Create! Test!

36. Create!

38. Keep the unfinished look!!!!

46. Common Challenges

47. Screen estates

50. http://www.balsamiq.com/products/mockups

51. http://mayo.svidnik.com/images/blog_pics/feed-icon.png

52. Q&A

53. Thank you! Stephan H. Wissel Lotus Technology & Productivity Advisor [email_address]