## Developer Metrics
I think we should have four major goals. We should measure these goals as well as the factors we believe contribute to them. Methods of measuring each factor are denoted with [brackets]. They are in no particular order as follows:

- Features Delivered
  - How do we measure? [Stories per quarter]
  - Each feature must have acceptable test coverage, must be an approach acceptable by peers, and gets bonus points for cleverness or efficiency
  - Affected by:
    * Our work with Biz & Design to determine scope [survey customer happiness]
    * Accuracy of estimates [keep history, noah charts this]
    * How well we follow our process, breaking these down [points::stories ratio]
    * Team happiness [team survey]
    * Time spent on overhead [time track meetings/week]

- Customer Happiness
  - How do we measure? [NPS, customer success evaluation]
  - It's the biz team's job to determine the balance of price and features. We focus on building great things for them to sell.
  - Affected by:
    * How effectively we measure this/prioritizing analytics work [???]
    * How effective our research is [feature churn]
    * Iterating to get to the right place quickly [points per feature]
    * The realm of technical feasability
    * Balance of right amount of features, delivered the right way [customer use/churn]

- Team Happiness
  - How do we measure? See below:
    * Growth opportunities [how many people use their learning budget?]
    * Stable and supportive work environment [employee churn, anonymous survey]
    * Realistic, but challenging expectations [peer review of growth (using commit messages?)]
    * Burnout [blackout (no comms) vacation taken]

- Technical Debt/Infrastructure cost
  - How do we measure? [Cost per Passenger?]
  - We know what's needed and it's our job to help the rest of the biz understand that
  - Keeping costs down helps ensure viability
  - Affected by:
    * Features chosen
    * Client needs
    * AWS pricing structure
    * Time devoted to maximizing Dev Ops