Download as PDF, PPTX
Uploaded byLukas Fittl
Lean Startup & UX for Agile Teams
This document outlines principles and techniques for lean startup and user experience work for agile teams. It emphasizes the importance of prioritizing ideas based on gathering customer information through qualitative and quantitative research methods. Teams are encouraged to focus on measurable outcomes over tasks, test ideas quickly through low-fidelity prototypes and experiments, and iterate work through fast weekly sprints of building, measuring, and learning. Cross-functional collaboration between business and development team members is also highlighted.
More Related Content
![[DevDay2019] Why you'll lose without UX Design - By Szilard Toth, CTO at e·pi...](https://cdn.slidesharecdn.com/ss_thumbnails/nicolaspython-devdaypresentationfinal-2-190412104945-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Lean Startup & UX for Agile Teams
Lean Startup & UX for Agile Teams
- 1. Lean Startup &UX for Agile Teams @LukasFittl
- 2.
- 3.
- 4.
- 5. When Agile isnot enough
- 6.
- 7. Which Idea? Idea Agile Development Release DidIt Have an Effect?
- 8. Which Idea? Idea Agile Development Release DidIt Have an Effect?
- 9. Wrong Idea. Idea Agile Development Release DidIt Have an Effect?
- 10. Wrong Idea. Idea Agile Development Release WrongIdea = Zero Business Impact No Effect.
- 11. Which Idea? Idea Agile Development Release DidIt Have an Effect?
- 12. Right Idea. Idea Agile Development Release DidIt Have an Effect?
- 13. Right Idea. Idea Agile Development Release DidIt Have an Effect?
- 14. Right Idea. Idea Agile Development Release WrongImplementation = Zero Business Impact No Effect.
- 15. Right Idea. Idea Agile Development Release NoEffect. Tweak It!
- 16. Making The RightFeature & Making The Feature Right
- 17.
- 18. Ship working software. Shipthe right software.
- 19.
- 20.
- 21.
- 22.
- 23. Prioriti zation Wrong Idea. Idea Agile Development Release WrongIdea = Zero Business Impact No Effect.
- 24. Prioriti zation When we Buildall ideas: Wrong Idea. Idea Agile Development Release No Effect. Wrong Idea. Idea Agile Development Release No Effect. Wrong Idea. Idea Agile Development Release No Effect.
- 25.
- 26. Prioriti zation Information Successful Has Potential Bad Idea OkIdea Great Idea We want Better Information about the Market, Customers, etc
- 27.
- 28. Quantitative Qualitative Generative Surveys Interviews Contextual Inquiry Mental Models Interviews DiaryStudies Evaluative Automated Card Sort Surveys Automated Studies Analytics A/B Testing Multi-Variant Testing Usability Testing Moderated Card Sort Wizard of Oz By @JohannaKoll, based on work by Janice Fraser, Nate Bolt & Christian Rohrer
- 29. Prioriti zation Who is thecustomer? Why do they care? What are they buying?
- 30.
- 31.
- 32.
- 33.
- 34. Prioriti zation Test Out beforeyou Build: Low-Fidelity Prototypes
- 35.
- 36.
- 37.
- 38. Prioriti zation Customer Interview (Paper) Prototype MVP “ThePerfect Product” Inside-the-Building Comfort Zone
- 39. Prioriti zation Get-out-of-the-Building Reality Customer Interview (Paper)Prototype MVP “The Perfect Product”
- 40.
- 42. 10.000 EUR /month
- 43. 10.000 EUR /month Jan 2014 Apr 2014 Jul 2014 Oct 2014 Jan 2015 Mar 2015
- 44. 10.000 EUR /month Jan 2014 Apr 2014 Jul 2014 Oct 2014 Jan 2015 Mar 2015
- 45. 10.000 EUR /month Task Task Task Task Task Task Jan 2014 Task Task Task Task Task Task T ask Task Task Task Task Task Task Apr 2014 Jul 2014 Oct 2014 Task Task Task Task Task Task Task Task Jan 2015 Mar 2015
- 46. INBOUND CHANNELS INCREASE ACQUISITION SEO RANKING Jan 2014 Apr2014 LANDING PAGE CONVERSION Jul 2014 Oct 2014 Jan 2015 Mar 2015
- 47. Focus on Outcome Focus onOutcomes, not Tasks.
- 48. Focus on Outcome Task: Build thenew Landing Page Outcome: Acquire 10 Customers / Week 20% Monthly Revenue Growth
- 49. Focus on Outcome Outcome 20% ActivationRate 40% Access it Daily Tasks
- 50. Focus on Outcome Each Ideashould have a Measurable Goal
- 51. Focus on Outcome A A R R R ACQ: Dowe have the right message? ACT: Do people use the product successfully? REV: Do people pay? RET: Do people come back? REF: Do people bring more people?
- 52. Focus on Outcome 5000+ EUR license 2-3weeks integration Look at your Financial Plan for Assumptions
- 53. Focus on Outcome Testing theOutcome
- 54.
- 55. Quantitative Qualitative Generative Surveys Interviews Contextual Inquiry Mental Models Interviews DiaryStudies Evaluative Automated Card Sort Surveys Automated Studies Analytics A/B Testing Multi-Variant Testing Usability Testing Moderated Card Sort Wizard of Oz By @JohannaKoll, based on work by Janice Fraser, Nate Bolt & Christian Rohrer
- 56.
- 57.
- 58. Test & Tweak Right Idea. Idea AgileDevelopment Release No Effect. Tweak It!
- 59.
- 60. Fast Iterations Faster iteration =trying more ideas. Speed of Iteration Your Runway
- 61.
- 62.
- 63.
- 64.
- 65. Wizard of OzMVP
- 66.
- 67.
- 68.
- 69.
- 70. “Business people anddevelopers must work together daily throughout the project.” - Agile Manifesto
- 71. Every team hasOwnership of a part of the product
- 72. Cross-functional is abad name. It's about reducing dependencies: Teams acting without asking for permission. #autonomy - Anders Haugeto @ Iterate.no https://twitter.com/hauge2/status/274082772589633536
- 73.