Slide 1

Slide 1 text

Prototyping Pitfalls Ross Belmont @rossbelmont

Slide 2

Slide 2 text

@rossbelmont

Slide 3

Slide 3 text

@rossbelmont

Slide 4

Slide 4 text

@rossbelmont

Slide 5

Slide 5 text

@rossbelmont

Slide 6

Slide 6 text

@rossbelmont

Slide 7

Slide 7 text

@rossbelmont

Slide 8

Slide 8 text

@rossbelmont

Slide 9

Slide 9 text

@rossbelmont

Slide 10

Slide 10 text

@rossbelmont

Slide 11

Slide 11 text

@rossbelmont

Slide 12

Slide 12 text

@rossbelmont Spend less time tweaking Photoshop comps

Slide 13

Slide 13 text

@rossbelmont

Slide 14

Slide 14 text

@rossbelmont

Slide 15

Slide 15 text

@rossbelmont We crushed it.

Slide 16

Slide 16 text

@rossbelmont

Slide 17

Slide 17 text

@rossbelmont

Slide 18

Slide 18 text

@rossbelmont

Slide 19

Slide 19 text

@rossbelmont

Slide 20

Slide 20 text

@rossbelmont

Slide 21

Slide 21 text

@rossbelmont

Slide 22

Slide 22 text

@rossbelmont Walkthrough (a.k.a. Storyboard)

Slide 23

Slide 23 text

@rossbelmont

Slide 24

Slide 24 text

@rossbelmont Building a prototype is not iterating. =

Slide 25

Slide 25 text

@rossbelmont Building a prototype is not iterating. =

Slide 26

Slide 26 text

@rossbelmont Schedule Time to Iterate: Don’t Do This Sprint 1 Sprint 2 Sprint 3

Slide 27

Slide 27 text

@rossbelmont Schedule Time to Iterate: Do This Instead Sprint 1 Sprint 2 Sprint 3

Slide 28

Slide 28 text

@rossbelmont

Slide 29

Slide 29 text

@rossbelmont

Slide 30

Slide 30 text

@rossbelmont Prototyping Affects Everyone Role Unintended Effect Adjustment Designers • Added stress of hitting tight deadline • Highlighted need to iterate Smarter planning in future phases/projects Clients • Can’t react quickly enough • Want to “shop it around” • Repeated expectation setting • May still need deliverables Project managers • Increases clarity on what will be built • New work to manage Discussion needed to get comfortable with new process (at a minimum) Developers & testers

Slide 31

Slide 31 text

@rossbelmont

Slide 32

Slide 32 text

@rossbelmont

Slide 33

Slide 33 text

@rossbelmont

Slide 34

Slide 34 text

@rossbelmont Some Details Prototypes Don’t Include

Slide 35

Slide 35 text

@rossbelmont Some Details Prototypes Don’t Include • Error states

Slide 36

Slide 36 text

@rossbelmont Some Details Prototypes Don’t Include • Error states • Field validation rules

Slide 37

Slide 37 text

@rossbelmont Some Details Prototypes Don’t Include • Error states • Field validation rules • Back end data specs

Slide 38

Slide 38 text

@rossbelmont Some Details Prototypes Don’t Include • Error states • Field validation rules • Back end data specs • Status codes and their meanings

Slide 39

Slide 39 text

@rossbelmont Some Details Prototypes Don’t Include • Error states • Field validation rules • Back end data specs • Status codes and their meanings • Back end business logic

Slide 40

Slide 40 text

@rossbelmont Some Details Prototypes Don’t Include • Error states • Field validation rules • Back end data specs • Status codes and their meanings • Back end business logic • “Nonfunctional” requirements (e.g. page load times)

Slide 41

Slide 41 text

@rossbelmont • Thing to build • Related thing to build • Another thing to build • Related thing to build • Another thing to build • Final thing to build

Slide 42

Slide 42 text

@rossbelmont Story 1 Story 2 Story 3 • Thing to build • Related thing to build • Another thing to build • Related thing to build • Another thing to build • Final thing to build

Slide 43

Slide 43 text

@rossbelmont

Slide 44

Slide 44 text

@rossbelmont Sprint 1 Sprint 2 Sprint 3

Slide 45

Slide 45 text

@rossbelmont Prototyping Affects Everyone Role Unintended Effect Adjustment Designers • Added stress of hitting tight deadline • Highlighted need to iterate Smarter planning in future phases/projects Clients • Can’t react quickly enough • Want to “shop it around” • Repeated expectation setting • May still need deliverables Project managers • Increases clarity on what will be built • New work to manage Discussion needed to get comfortable with new process (at a minimum) Developers & testers • Doesn’t capture all details needed for build • Confusing when out of date Discussion needed to get comfortable with new process (at a minimum)

Slide 46

Slide 46 text

@rossbelmont

Slide 47

Slide 47 text

@rossbelmont

Slide 48

Slide 48 text

@rossbelmont Thank you! I’m @rossbelmont.