1. Define value
   1. Find a Key Value Indicator (KVI)
      1. Daily Active Minutes (DAM)
      2. Daily Active Users (DAU)
      3. Conversion rates (%)
      4. Time-to-Learn
      5. non functional quality criteria
      6. Summary
         1. Ask your customers
            1. NPS (Net Promoter Score)
            2. to ensure that your software engineering team is delivering value to business and customers
   2. Key Value Areas (KVA)
      1. Current Value
         1. Revenue per Employee
            1. Gross Revenue / #employees
         2. Product Cost Ratio
            1. All expenses in the organization that develops, sustains, provides services, markets, sells, and administers the product or system.
         3. Employee Satisfaction
            1. Engaged employees that know how to maintain, sustain and enhance the software systems and products are one of the most significant assets of an organization.
         4. Customer Satisfaction
            1. Sound management, solid software, and creative, fulfilled employees
         5. Summary
            1. Healthy Business Metrics
      2. Time-to-Market / Time to delivery
         1. Release Frequency
            1. The time needed to satisfy the customer with new, competitive products.
         2. Release Stabilization
            1. The impact of poor development practices and underlying design and code base. Stabilization is a drag on competition that grows with time.
         3. Cycle Time
            1. The time (including stabilization) to satisfy a key set of customers or to respond to a market opportunity competitively.
         4. Lead Time
      3. Ability to Innovate
         1. Installed Version Index
            1. The difficulty customers face installing a new release .The relatively low value of new releases, or even the # of customers that are evaluating alternatives.
         2. Usage Index
            1. Determines a product that is burdensome and difficult to use and excess software that must be sustained even though it is rarely used.
         3. Innovation Rate
            1. Growth of technical debt caused by poorly designed and developed software. Budget is progressively consumed keeping the old software alive.
         4. Defects
            1. Measures increasingly poor quality software, leading to greater resource and budget to maintain it and potential loss of customers.
2. Quality
   1. Defect rate
   2. Percentage of test coverage
   3. Average age of closed bugs
   4. Up time (reliability)
   5. Latency
   6. more metrics: Audit of Testing
      1. metrics for docs
         1. The recipe for a good Test Plan
3. Time to recovery
   1. Incident detection time (MTTD)
   2. Incident recovery time (MTTR)
   3. Summary
      1. Метрики HelpDesk service
         1. Улучшаем сервис технической поддержки: нанимаем новые технологии
4. Team velocity
   1. Number of releases
   2. Number of story points completed
   3. Rate of story completion
5. Metrics of Iterations
   1. Carry Over
      1. the amount of work pushed from one Sprint or iteration into the next
   2. how much work Team is doing at one time
   3. Release Frequency
   4. Number Of Backlog Items NOT Done
   5. Sprint burndown
   6. Epic and release burndown
   7. Velocity
      1. average amount of work a scrum team completes during a sprint
   8. Kanban metrics
      1. Cumulative flow diagram
      2. Lead and Cycle Time Diagram
      3. Burn Down Chart
   9. to slice User Stories into independent increments of value
6. 10 KEY METRICS FOR SCRUM
   1. SPRINT GOAL SUCCESS RATES
   2. DEFECTS
   3. TIME TO MARKET
   4. RETURN ON INVESTMENT (ROI)
   5. CAPITAL REDEPLOYMENT
      1. The value (V) of the remaining requirements in the product backlog
      2. The actual cost (AC) for the work to complete the requirements in the product backlog
      3. The opportunity cost (OC), or the value of having the scrum team work on a new project
      4. When V < AC + OC, the project can stop
   6. SATISFACTION SURVEYS
      1. Customer satisfaction surveys
      2. Team satisfaction surveys
   7. TEAM MEMBER TURNOVER
      1. Scrum team turnover
      2. Company turnover
   8. PROJECT ATTRITION
   9. SKILL VERSATILITY
      1. Per-person skills and levels
      2. Per-team skills and levels
      3. Per-organization skills and levels
   10. MANAGER:CREATOR RATIO
7. The recipe for a good METRICS
8. more metrics here
   1. SaaS. Разбираем некоторые Метрики
   2. Unit-экономика. Разбираем основы (V2)
   3. Some notes about Customer Lifetime Value (LTV)
   4. Metrics for PO and not only: HEART, AARRRT, Daily Revenue
   5. How to calculate Daily Revenue according to @GooglePlayDev
   6. Some notes about Advertising metrics
   7. MVP. Оценка Рынка (Product Star)
   8. Healthy Business Metrics Mix by @smashingmag
   9. Работа с гипотезами и не только. Идеи с AgileDays 2020
   10. Unit-экономика. Mobile Apps
   11. Some notes about metrics for PO
   12. Метрики: продуктовые, финансовые, технические
9. more recipies
   1. Some Software Testing Recipes
   2. The recipe for good bug report