How to present your design to the development team so they build it right
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


How to present your design to the development team so they build it right






Total Views
Views on SlideShare
Embed Views



3 Embeds 4 2 1 1



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

How to present your design to the development team so they build it right Presentation Transcript

  • 1. How to Present Your Design to the Development TeamSo They Build It Right Michael Walkden @michaelwalkden
  • 2. delivering teams designer developerleader agile northwestern practitioner product quality softwarekids 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 transferringemployees. Fortune 1000 companies are utilizing UrbanBound to help theiremployees bring order instead of chaos and excitement instead of stress to their transition.  With our online tools, employees plan and organize theirentire 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 ConceptAwesome Product
  • 5. And
  • 6. Photo By: Eleaf
  • 7. The Plan • Tour of the developer psyche • Tools • Write some software Photo By: slworking2
  • 8. The Developer Brain
  • 9. Structural / Procedural Thinker
  • 10. Independent Thinker Photo By: adwriter
  • 11. Pattern Matcher
  • 12. Long Term Planner Photo By: Nicholas_T
  • 13. Pessimist
  • 14. The Best Developers *In a Nutshell
  • 15. Arrogant Smart Lazy
  • 16. Option 1
  • 17. Option 2
  • 18. Speaking The Right Language
  • 19. Be Specific
  • 20. Explain WhyUse Metrics
  • 21. Talk About The Users,Teach About The Users
  • 22. Tools You Both Can Enjoy
  • 23. InceptionA short period of hard collaborative work; to better understand project objectives, identify potential users, and define high level functionalscope so that size of the project can be roughly estimated and an incremental release strategy can be identified
  • 24. User Centric Design
  • 25. Scrum / IterationPlanning Meetings
  • 26. Retrospectives*A learning exercise
  • 27. Design Huddles
  • 28. User Activity Diagrams *Not the UML kind
  • 29. Personas
  • 30. Wireframes
  • 31. User Stories As a [user role] I want to [goal] so I can [reason] ExampleAs an administrator I want to review users logsso I can determine if a security breach occurred
  • 32. User StoriesA visual representation “The card”Expectations What done means / TestsWritten description Notes / ConversationFurther information Everything else
  • 33. User Stories Small Independent Valuable Testable Estimatable ~Negotiable~
  • 34. Acceptance CriteriaGiven Who Set the sceneWhen User takes an actionThen Expected result
  • 35. So .... What the ?$@# dodevelopers do all day long?
  • 36. Agile DevelopmentIndividuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  • 37. Test Driven Development (TDD)Write Write RunTest Code Test Higher quality design Clean simple code
  • 38. TDDWrite Write RunTest Code Test
  • 39. DemoLets write some code
  • 40. WALSTIBThe developer brainUsing the right languageCommon toolsDay-in-the-life of a developer
  • 41. Michael Walkden @michaelwalkden