# CoP Quality Manifesto & Definition of Success ## Topics * Technical debt * How to discover * How to communicate * How to pay it off * How to keep it low * Quality metrics * How to identify signs you are approaching a scaling bottleneck ## Activities * Coaching as a Service * Define established practices and strategies * Improve [learning paths and topics](https://github.com/casavo/tech-learning) * Promote practices and strategies in tribes through presentations and practical sessions * Promote practices and strategies providing on demand support (in pair) * Drive quartely updates of tech radar * Learn new stuff and explore with spikes * Act as enabler of cross-CoP questions ## Definition of Success * Attendance/participation (KPI: 1 for tribe -> aspirational: 1 for squad) * Number of "public" event + related reference doc (KPI: 1/month) * Constant feedback from squads about adoption/comprehension * Relevant quality metrics adopted by tribes ## Fra Feedback * rotazione dei team member // quality ambassador, ma non vogliamo che sia solo uno a farsi carico * chi partecipa deve essere "spingitore di qualità" * "sessioni" più verticali (es. quality in FE vs quality in BE)