Lean Software Development

1,255 views

Published on

Talking Lean Tel Aviv meetup 5-Jan-2014 by Boris Nadion.

How I learned to stop worrying and stay focused on the product.

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,255
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
17
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Lean Software Development

  1. 1. Lean Software Development Boris Nadion boris@astrails.com @borisnadion
  2. 2. Boris Nadion developing software since early 90s participated in over 100 web and mobile projects since 2005 partner at Astrails
  3. 3. idea coffee shop napkin sketches
  4. 4. thousands of users
  5. 5. idea launch success
  6. 6. idea launch success failure
  7. 7. idea launch success failure
  8. 8. idea launch success
  9. 9. launch success
  10. 10. idea launch many ways to get from an idea to a launch
  11. 11. Lean Software Development
  12. 12. How I Learned to Stop Worrying and Stay Focused on the Product http://www.imdb.com/media/rm1366197248/tt0057012?ref_=ttmi_mi_all_sf_6
  13. 13. learned
  14. 14. SE7EN http://en.wikipedia.org/wiki/Lean_software_development
  15. 15. obvious amplify learning empower the team build integrity in see the whole
  16. 16. amplify learning
  17. 17. empower the team http://www.projectsherpa.com/blog/developers-dont-need-to-know-the-product/
  18. 18. build integrity in
  19. 19. see the whole
  20. 20. not obvious eliminate waste deliver as fast as possible decide as late as possible
  21. 21. eliminate waste
  22. 22. deliver as fast as possible
  23. 23. decide as late as possible
  24. 24. how to start 1-pager document: problem, solution, product
  25. 25. scope a few pages document
  26. 26. iA Writer
  27. 27. content creation flow see the whole
  28. 28. estimate what budget will be required
  29. 29. eliminate waste
  30. 30. pages/screens definitions workflowy.com, hackpad.com
  31. 31. wireframes
  32. 32. test flows on wireframes
  33. 33. designer key pages
  34. 34. user stories trello.com, pivotaltracker.com
  35. 35. example • users should be able to login and register with • • • Facebook users should be able to add a package with a tracking number PACKAGE UPDATES NOTIFICATION EMAILS
  36. 36. decide as late as possible
  37. 37. trello column = story state icebox backlog pending staging/testing accepted rejected production
  38. 38. closed loop deliver as fast as possible
  39. 39. write some code
  40. 40. code review github.com pull requests circleci.com, codeclimate.com build integrity in
  41. 41. staging deployment
  42. 42. acceptance testing manual
  43. 43. automatic/regression testing unit/functional, integration for critical paths
  44. 44. refactoring never have time for this shit
  45. 45. maintainability build integrity in
  46. 46. technical debt comes with an interest rate
  47. 47. refactoring return the debt
  48. 48. launch not a date, but completeness of the feature set http://www.flickr.com/photos/cobalt/6162053776/
  49. 49. fun begins
  50. 50. launch success
  51. 51. new feature lifetime • discussion • wireframes or/and designs • testable user stories • development and reviews • staging deployments • acceptance testing • production deployment
  52. 52. not obvious eliminate waste deliver as fast as possible decide as late as possible
  53. 53. success
  54. 54. Thank You! Boris Nadion boris@astrails.com @borisnadion

×