The purpose of this markdown is to collect and aggregate the different metrics we would like to measure for analyzing different aspects of the Peribolos-as-a-Service. These metrics should help us answer some of the questions like how many users are interacting with the app, what is the performance of the app etc.
The metrics are defined by the different personas. Based on the different personas different kinda metrics might be interesting. We have listed the different personas in the following subsection and metrics that would be interesting based on these personas.
This doc describes the different personas that are involved in Project Peribolos-as-a-Service.
Project's key stakeholder who communicate the vision of the product to the team/stakeholders and ensure the feasibility of the product with respect to business objectives.
Primarily focused on application management, application maintenance and instrumental in automation of application development processes.
Provides technical feasibility of requirements, advise on technology choices and manage the technical roadmap i.e. Team Comet members.
Work with both developers and users to assess the product, utilizing data and user feedback to suggest improvements. Responsible for analyzing metrics to continually improve the product i.e. Team Telescope members.
Users interacting with the product (who we are building the product for).
Based on the different personas involved in Project Peribolos-as-a-Service and identified here, we can categorize the metrics as follows:
| Metrics | Metric Definition | Metric Calculation | Targeted Persona | Data Source |
| # New users (daily/weekly/monthly) | Number of new users over time | Product Owner | ||
| Product Adoption rate | How many people adopt the product and become regular users | (New Users ÷ Total Users) * 100 | Product Owner | |
| User Retention Rate | Rate of users retained over time | (# Users end of given period)-(# New users acquired in the period) / (#Users in the beginning of the period) * 100 | Product Owner | |
| Daily/Monthly Active repos (DAU/MAU) | Number of active repos daily/monthly | Product Owner | ||
| Product Stickiness Ratio | Measures the number of people that are highly engaged with the product | (DAU) / (MAU) * 100 | Product Owner | |
| Product Engagement Score (PES) | How users are interacting with your product | (Adoption + Retention + DAU/MAU) / 3 *100 | Product Owner | |
| Customer Satisfaction Score (CSAT) | How satisfied a customer/user is with overall experience of product | User provides rating on a 1-5 level (1 unsatisfied, 5 highly satisfied) \
\
Avg of 1-5 scores or
(# 4-5 scores)/(Total response volume) * 100 |
Analyst | Feedback Survey |
| Availability | Probability that the product is operational at a given time | (Time product is operating) / (total time it should be operating) | Operations | Prometheus |
| Avg Response Time | Total time it takes to respond to a request for the app service | (Total time taken to respond during the selected time period) / (# Responses in the selected time period) | Operations | Prometheus |
| # API request per minute (RPM) | Operations | Prometheus | ||
| Success Rate per Action | Success rate per action performed by the app | (Success rate/per action) | Operations | Prometheus |
| Failure Rate per Action | Failure rate per action performed by the app | (Failure rate/per action) | Operations | Prometheus |