1 / 22

enabling lean with tech lessons learned applying lean at paypal

enabling lean with tech lessons learned applying lean at paypal. bill scott (@billwscott) sr. director, user interface engineering, paypal Lean Startup in the Enterprise. The Lean Startup Conference with Jeff Gothelf. Dec. 4, 2012. San Francisco, CA.

coby
Télécharger la présentation

enabling lean with tech lessons learned applying lean at paypal

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. enabling lean with techlessons learned applying lean at paypal • bill scott (@billwscott) • sr. director, user interface engineering, paypal • Lean Startup in the Enterprise. The Lean Startup Conference with Jeff Gothelf. • Dec. 4, 2012. San Francisco, CA

  2. at Netflix 90% or more of the “ui bits” were thrown away every year.doesn’t take too many tests to result in lots of throw away code. followed buid/test/learn designed for volatility

  3. new dna @paypal • march 2012 • david Marcus becomes president of PayPal • april 2012 • we form lean startup team to reinvent checkout experience

  4. in the midst of transformation

  5. tangled up technology • big problem. technology and processes not geared to build/test/learn.

  6. a tale of two stacks • two non-standard stacks • new stack tied to Java • “one word” change could take 6 weeks to fix long release cycles non-standard UI non-standard UI xml jsp c++ java old new

  7. leave the old behind • we can rule out the old stack X non-standard UI non-standard UI xml jsp c++ java old new

  8. need to design for volatility • but still the new stack is not conducive to prototyping • follows an “enterprise application” model. ui gets built into the “app” prototyping is hard non-standard UI jsp “ui bits” could only live here java

  9. 1. set the ui bits free

  10. separate the ui bits • engineered the user interface stack so that the only artifacts are: • javascript • css • images style = CSS images templates = JS code = JS

  11. separate the ui bits • templates get converted to javascript • <p>Hello {name}</p> • we use dust.js style = CSS images templates = JS code = JS JavaScript

  12. separate the ui bits • language independent • server/client agnostic • CDN ready • cacheable • rapid to create style = CSS images templates = JS code = JS

  13. make the ui bits portable • JS templating can be run in client browser or server on the production stack • we can drag & drop the ui bits from prototyping stack to the production stack open source JS template open source JS template open source JS template node.js java prototype stack production stack

  14. style = CSS images free to work together templates = JS code = JS node.js co-located lean ux team whiteboardto code code to usability user interfaceengineers usability/customers product/design team

  15. free to turn sketch to code • forcing function. • it brings about a close collaboration between engineering and design • it creates a bridge for shared understanding • requires a lot of confidence and transparency

  16. free to test frequently with users

  17. free to iterate independent of agile usability usability usability usability usability lean ux - lean team track user interface engineering - agile scrum team { agile sprint 0 engineering - agile scrum team release release release release

  18. 2. embrace open source

  19. use open source religiously

  20. work in open source model • internal github revolutionized our internal development • rapidly replaced centralized platform teams • innovation democratized • every developer encouraged to experiment and generate repos to share as well as to fork/pull request

  21. give back to open source • we have a string of projects that will be open sourced • node bootstrap (similar to yeoman) • contributions to bootstrap (for accessibility) • contributions to bootstrap (for internationalization) • component repository framework for github (similar to bower) • and more...

  22. 1. set the ui bits free2. embrace open source

More Related