Your SlideShare is downloading. ×
0
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
The Two Burger Team – Cross Functional Pairing for MVPs
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

The Two Burger Team – Cross Functional Pairing for MVPs

772

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 …

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
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
772
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×