Successfully reported this slideshow.

The Two Burger Team – Cross Functional Pairing for MVPs

1,093 views

Published on

Part of the inspiration for lean is to eliminate as much unnecessary work as possible to arrive at a valuable end-product. Methodologies such as Lean UX aim to design the best customer experience in the shortest cycle possible, but how do these approaches apply when it comes to executing and shipping a functional Minimum Viable Product? In this talk, designer Jono Mallanyk and software engineer Ben Burton delve into the hands-on approach they've taken to cross-functional pairing to design and build products quickly and effectively. They'll detail how and when to involve execution in the lean process and tools and techniques they've found useful for developers and designers working together. At Neo Innovation Labs, Jono and Ben have spent the past 12 months pairing as designer and developer, learning from each other, and honing their cross-functional process to arrive at a truly lean approach to software creation.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

The Two Burger Team – Cross Functional Pairing for MVPs

  1. 1. #twoburgerteam Photo credit: http://www.flickr.com/photos/snekse/2500327895/
  2. 2. #twoburgerteam Jono @jonomallanyk Ben @bjburton
  3. 3. VALUES PROCESS & CASE STUDY +
  4. 4. " If a tm c’t be f wh two pi, ’s o big. Jeff Bezos
  5. 5. " If yr MVP execu tm c’t be f wh two burgs, ’s o big. Jono Mallanyk
  6. 6. MVP?
  7. 7. An MVP   smat g y c do  make  r  dictly msu some fm  val  ng.
  8. 8. AN EVOLUTION OF PAIRING
  9. 9. AN EVOLUTION OF PAIRING
  10. 10. AN EVOLUTION OF PAIRING
  11. 11. GENERALISTS
  12. 12. PROXIMITY
  13. 13. WORK IN PARALLEL
  14. 14. Ga a sd ustg, n get  al  sn  psib.
  15. 15. TWO BURGER VALUES
  16. 16. BE CURIOUS EVERYONE SHOULD
  17. 17. GET OUT OF THE BUILDING EVERYONE SHOULD
  18. 18. SKETCH EVERYONE SHOULD
  19. 19. UNDERSTAND THE BUSINESS GOALS EVERYONE SHOULD
  20. 20. OPTIMIZE FOR LEARNING EVERYONE SHOULD
  21. 21. DESIGNERS SHOULD DEMYSTIFY THE PROCESS SHOW DESIGNS EARLY AND OFTEN
  22. 22. WRITE HTML & CSS (AT THE VERY LEAST) DESIGNERS SHOULD
  23. 23. DEPLOY TO PRODUCTION DESIGNERS SHOULD
  24. 24. NOT OVER-DESIGN DESIGNERS SHOULD
  25. 25. CARE ABOUT DESIGN: ASK WHY? DEVELOPERS SHOULD
  26. 26. NOT OVER-ENGINEER DEVELOPERS SHOULD
  27. 27. THROW OUT CODE DEVELOPERS SHOULD
  28. 28. INVOLVE YOUR TEAM EARLY PRODUCT MANAGERS SHOULD
  29. 29. FIND A WAY TO BE HANDS ON PRODUCT MANAGERS SHOULD
  30. 30. BUY BURGERS PRODUCT MANAGERS SHOULD
  31. 31. OUR MVP PROCESS
  32. 32. Probm: C we improve ships by lpg cps be crde ir sd spsibili?
  33. 33. INCEPTIONPhoto credit: http://muted.com/inception-totem/
  34. 34. FULL TEAM INCEPTION
  35. 35. Problem, vision & MVP idea
  36. 36. ASSUMPTIONS
  37. 37. DESIGN STUDIO
  38. 38. A “Wizard of Oz” MVP
  39. 39. BUILDING TOGETHER
  40. 40. CUSTOMER DEVELOPMENT
  41. 41. BURGERS
  42. 42. TWO BURGERS OF YOUR OWN WHAT’S NEXT?
  43. 43. #twoburgerteam Jono @jonomallanyk Ben @bjburton

×