UrbanBound is a web-based platform that helps companies offer relocation assistance to employees. It allows employees to plan and organize their relocation online while connecting them to preferred vendors. The platform has changed how businesses relocate employees by providing online tools. This document discusses how to present a design to developers so they can properly implement it, including touring the developer mindset, using specific language focused on users and metrics, and common tools like user stories and acceptance criteria.

1. How to Present Your
Design to the
Development Team
So They Build It Right
Michael Walkden
@michaelwalkden
www.urbanbound.com

2. delivering teams designer developer
leader agile northwestern practitioner
product quality software
kids start-ups untanned youth vw bus

3. UrbanBound is a web-based platform that helps companies offer a
comprehensive transition system to their newly hired and transferring
employees. Fortune 1000 companies are utilizing UrbanBound to help their
employees bring order instead of chaos and excitement instead of stress to
their transition. With our online tools, employees plan and organize their
entire relocation while being connected to merchants who offer preferred
pricing through our exclusive group buying power.
Our breakthrough approach has changed the way businesses relocate
and onboard employees forever.

4. Abstract
Concept
Awesome
Product

5. And

7. Photo By: Eleaf

8. The Plan
• Tour of the
developer
psyche
• Tools
• Write some
software
Photo By: slworking2

9. The Developer Brain

10. Structural / Procedural Thinker

11. Independent Thinker
Photo By: adwriter

12. Pattern Matcher

13. Long Term Planner
Photo By:
Nicholas_T

14. Pessimist

15. The Best Developers
*In a Nutshell

16. Arrogant
Smart
Lazy

17. Option 1

19. Option 2

21. Speaking The Right
Language

22. Be Specific

23. Explain Why
Use Metrics

24. Talk About The Users,
Teach About The Users

25. Tools You Both Can
Enjoy

26. Inception
A short period of hard collaborative work; to
better understand project objectives, identify
potential users, and define high level functional
scope so that size of the project can be roughly
estimated and an incremental release
strategy can be identified

27. User Centric Design

28. Scrum / Iteration
Planning Meetings

29. Retrospectives
*A learning exercise

30. Design Huddles

31. User Activity Diagrams
*Not the UML kind

32. Personas

33. Wireframes

34. User Stories
As a [user role] I want to [goal] so I can [reason]
Example
As an administrator I want to review users logs
so I can determine if a security breach occurred

35. User Stories
A visual representation
“The card”
Expectations
What done means / Tests
Written description
Notes / Conversation
Further information
Everything else

36. User Stories
Small
Independent
Valuable
Testable
Estimatable
~Negotiable~

37. Acceptance Criteria
Given
Who
Set the scene
When
User takes an action
Then
Expected result

38. So ....
What the ?$@# do
developers do all day
long?

39. Agile Development
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

40. Test Driven Development
(TDD)
Write Write Run
Test Code Test
Higher quality design
Clean simple code

41. TDD
Write Write Run
Test Code Test

42. Demo
Lets write some code

43. WALSTIB
The developer brain
Using the right language
Common tools
Day-in-the-life of a developer

44. Michael Walkden
www.michaelwalkden.com
@michaelwalkden
www.urbanbound.com