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

1. hi

2. i’m @stevenbeeckman

4. Think before you act
or
rapid prototyping

5. how to build software

6. Client
Analyst
Designer
Developer
Tester
Client

7. Client
Analyst
Designer
Developer
Tester
Client

8. en n
pm e
ri v
t
Client
elo D
ev rt
Analyst
pe
Ex
Designer
D
Developer
Tester
Client

9. this is what you get

11. here’s why

12. 60 pages of specs nobody reads
(nor really understands)

13. so let’s fix that problem

14. Solution 1:
wireframes

15. which tools?

16. A3 paper & pencil

17. iMockups
Omnigraffle
Photoshop
Illustrator
Axure
Balsamiq
based on @wolfr_’s blogpost http://bit.ly/zvZL83

18. Result:
lots of wireframes
(but client no real grasp of real flow)

19. Seeing is believing

20. Solution 2:
rapid prototyping

21. tools

22. HTML + CSS + JS

23. Frameworks:
Bootstrap (Twitter)
Foundation (ZURB)
Your own production framework

24. Need true data?
HTML5 Local Storage
Slim/Paris/Idiorm (PHP Persistence) + MySQL
RoR

25. Examples:
http://labs.shadowmedia.be/avenuel
http://labs.shadowmedia.be/twunch

26. problem:
analyst is not a designer nor a developer

27. still communication problems

28. some tips

30. focus on short iterations

31. reduce communication needs

32. bu
tt
he
n
yo
hire polyvalent people
u’
ll
ha
ve
to
fir
e
pe
op
l e?

33. talk with your client

34. A LOT

35. building computers is science

36. building software is art
a few pearls, lots of crap

37. know your audience

38. stay in touch
do often & extensive user testing
(check @AGConsult’s blog)
@stevenbeeckman