Think Before You Act or Rapid Prototyping

573 views

Published on

This presentation was given at World Information Architecture Day 2012 - Ghent (Belgium) edition

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
573
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Think Before You Act or Rapid Prototyping

  1. 1. hi
  2. 2. i’m @stevenbeeckman
  3. 3. Think before you act or rapid prototyping
  4. 4. how to build software
  5. 5. Client AnalystDesignerDeveloper Tester Client
  6. 6. Client AnalystDesignerDeveloper Tester Client
  7. 7. en n pm e ri v t Client elo D ev rt Analyst pe Ex DesignerD Developer Tester Client
  8. 8. this is what you get
  9. 9. here’s why
  10. 10. 60 pages of specs nobody reads (nor really understands)
  11. 11. so let’s fix that problem
  12. 12. Solution 1:wireframes
  13. 13. which tools?
  14. 14. A3 paper & pencil
  15. 15. iMockupsOmnigrafflePhotoshopIllustrator Axure Balsamiq based on @wolfr_’s blogpost http://bit.ly/zvZL83
  16. 16. Result: lots of wireframes(but client no real grasp of real flow)
  17. 17. Seeing is believing
  18. 18. Solution 2:rapid prototyping
  19. 19. tools
  20. 20. HTML + CSS + JS
  21. 21. Frameworks: Bootstrap (Twitter) Foundation (ZURB)Your own production framework
  22. 22. Need true data? HTML5 Local StorageSlim/Paris/Idiorm (PHP Persistence) + MySQL RoR
  23. 23. Examples:http://labs.shadowmedia.be/avenuelhttp://labs.shadowmedia.be/twunch
  24. 24. problem:analyst is not a designer nor a developer
  25. 25. still communication problems
  26. 26. some tips
  27. 27. focus on short iterations
  28. 28. reduce communication needs
  29. 29. bu tt he n yo hire polyvalent people u’ ll ha ve to fir e pe op l e?
  30. 30. talk with your client
  31. 31. A LOT
  32. 32. building computers is science
  33. 33. building software is art a few pearls, lots of crap
  34. 34. know your audience
  35. 35. stay in touchdo often & extensive user testing (check @AGConsult’s blog) @stevenbeeckman

×