lean ux pyramid

Download Lean UX Pyramid

Post on 05-Dec-2014

1.080 views

Category:

Technology

0 download

Embed Size (px)

DESCRIPTION

Palestra proferida por Tiago Silva da Silva (@tiagosdasilva) e Samuel Crescêncio (@screscencio) no Agile Brazil 2013.

TRANSCRIPT

  • 1. Lean UX Pyramid A practical case of applying Lean and UX principles to develop a product with a revolutionary user experience Samuel Crescncio @screscencio Tiago Silva da Silva @tiagosdasilva Friday, 28 June, 13
  • 2. SAMUEL CRESCNCIO 20 years in the software industry BA / AA Friday, 28 June, 13
  • 3. TIAGO SILVA DA SILVA Agile UX PhD Friday, 28 June, 13
  • 4. THEME Ongoing work Friday, 28 June, 13
  • 5. A practical case of applying Lean and UX principles to develop a product with a revolutionary user experience THEME Lean UX Pyramid Friday, 28 June, 13
  • 6. Friday, 28 June, 13
  • 7. Friday, 28 June, 13
  • 8. Friday, 28 June, 13
  • 9. A Practical Case Study Friday, 28 June, 13
  • 10. 2 years of continuous improvement applying the Lean Pyramid and UX Principles Friday, 28 June, 13
  • 11. Started from an innovation process; FirstVersion in RubyOnRails; Market opportunity: Existing tools were having a hard time to enter in Brazilian Market - Customers valued what weve done: Market Picture: ~250 competitors world wide a handful of them market leaders 200+ competing on price with little differentiation generally providing bad service; Existing solutions were heavy, hard to use, expensive and more like a white elephant OK, but why did we decide to build OnTrack? Friday, 28 June, 13
  • 12. And we knew we could do better! THE COMMON BELIEF Friday, 28 June, 13
  • 13. STARTED WITH Strong leadership: Product Champion Technical Leader THE BEGINNING Friday, 28 June, 13
  • 14. From the very beginning weve heard and observed our usersand have applied LEANand UX techniques to validate our ideas in the most effective and inexpensive possible way. THE BEGINNING Friday, 28 June, 13
  • 15. 4 SIMPLE PREMISSES Simple Easy to Use Totally Effective Elegant THE COMMON SHAREDVISION Friday, 28 June, 13
  • 16. WE AIMED: To boost collaboration THE COMMON SHAREDVISION Friday, 28 June, 13
  • 17. WE AIMED: Non Intrusive communication THE COMMON SHAREDVISION Friday, 28 June, 13
  • 18. WE AIMED: unprecedented traceability THE COMMON SHAREDVISION Friday, 28 June, 13
  • 19. WE AIMED: Revolutionary Usability (keyboard shortcuts) (undo/redo capacity) (no cruds) THE COMMON SHAREDVISION Friday, 28 June, 13
  • 20. WE AIMED: Mind Map like Tree Editing to manage scope THE COMMON SHAREDVISION Friday, 28 June, 13
  • 21. WE AIMED: Rich Single Page Web App THE COMMON SHAREDVISION Friday, 28 June, 13
  • 22. WE AIMED: To require no more than 10 minutes to be learned THE COMMON SHAREDVISION Friday, 28 June, 13
  • 23. WE AIMED: To require no technical support THE COMMON SHAREDVISION Friday, 28 June, 13
  • 24. WE AIMED: To require absolutely no conguration (ready to go out of the box, you just use it) THE COMMON SHAREDVISION Friday, 28 June, 13
  • 25. WE AIMED: To be resilient to different business scenarios capable of being deployed onDemand and OnPremisse THE COMMON SHAREDVISION Friday, 28 June, 13
  • 26. WE AIMED: To design everything with the user in mind User-Centered Design THE COMMON SHAREDVISION Friday, 28 June, 13
  • 27. The next step was to nd the right technology to build it. We decided by GWT THE TECHNOLOGY Friday, 28 June, 13
  • 28. To support all those premisses and goals we had to develop a robust architecture: Should be Fast, Reliable and Scalable Should not be dependent on Network/Server latency as we didnt want to let the user waiting. THE ARCHITECTURE Friday, 28 June, 13
  • 29. In order not to let the user waiting, we needed the entire model in each client, keeping it sync while processing transactions THE ARCHITECTURE Friday, 28 June, 13
  • 30. The solution: A Thick smart client with an asynchronous distributed architecture. THE ARCHITECTURE Friday, 28 June, 13
  • 31. THE ARCHITECTURE Friday, 28 June, 13
  • 32. Syncing Services Syncing Services provided Mode Availability; We decided by the command pattern providing an abstraction for actions; Actions are maintained in stacks; Small cheap diffs for actions provided undo/redo, collaboration, easy conict detection and treatment, accounting and traceability; The execution of actions are the only thing that can modify the model, providing model integrity; The code for syncing is the same for the client and the server, once again providing integrity; THE ARCHITECTURE Friday, 28 June, 13
  • 33. Actions are all stored with version control, enabling the recovery of the state of the model at any given point in time providing unprecedented traceability; Any new implementation will take advantage of all past data; Snapshots are used as cache to reduce processing when load a state (all lazy loading); The client UI is updated as fast as possible so the user does not need to be waiting for AJAX callbacks; Server validations assure model consistency and together with conict management and server push capabilities can provide a secure and reliable platform for intense collaboration; BENEFITS OF THE ARCHITECTURE Friday, 28 June, 13
  • 34. SCOPE TREE @ - DELIVERY TREE % - PROGRESS $ -VALUE # - EFFORT ! - IMPEDIMENT A FEW CONCEPTS FOR USER EXPERIENCE Friday, 28 June, 13