bidd.pdf

(Business) Impact driven development is the approach of the new feature development, based on the analysis of the business benefits of the new functionality.

Transcript

1. Business analytics driven development Dmitry Salahutdinov metrics impact 1
2. Hey, my name is Dmitry + 2
3. AMPLIFR !3
4. Part 1: Introduce
 Business analytics !4
5. metrics ↗ “Trial to Payment” conversion ↘ “Paid users outflow” !5
6. Advanced analytics Payment funnel Trial Retention !6
7. Numbers are the only one truth Measure The only One Truth! Everyone in your team has own background and insights Business analytics works both: for developer & product owner !7
8. Example: Stick header & footer Average user screen height is ~600px !8
9. Example: Publication fails Error rates correlates with users outflow Scheduled Posts User outflow Let developers earn money by increasing code quality: Do refactoring legacy code and give back technical debt ☺ Failed !9
10. Part 2: requirements !10
11. Tracking events !11
12. Show graphical data, compare Data visualisation Scheduled Post Created Draft !12
13. Metadata Event metadata stores “as is” User metadata associates within current event Pass extra user & event data to analytics !13
14. Metadata usage Scheduled Post
 by user having Billing Plan “A” Scheduled Post
 by user having Billing Plan “B” !14
15. Multiple platroms support Mobile application Web(frontend/backend) !15
16. Track releases Release:
 feature deployment Release:
 feature improvement !16
17. Part 3: Instrumentation ⚒ !17
18. Amplitude !18
19. 10 millions events for free !19
20. Amplitude API !20
21. Backend integration Ruby sample Node JS Mobile !21
22. Frontend integration !22
23. Share user properties Render “backend” User properties Pass actual user properties With events !23
24. Part 4: empirical tips !24
25. verb + noun (e.g. 'clicked signup’) noun + verb (e.g. 'signup clicked') Naming Scheduled Post Draft created Save post saved Fail to post ... ... ✅ ❌ Event naming convention prevent entropy !25
26. Separate environments To keep experiments pure and prevent testing events mixing Overall data Testing data Very significant for low traffic experiments! !26
27. Organise events & properties And keep it simple !27
28. Part 5: Use cases !28
29. Existing feature analysis Start to collect metrics - measure feature performance - make a decision: improve or remove Measure business performance metrics before !29
30. New feature investigating/testing Start to collect metrics New feature deployment Ensure to have previous and next metrics collected !30
31. Incremental improvements Do small experiments with performance analysis !31
32. Part 6: workflow - For getting business impact !32
33. Success steps •Collect product metrics with analytics that is easy to use and accessible to everyone. •Analyze feature performance and user interaction with the product •Build predictions and hypotheses of features to increase key/financial application metrics •Monitor metrics changes after releases, repeat successful ones, increase expertise !33
34. Necessary conditions ✅ Ensure you have enough analytics before & after ✅ Traffic vs time ✅ Prevent hypothesis interception ✅ Overhead for small experiments !34
35. Part 5: Amplifr stories !35
36. Green errors 6%↗ post popup cancellation !36
37. Settings => Subscription ~20% Change Project Name => Activate Subscription Let just force people to change project name and earn !37
38. Collaboration feature visibility Unexpected ideas could work ↗ feature visibility with ugly ↗ adding another user ↗ billing plan 4 !38
39. For developers? get deeper to a business process essence 5 to increase developer culture (awareness of feature benefits) to reduce communication blockers (distributed teams) to motivate yourself Unique argumentation system to growth experience & expertise Do small experiments with performance analysis !39
40. Pet project? !40
41. SAINTPRUBY 30% discount coupon ❤ !41
42. Thank you ❤ @dsalahutdinov1 @dsalahutdinov https://dev.to/amplifr https://amplifr.com We are looking for passionate Ruby developer ❤ Write us to team@amplifr.com See you! !42