Running lean startup with agile 20130810

2,040 views

Published on

Introduction to Agile in Lean Startup context.

Published in: Technology

Running lean startup with agile 20130810

  1. 1. Running Lean Startup with Agile kulawat@proteus-agility.com amp.tanawat@proteus-tech.com SIPA Angel in The City Aug 10, 2013
  2. 2. http://vizualize.me/kulawat Agile Coach Goes Entrepreneur Found Proteus Agility Eidos, Humane Software for Human Agile66 Founder Dad of a 3-Year-Old Rebellious Son
  3. 3. Amp Intro
  4. 4. Agile is Culture - Eidos , Disruptive Agile Tool - Share our culture/experience - Aki Story
  5. 5. Warm Up ● Line up based on How much you know about Agile? ○ 1 - Never heard of it ○ 5 - I should teach this class ● Write down and read aloud ○ Nickname ○ Team ○ What is your pain point in software development? ● Count to 3, Go!
  6. 6. Outline ● Why Lean Startup needs Agile? (1h) ● Agile Lego Workshop (2h) ● Lunch Break (1h) ● Practical Agile Management Practices for Startup (1.5h) ● Agile Technical Practices for Scalable Startup (1.5h) ● Feedback Tools for Startup (0.5h) ● Wrap-Up
  7. 7. Note Before We Start ● It takes me 3 years to start to “get” Agile ● Interrupt me to ask questions any time ● The more you ask, the more you get ● Focus on WHY, not HOW
  8. 8. Why Lean Startup Need Agile? 60m
  9. 9. What is a Startup? “A startup is an organization formed to search for a repeatable and scalable business model” [Steve Blank] “A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty” [Eric Ries]
  10. 10. http://startupweekend.org/
  11. 11. What is your Lean Startup? http://thebln.com/ 5m
  12. 12. The Lean Startup Video by Joone Studios (2:29m) http://www.youtube.com/watch?v=WAdikBfKeD8
  13. 13. What is Lean Startup? http://theleanstartup.com/ Loop as fast as possible!
  14. 14. Problem & Solution Problem Known Known Unknown Solution Known Unknown Unknown Product Manager Product Owner Customer Development Waterfal Agile Agile
  15. 15. http://images.nationalgeographic.com/ AGILE? 5m
  16. 16. 12 Agile Principles Customer is Priority Welcome Change Deliver Frequently Business & Dev Together Trust the Team Face-to-Face Measure with Working Software Sustainable Pace Good Design Simplicity Self Organized Team Retrospect Regularly http://agilemanifesto.org/
  17. 17. We are uncovering better waysof developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan http://agilemanifesto.org/ “The Agile Manifesto”
  18. 18. Why Lean Startup Need Agile? 5m
  19. 19. Why Agile? AGILITY Loop as fast as possible!
  20. 20. Agile Lego Workshop Startup Edition - 120m
  21. 21. Agile Lego ● To build “a city” as a product to sell to a customer ● Work as a team ○ Pre-Game - 45m ■ Organize Your Team (5m) ■ Customer Interview (15m) ■ Release Plan (25m) ○ 3 Iterations - 60m ■ Build - Iteration Plan (3m) & Build (7m) ■ Measure - Iteration Review (5m) ■ Learn - Retrospective (5m)
  22. 22. Agile Lego Rules Buildings MUST be built by LEGO bricks Customers will pay for your product with LEGO bricks
  23. 23. Organize Your Team - 5m ● 3 teams based on “the number” ● Roles? ● Process? ● Team Name? Join hands and shout it!
  24. 24. Customer Interview - 15m ● Write these basic requirements on sticky ○ House 1 ○ House 2 ○ House 3 ○ School ○ Hospital ○ Fire Station ○ Park ● All teams ask the customer more questions to find out more about what he wants. ● Each team should have around 12-15 cards Park blank square you can take some note here
  25. 25. Release Plan (25m) Estimation fruit 1 fruit 2 fruit 3 fruit 4 5 ● Pick Five Fruits ● Pick Second Smallest Story ● 1,2,3,5 ● Hand Vote ● Write Down Estimation Wall
  26. 26. Release Plan (25m) Prioritization release backlog iteration 1 iteration 2 iteration 3 sum = x x 1 2 3 ● sum total points ● pick stories for 3 i ● estimate velocity ● draw burndown ● draw projection to do doing done learned top priority
  27. 27. Build - Iteration Plan (3m) release backlog iteration 1 iteration 2 iteration 3 sum = x x 1 2 3 to do doing done learned
  28. 28. Build - Build (7m) http://ourlegocity.files.wordpress.com/2010/02/img_0524.jpg
  29. 29. Measure - Iteration Review (5m x3) ● Present your city to the customers, one team at a time ● Find out if your customer will pay for any of your card ● Decide if each card is “learned” and update burndown accordingly
  30. 30. Learn - Iteration Retrospective (5m) Good Bad Try ● 2m Good/Bad/Try ● 1m 3-Dot Vote ● 2m Pick 1 Iteam
  31. 31. Closing Thoughts ● One-Word Feeling ● Key Takeaway
  32. 32. BREAK
  33. 33. for Startup - 90m Practical Agile Management Practices
  34. 34. ● Daily Standup Meeting ● User Story ● Hypothesis ● Planning Poker ● Iteration ● (Retrospective) Practical Agile Management Practices
  35. 35. Daily Standup ● Pattern ○ What did I do? ○ What will I commit to do? ○ Will problems are blocking me? ● Typically ○ 15 min ○ In front of the board or just form circle ○ works with remote team (with TC, e-board)
  36. 36. Daily Standup ● When it is done right ○ Fun ○ Team Building ○ Rhythm ○ Happen with or without the boss ● Watch Out For ○ Status Report - “Avoid Eye Contacts” ○ Talking Too Long - “Take It Off-Line”
  37. 37. 4 Volunteers & Observers 5m ● 4 volunteers + 2 coach ○ talk about real work ○ pretend it is the same project ● other observes ○ take it offline ○ avoid eye contacts
  38. 38. WHY? 5m
  39. 39. User Story - a Template As a (WHO , Persona) I want (WHAT, Small Feature) So that (WHY, Reason)
  40. 40. User Story - exercise 5m Write the story of adding the Twitter registration ● write story ● pick the best one from the group ● read it out loud
  41. 41. User Story - example As a potential user, I want to register using twitter so that I don’t have to fill out a registration form. http://www.infoq.com/presentations/Questions-Stories
  42. 42. User Story - exercise 5m In group, write high-level test cases for this story ● write test cases ● read it out loud
  43. 43. User Story - Acceptance Acceptance Criteria ● testable condition ● manual test steps ● or even better be automated (BDD, ATDD) ● just free style ● or a Template ○ Given [initial context], ○ when [event occurs], ○ then [ensure some outcomes]
  44. 44. User Story - Acceptance Acceptance Criteria Example ● Twitter registration icon is the same size as Facebook ● Given a new user, when the user register with their Twitter account, then the user should be able to register ● Given existing user, when the user register with their Twitter account with associated existing email, the user account should be linked with this Twitter account ● Given existing Twitter linked account, when the user register with the same Twitter account, the user should be alerted with “duplicated account” message
  45. 45. User Story - Characteristic Independent Negotiable Valuable Estimable Small Testable http://emmottontechnology.com/wp-content/uploads/2012/06/cut-cake-de-5170669.jpg
  46. 46. http://www.agilemodeling.com/artifacts/userStory.htm http://theeidos.com/
  47. 47. http://nigelshaw.files.wordpress.com/2010/04/042710_0014_nowonderagi121.png?w=540 http://theeidos.com/
  48. 48. User Story - Benefits Independent -> Prioritization Negotiable -> Flexibility Valuable -> Customer Focus Estimable -> Predictability Small -> Early Feedback Testable - Clear
  49. 49. User Story - Essence Card Conversation Confirmation
  50. 50. WHY? 5m
  51. 51. Who write User Story? ● Traditional Agile (Scrum) relies heavily on Product Owner or “specific” small number of customers. ● What about Startup with mass customers? http://corradosimeoniparis.files.wordpress.com/2010/07/christ-in-the-crowd-2005-oil-on-panel-cm-50-x-40.jpg
  52. 52. Hypothesis ● Value of the user (WHY) in User Story does not necessary mean value for business! ● Customers may like it but will it make money? ● Everything in Startup is Hypothesis ● Turn Story to Hypothesis in 3 steps
  53. 53. STEP 1 : Add ? As a potential user, I want to register using twitter so that I don’t have to fill out a registration form? http://www.infoq.com/presentations/Questions-Stories
  54. 54. STEP 2 : Ask Whys ● Increase # registrations? ● More social media penetration for marketing? ● Allow notification features? http://www.infoq.com/presentations/Questions-Stories
  55. 55. STEP 3 : What’s our hypothesis? Allowing users to register with twitter will <do something measurable> http://www.infoq.com/presentations/Questions-Stories
  56. 56. STEP 3 : What’s our hypothesis? Allowing users to register with twitter will drop abandoned registrations by 5% http://www.infoq.com/presentations/Questions-Stories
  57. 57. Paradigm Shift TO DO DOING DONE (HYPOTHESIS) VALIDATED Working software over comprehensive documentation LEARNING over
  58. 58. WHY? 5m
  59. 59. Agile Estimating ● Accurate Estimation is Oxymoron English! ● Plans are worthless, but planning is everything” Dwight D. Eisenhower ● “Creative processes are not easily planned, and so predictability may well be an impossible target.” The New Methodology ,Martin Fowler
  60. 60. Agile Estimating Group Estimating 5m ● Absolute ● Relative ● We Suck!
  61. 61. Agile Estimating Story Point ● Measure Relative Complexity ● Include Entire Team Efforts ● Avoid Precision ● Prevent “Manager Math”
  62. 62. 10m Volunteer & Observe
  63. 63. Planning Poker ● Tool for Estimating ● Encourages Full Team Participation ● Builds Rapid Consensus ● Quick on Easy Story ● Fun! Sequence which prevents arguments over a tiny estimate difference. ○ Fibonacci : 1, 2, 3, 5, 8, 13, 21, etc… ○ Mike Cohn's : 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100, ? ○ Simple : 0, 1, 2, 3, 5, 8, BIG
  64. 64. WHY? 5m
  65. 65. Agile Project Rhythm Plan Code & Test Review & Retro 0.5 day 0.5 day 9 days a 2-Week Iteration Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Iteration 6 a 3-Month Release more than iterative - prioritized - welcome change - inspect & adapt
  66. 66. Release Planning http://www.mountaingoatsoftware.com/uploads/blog/Index-Card-Stack.jpg i1 i2 i3 i4 i5 100 pts Release Burndown Chart i6 top priority more detail
  67. 67. Real Life!
  68. 68. Iteration - Time-Boxing Time People Scope (prioritized) Time-Boxed HobbyTime-Crunched Unknown Cost
  69. 69. Iteration ● Shorten Feedback Loop ● Focus ● Reduced Risk ● Inspect and Adapt ● Done-Done, not just a phase traditional agile Effort Time
  70. 70. WHY? 5m
  71. 71. Agile Technical Practices for Scalable Startup - 90m
  72. 72. AndroidWinXPWin7 MacMiniServer OSXMountainLion(10.8) VMware Fusion Android Developer Tools
  73. 73. Continuous Delivery
  74. 74. ? || /* */
  75. 75. for startup - 30m Feedback Tools
  76. 76. Feedback Tools Qualitative ● Customer Interview ● DIY Usability Test Quantitative ● Google Analytic ● MixPanel
  77. 77. DIY Usability Test
  78. 78. DIY Usability Test ● Easy & Cheap ● A Morning A Month ● Start earlier than you think makes sense ● Test other people’s sites ● Tester does not have to match your target ● Three testers is enough for each test ● Make the tasks into scenarios ● Give your tester small thanking you gift
  79. 79. DIY Usability Test FACILITATOR = TOUR GUIDE + THERAPIST THINK OUT LOUD QUIET ROOM
  80. 80. Test Script ● Welcome (4m) ● Pre-Test Questions (2m) ● The Home Page Tour (3m) ● The Tasks (35m) ● Probing (5m) ● Wrapping Up (5m) ● Prepare For The Next Test (10m)
  81. 81. “SEEING IS BELIEVING”
  82. 82. DIY Usability Test ● Debrief ● Take on the worst first!
  83. 83. DIY Usability Test ● Volunteer 1 tester ● Eidos Usability Test a. Sign up at http://theeidos.com/ b. Create a project c. Add john@theeidos.com and paul@theeidos.com to your project d. Create a story on the storyboard of your iteration 1 10m
  84. 84. Vanity vs Actionable Metric something that always goes up t Vanity Metric
  85. 85. Vanity vs Actionable Metric http://practicetrumpstheory.com/2010/07/3-rules-to-actionable-metrics/
  86. 86. Vanity vs Actionable Metric http://practicetrumpstheory.com/2010/07/3-rules-to-actionable-metrics/
  87. 87. MixPanel - Funnel
  88. 88. MixPanel - Retention
  89. 89. Retrospective ● Critical to Agile team ● Easily ignored ● Easy to do ● Challenging for team with blame-culture 5m Pretend you are the trainers and do retrospective for this course
  90. 90. Final Thought
  91. 91. Final Thought http://www.hhar.ie/wp-content/uploads/relay-2.jpg
  92. 92. Final Thought http://answers.bettor.com/images/Articles/thumbs/extralarge/UAB-women-volleyball-team-receive-two-more-players-for-2012-season-Volleyball-news-162802.jpg
  93. 93. Good Reads
  94. 94. theeidos.com

×