Right Product and Process - When time is limited - Ncell App Camp 2015

The technology and the development will be driven by whether the app is going to be used by 100 or 1 million users in one to three months. Technology, scalability and performance are important but might not be of that significance at the initial phase of Ncell App Camp 2015. How do one decide that? How do one decide how much features he/ she should include to ensure that his/ her app is usable and complete in a month time. Anjesh highlighted key points that participants should keep in their minds during app development for the challenge and gave them some ideas to avoid premature optimization and over-engineering.

Transcript

1. Right  Product   and  Process   when  the  Time  is  Limited   Anjesh  Tuladhar   YoungInnova;ons  
2.   How  long  does  it  take  for  the    good   so&ware  to  develop?  
3. The  answer  is  lot  of  Time  
4. •  To  develop  the  right  product  especially  when   we  have  limited  ;me   – What  is  the  best  way?   – What  are  the  things  we  need  to  keep  in  mind?   – What  is  the  right  product?  
5. A  case  on  E-­‐bay   •  American  mul;-­‐na;onal  ecommerce  company   •  Established  year:  1995   •  2014  Revenue:  $  17.90  billion   •  2014  Employees:  34,600   hSps://en.wikipedia.org/wiki/EBay  
6. Ebay:  Evolvement  over  ;me   1995  –  set  of  perl  scripts  build  over  a  weekend     1997  –  replaced  with  C++  system     2002  –  rewriSen  in  java   The  right  architecture  to  support  1995  ebay  is  not  going  to  be   the  right  one  for  2002  ebay  or  2015  ebay  
7. Growth  of  Ebay  Users  
8. MVP  –  Minimum  Viable  Product     •  Minimum  viable  product  is  the  small  thing  you   can  build  that  delivers  the  customer  value   •  Analyse  each  feature  and  ask  what  if  I  take  it   out  
9. Pareto  Principle  in  MVP   •  Pareto  Principle  =  80/20  Rule     –   80%  of  your  product  values  is  delivered  by  20%  of   its  features.     What  are  those  20%  of  your  features?  
10. Technology   •  Technology  is  the  core   •  Just  remember   – No  over-­‐engineering  
11. Process   •  Source  code  versioning   •  Tests   •  Deployment  strategy   •  Staging  and  demo  servers   •  Code  Quality   •  Excep;on/error  handling   Nobody  is  going  to  ask  you  and  see  if  you  are  following  these   process.  It’s  for  you  –  only  you.  
12. Source  code  versioning   •  Make  sure  you  always  have  the  good  commit   to  come  back  to    
13. Tests   •  100%  coverage  is  not  needed,  but  make  sure   that  the  key  func;ons  have  unit-­‐tests   hSp://code.tutsplus.com/tutorials/the-­‐newbies-­‐guide-­‐to-­‐test-­‐driven-­‐development-­‐-­‐net-­‐13835  
14. Deployment  strategy   •  Use  Staging  and  development  servers   •  Use  scripts  (capistrano,  custom  scripts)  to   deploy   Problems  happen  to  everyone,  especially  when  you  have   rushed  deadlines.  
15. Code  Quality   •  Nobody  is  going  to  give  you  low  grade  if  you   have  bad  code  quality  but  you  will  get   punished    in  the  long  run  
16. Code  Quality   Con;nuously  measure  and  track  your   code  quality  
17. Code  quality  –  Lint  for  Android   hSp://developer.android.com/tools/debugging/improving-­‐w-­‐lint.html  
18. Excep;on/error  handling   •  Errors  are  part  of  your  applica;on.     •  Does  your  applica;on  handle  the  errors  well?   •  Do  you  think  your  user  will  come  back  to  use   your  buggy  app?  
19. Excep;on/error  handling   Say  goodbye  to  bugs.   Deep,  ac;onable  insights  let  you  pinpoint   and  fix  issues.  
20. A  quick  recap   •  Good  sokware  takes  a  lot  of  ;me  to  develop   fully   •  We  don’t  have  ;me  and  millions  of  users  yet   •  Define  MVP   •  Develop  without  gelng  very  deep  into   technology  and  over-­‐engineering   •  Follow  fundamental  process  
21. Thank  you