How to prototype to understand your clients
•
0 j'aime•653 vues
The talk by Antti Tarvainen and Harri Lammi at Turku Agile Day on May 16, 2012.
Recommandé
Contenu connexe
En vedette
Similaire à How to prototype to understand your clients
Similaire à How to prototype to understand your clients (20)
Dernier
Dernier (20)
How to prototype to understand your clients
- 1. How to prototype to understand your clients antti.tarvainen@leonidasoy.fi harri.lammi@leonidasoy.fi @tarvaina @harri_lammi
- 2. Talk in one slide Understand the context 1. of your system. Build prototypes to validate 2. your understanding of the context and the design. Different situations call for 3. different kinds of prototypes.
- 3. PROTOSONNI “A prototype in seven days”
- 4. Case: Lausuntopalvelu Demo http://youtu.be/jVlYofasZnI http://lausuntopalvelu.fi https://github.com/leonidas/lausuntopalvelu-prototyyppi but look at it on your own risk — it really is throwaway code.
- 5. Schedule: Understand the problem Start shop 1 day Iterate with paper protos Design & Design user interface 5 days Development Develop functionality Demo 2 hours Deliver to the customer Team: Proxy product owner 2 IX/UI designers 2 software developers
- 10. Startshop Tips DO have a schedule DO let the client tell their story DON’T try to come up with a solution before you understand the problem DON’T delegate design responsibility to the client
- 11. From context to the solution Context Personas We need to understand the Scenarios context before Paper prototypes we can implement the Wireframes solution. Layouts Solution
- 12. From context to the solution Context Personas We use Scenarios different tools to move from Paper prototypes context towards Wireframes solutions. Layouts Solution
- 13. From context to the solution Context We verify our Personas understanding Scenarios at each level with the client Paper prototypes and by Wireframes comparing to the other levels. Layouts Solution
- 15. PO CODE
- 16. Development Tips DO have small tasks (< 2h) DO commit and deploy all the time DO have product owner test the prototype all the time DON’T write anything extra DON’T spend time in polishing
- 17. Internals in this case jQuery, Transparency, Spine, Undescore, ... CoffeeScript Node.js MongoDB Github Linode YouTube
- 18. Demo to the client
- 19. Lessons learned • 7-day projects are exciting! • Throw the code away. • Throw the design away.
- 20. What is good software?
- 21. What is a good tool?
- 22. context tool A tool is used in some context.
- 23. context tool In the context different forces act upon the tool
- 24. context tool Tool is good if it fits the context.
- 25. context tool Tool is bad if it doesn’t fit the context.
- 26. Example.
- 27. when you are Example. just a few bored and need minutes of time entertainment you can stop whenever you want always with you etc. etc. you don’t want to learn anything difficult
- 28. when you are Example. just a few bored and need minutes of time entertainment you can stop whenever you want always with you etc. etc. you don’t want to learn anything difficult
- 29. when you are Example. just a few bored and need minutes of time entertainment you can stop whenever you want always with you etc. etc. you want to learn something useful
- 30. when you are Example. bored and need social entertainment situation you can stop whenever you want always with you etc. etc. you want to learn something useful
- 31. So to create a good tool you need two things.
- 32. context ? ? ? 1. Understand the context where the tool will be used.
- 33. context tool 2. Design a tool that fits the context.
- 34. context tool You cannot tell from an abstract idea, if it will fit the context.
- 35. context tool As you make the idea more concrete, you will see its problems more clearly.
- 36. context tool This gives you an idea how to improve it.
- 37. context tool And so on.
- 38. context tool Continue iterating until you find a design that fits the context well enough.
- 39. specifi implem mainte design testing cation entation nance Traditional waterfall lacks iteration
- 40. specifi implem mainte design testing cation entation nance context tool Probably resulting in a bad tool.
- 41. Agile methods, e.g. Scrum, introduce iteration to fix that problem.
- 42. But a few things are unclear 1. How do you find the context? 2. How does the context result in a backlog?
- 43. user needs User needs are the most fundamental part of the context.
- 44. architecture user interface user needs ? requirements data model feature list What is the most logical next step? Why?
- 45. architecture user interface user needs requirements data model feature list User interface is, because it can be tested against user needs.
- 46. architecture user interface user needs requirements data model feature list You cannot tell from e.g. data model alone if it will match the user needs.
- 47. This is our process.
- 48. The right side of the process is traditional agile, e.g. Scrum.
- 49. Before starting Scrum we investigate the context and look for solutions by prototyping.
- 50. context ? ? ? ? We find out the context of the system by interviewing potential users.
- 51. context ? We describe the context by writing scenarios.
- 52. context tool ? We create prototypes based on the scenarios.
- 53. context tool ? We test the prototypes using simulation and user testing.
- 54. When the user interaction of the most common scenarios is clear, we put them to the product backlog.
- 55. A use case may consist of one or more features.
- 56. We take new features to production based on the rhythm of the project. Preferrably as soon as they are ready.
- 57. There are multiple kinds of prototypes.
- 58. Paper prototyping is fastest.
- 59. A fancier prototype adds precision but not necessarily accuracy.
- 60. We use mostly paper prototypes and functional prototypes.
- 61. The length of a paper prototype feedback loop is minutes.
- 62. The length of a functional prototype feedback loop is days.
- 63. Paper prototype is good for finding out and validating the use cases and the design.
- 64. A functional prototype is good for communicating the vision of the product, selling it and validating the market.
- 65. Talk in one slide Understand the context 1. of your system. Build prototypes to validate 2. your understanding of the context and the design. Different situations call for 3. different kinds of prototypes.