Lean Features Development

Many teams in almost every company implement awesome features. They implement them to provide the best quality, to cover all the known possible scenarios and to enter into the market - and they believe they're going to work perfectly. The users will love it... right?

But the truth is, in most cases, things don't work as expected. Users do unpredictable things and the company could potentially waste a lot of time and resources on a feature that doesn't work.

I'll be telling you about some approaches and techniques that will help you to avoid these scenarios - and save some money in the process!

Transcript

1. Lean features development Alexis Santos
2. How many times a developer has to implement a feature that will be the next game changer?
3. Do you remember Google Wave?
4. Do you remember Google Wave?
6. Or Apple’s Ping?
7. Or Apple’s Ping?
9. If the biggest companies in the world sometimes fails, why wouldn’t we fail? “
12. Agenda • Build • Measure • Learn
13. Build
14. From developer point of view • Move fast • Unit tests • Automatic tests • Technical debts tasks • Release
15. • Also called MVP Minimum Viable Product
16. • Also called MVP • Only includes core part of the feature and no more Minimum Viable Product
17. • Also called MVP • Only includes core part of the feature and no more • Allows to verify correct or wrong assumptions Minimum Viable Product
18. • Also called MVP • Only includes core part of the feature and no more • Allows to verify correct or wrong assumptions • Accelerate learning Minimum Viable Product
19. • Also called MVP • Only includes core part of the feature and no more • Allows to verify correct or wrong assumptions • Accelerate learning • Is often less expensive to implement an MVP Minimum Viable Product
20. Is the smallest thing you can build that delivers customer value (and as a bonus captures some of that value back) Minimum Viable Product
22. Begins the learning process, rather than ending it “
23. When in doubt: simplify “
24. Use case: Lookalikes
25. Measure
26. Of course, you can’t measure if you don’t have a tool or SDK to report statistics In-House Solution
27. Some techniques that will help you to measure and compare features in your application
28. Split tests • Also known as A/B/C/… tests
29. Split tests • Also known as A/B/C/… tests • Different versions of the feature with identical purpose introducing variants between them
30. Split tests • Also known as A/B/C/… tests • Different versions of the feature with identical purpose introducing variants between them • Control the amount of users on every version
31. Split tests • Also known as A/B/C/… tests • Different versions of the feature with identical purpose introducing variants between them • Control the amount of users on every version • Test different hypothesis to detect the most effective
32. Use case: Own profile
33. Use case: Paywall
34. Remote feature flag/toggles Provides the ability to remotely control (enable or disable) features that are in production.
35. Learn
36. Is time to think if you want to discard or persevere
37. Discard the feature Is possible that the feature didn’t work well, in that case is time to think in removing it because is could be distracting the user
38. Tune the feature Use all the measurements, validate the results and tune the feature. Add possible modifications, improvements, polish UI, ...
39. Use case: Lookalikes
40. Use case: Lookalikes
41. Gain visibility Add more entry points placements
42. Use case: Female walkthrough Initial subtle entrypoint
43. Use case: Female walkthrough
44. Some extra tasks should be done before the next iteration
45. Don’t forget the technical debt • Maybe some technical debt was created during the implementation of the MVP
46. Don’t forget the technical debt • Maybe some technical debt was created during the implementation of the MVP • Do some extra clean up if possible
47. Don’t forget the technical debt • Maybe some technical debt was created during the implementation of the MVP • Do some extra clean up if possible • Split tests non-winner variants code to be removed
48. Summarize • Build ▪ MVP, start learning process • Measure ▪ Split tests, remote feature flags • Learn ▪ Discard or persevere ▪ Tech debt and clean up pending tasks
49. Thank you! Alexis Santos alexissp@corp.badoo.com