Know what (not) to build
0 likes•2,871 views
The document discusses lessons learned from a droidcon presentation on product development, emphasizing the importance of time management and user feedback in the agile process. It highlights the value of iterative testing, using A/B testing to refine features, and understanding user engagement through analytics. Challenges such as community building and the complexities of beta testing are also addressed, alongside practical strategies for measuring user flows and performance.
Know what (not) to build
- 1. Know what (NOT) to build Droidcon, 2015
- 2. Shem Magnezi @shemag8 | MyRoll
- 3. Usual scrum iteration Stories, backlog, implement, release
- 4. Merge moments Users wanted more control over our clustering Place your screenshot here
- 5. 3 days To implement with merge gesture 0.04% users Actually merged 0.2% users Used that feature
- 7. Was it worth it? Probably
- 8. Would we do it again? Absolutely not
- 9. ‘’ “Once you have a vision and your priorities articulated- then, as a leader, the most valuable asset you have, yes there’s money, yes there’s a lot of customers, yes there’s many valuable assets, but the most valuable in my opinion- is your time” Robert Kaplan, Professor of management at Harvard Business School
- 10. Build small & Learn fast
- 11. Build
- 12. Beta group Great integration with the Play Store
- 13. Beta problems 1. Not really heterogeneous 2. Takes time to build the community 3. Joining process might be tricky 4. They always NEED something
- 15. A/B testing It’s faster than arguing
- 16. github.com/shem8/ABTestingUtils public enum REGISTER_OPTION implements ABTestingEnum { //Will show 1 for 5%, 2 for 5%, 3 for 5% and disable for 85% of the users REGISTER1(0.05), REGISTER2(0.05), REGISTER3(0.05), NONE(0.85); private final double value; REGISTER_OPTION(double value) { this.value = value; } public double getValue() { return value; } } public REGISTER_OPTION getRegisterOption() { return getABTestingType(sharedPref, REGISTER_OPTION.class, "REGISTER_OPTION_KEY"); }
- 17. Learn
- 18. Get feedback 1. Use Google+ Communities (Beta) 2. Send an apk (that expires after some time) 3. Be clear on what you want to test 4. Get the right people 5. Treat feedback as opinions, not facts
- 19. Measure User flows, missing features and even performance
- 22. In house Quick N’ dirty
- 23. Analyze If you can’t bet on it you’re doing something wrong
- 25. Examples
- 29. Thanks! Any questions? You can find this presentation at: blog.myroll.com [email protected] Presentation template by SlidesCarnival | Photographs by Unsplash