Startup Engineering & Operations
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Startup Engineering & Operations

  • 1,714 views
Uploaded on

We presented a method of focusing a web startup engineering team on finding a must have use case for the company's product. At least one must have use case is needed for a technology company to......

We presented a method of focusing a web startup engineering team on finding a must have use case for the company's product. At least one must have use case is needed for a technology company to achieve a product market fit. The engineering team would build an environment of rapid iteration toward this goal.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,714
On Slideshare
1,714
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
8
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Dev  &  Ops   for  Lean  Startups   Alex  Shers*nsky   V.P.  of  Product  Development,  CatchFree,  Inc.   ashers*nsky@catchfree.com  |  @AlexShes*nsky       MuckerLab   February  28,  2012       Copyright  CatchFree,  Inc.  3/1/12   1     Prepared  for  MuckerLab  
  • 2. Quick  Intro  •  MustHave  Score  measures  product  market  fit   –  Iden*fies  your  product’s  “Must  Have”  use  cases   –  Helps  tech  companies  guide  product  development   and  grow  the  legions  of  authen*c  evangelis*c  users   –  Basic  service  is  FREE  at  www.musthavescore.com   Copyright  CatchFree,  Inc.   3/1/12   2   Prepared  for  MuckerLab  
  • 3. Target  Audience  •  Web  soUware/services  startup  •  Low  technical  risk  •  Strong  all-­‐around  engineers  •  Funding  for  9  months   Copyright  CatchFree,  Inc.  3/1/12   3   Prepared  for  MuckerLab  
  • 4. Goals  •  Goal  1:  Get  to  product  market  fit   – Build  MVP  (minimum  viable  product)   – Facilitate  learning   – Speed   – Cost  control  •  Goal  2:  See  Goal  1   Copyright  CatchFree,  Inc.  3/1/12   4   Prepared  for  MuckerLab  
  • 5. Process  •  Market-­‐focused,  service-­‐oriented  engineering  culture  •  No  development  without  requirements  •  MVP  mindset  (enough  to  validate  value  proposi*on)  •  Rigorous  priori*za*on  (no  “nice  to  have”  features)  •  Rapid  itera*ons  to  learn  “compelling  reasons  to  use”   Copyright  CatchFree,  Inc.  3/1/12   5   Prepared  for  MuckerLab  
  • 6. Example  Service  Arch.  for  MVP   Copyright  CatchFree,  Inc.  3/1/12   6   Prepared  for  MuckerLab  
  • 7. Components   (overview)  •  Uniform  environments   –  development,  tes*ng,  produc*on,  demo/staging  •  Con*nuous  deployment  •  Usability  tes*ng  •  Metrics,  analy*cs  •  Customer  feedback,  surveys  •  Virtualized  hos*ng  •  Automa*c  provisioning  of  servers  •  Produc*on  monitoring,  aler*ng,  &  recovery   Copyright  CatchFree,  Inc.  3/1/12   7   Prepared  for  MuckerLab  
  • 8. Design  for  Speed  of  Learning  •  Con*nuous  integra*on/deployment   –  From  check-­‐in  to  produc*on  in  minutes  –  mul*ple  itera*ons  every  day   –  Engineers  constantly  release  func*onality  to  produc*on   –  Stability  through  automated  tests  •  Learning   –  Capture  &  report  on  funnels  for  product   market  fit  &  general  web  analy*cs   –  A/B  tes*ng  •  Maintain  automated  tests  only  for  the  Must  Have  use  cases   –  Allows  for  fast  itera*on  w/o  compromising  quality  where  it  mahers  most   Copyright  CatchFree,  Inc.   8   Prepared  for  MuckerLab  
  • 9. Design  for  Nimble  OperaNons  •  Applica*on  Hos*ng:  Use  cloud  service  provider   –  All  servers  in  the  cloud  –  easy  to  set  up  &  low  setup  costs   –  Fast  &  cost-­‐effec*ve  to  scale  when  needed  •  Capacity  Scaling:  Automa*c  Resource  Configura*on   –  Brings  up  addi*onal  server  in  minutes   –  Instrumental  for  recovery  or  changing  service  provider   •  Reliability:  Monitoring  &  Alerts   -  Automa*c  recovery   -  Hands-­‐off  opera*on   -  Allows  planning  ahead     Copyright  CatchFree,  Inc.   9   Prepared  for  MuckerLab  
  • 10. Some  Specific  Choices   (most  Open  Source)  •  Basic  Tools  &  Technologies   –  CentOS  Linux;  Ruby/Rails;  MySQL;  Memcached;  Apache;  NGINX;  Solr  •  Development  Environment   –  Mac  OS;  Git;  GitHub*   –  Business  Gmail*;  Skype;  Social  Cast,  Yammer;  Bugzilla;  Pivotal  Tracker*  •  Test   –  Selenium  •  Con*nuous  Deployment   –  Capistrano;  JetBrains/TeamCity*  •  Hos*ng  &  Provisioning   –  DNS  Made  Easy*;  Linode,  Rackspace,  Amazon,  Heroku;  Opscode/Chef*  •  Monitoring   –  Munin;  Nagios;  Monit  •  Tracking,  Usability  Tes*ng,  Learning,  Feedback   –  KISS  Metrics;  Google  Analy*cs;  UserTes*ng;  MustHave  Score   Copyright  CatchFree,  Inc.  3/1/12   10   Prepared  for  MuckerLab  
  • 11. Q&A       Thank  You!     ashers*nsky@catchfree.com  |  @AlexShes*nsky   Copyright     atchFree,  Inc.   C3/1/12   11   Prepared  for  MuckerLab