ID | Title | Cluster | Status | Closed At | Activities | Exp. Biz Impact | Release/Communication Plan | OKR Impacts | Exp. Due Date | Impact Achievement Eval. | Long running | Notes | Living Roadmap | 12/02 | 26/02 | 12/03 | next 30 sprint days | next 30 sprint days | next 60 sprint days |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Integrazioni esterne ("BOCCHETTONE") + Group Budget/Approval Flow + SSO/Mapping integrazione Decathlon | internal efficiency | Closed | 2025-05-15 | 0 / 0 activities 0 / 0 SP | - first SSO integrated customer (commercial value) streamlining Decathlon user and areas scaling
- possibility to support other enterprises to automatize and centralize user management through exposed API ("bocchettone"): this could also be exposed with a pay-per-use policy, consisting in a new revenue channel in the future
- gain know-how to handle other similar cases that are likely to be new needs for big companies | w17 | No tagged master issue w9 |
Zero operative issues on Decathlon onboardings/scaling after 3w from the release (w20) - CONFIRMED IN W20, ACHIEVED | - | - | |||||||||
Combine Event & Concierge | internal efficiency | Closed | 2025-09-29 | 0 / 0 activities 0 / 0 SP | PHASE 1
- Reduced time for EEs to add standard products to proposals
- Preparation of foundation blocks for following phases
PHASE 2
- Preparation of foundation blocks for following phases
- Reduced time for Kampaayers to find information about concierge events
- Better navigation in Concierge section BO
PHASE 3
- Reduced time for EEs to manage self-service events
- Improved dashboard and event navigation for customers (unified UX for all events + better UI)
- Improved event navigation for EEs and Kampaayers in BO (unified UX for all events + better UI)
- Extended supplier portal
PHASE 4
- Higher scalability of our codebase
- Higher dev productivity | PHASE 3
- W19 update Doc with expected changes and impacts (DONE)
- W20 async feedback collection from founders on impacts and release date (DONE)
- W21 scheduled meetings with other teams (EE, Sales, Financ&Legal) to explain key changes and expected release timeframe (DONE)
- Confirm final release date to all teams by end of June (DONE)
- Define how to communicate changes to customers by end of June coordinating with Marketing and Sales (DONE)
PHASE 4
(DONE) | No tagged master issue PHASE 3:
- Expected completion date: 18/07 (DONE)
PHASE 4
- Expected completion date: 29/8 (DONE) | PHASE 1
- Positive feedback in the weeks immediately after release
- Positive score at dedicated question in CSAT survey in w38 --> PARTIALLY ACHIEVED
- No immediate disruption in any BAU process (DONE) --> ACHIEVED
PHASE 2
n/a (minor UI changes + preparation of final merge, so impacts will be visible especially after Phase 3)
PHASE 3
- Positive feedback in the weeks immediately after release
- Positive score at dedicated question in CSAT survey in w38 --> PARTIALLY ACHIEVED
- No immediate disruption in any BAU process (DONE)
PHASE 4
- No disruption in any BAU process until w35 included (DONE) --> ACHIEVED | - | - | |||||||||
Performance and processing speed | internal efficiency | Closed | 2025-06-16 | 0 / 0 activities 0 / 0 SP | scope SEED ASIS si compone di 3 iniziative:
#1 soluzione problemi memoria e stabilità BE
#2 soluzione rendering performance BOv2
#3 miglioramento perf. ricerca (semantica + items)
Steps per ogni iniziativa:
STEP1 (investigazione/R&D): approfondimento, discussione, definizione e validazione soluzioni
STEP2 (implementazione): TBD in funzione dei findings e dell'output di step1 | Tutto retrocompatibile, quindi N/A
| No tagged master issue per ogni iniziativa:
#1: investigazione terminata con successo, implementazione RILASCIATO il 18 Aprile
#2 RILASCIATO in produzione il 16 Maggio, con interventi circoscritti (suppliers, proposals) ed un intervento più generico
#3: RILASCIATO in produzione il 16 Maggio | per ogni iniziativa:
#1 istanze BE stabili nel mese successivo al rilascio (no out of memory) // monitoring fino al 18/05 (w21) -- CONFERMATO, ISTANZE STABILI POST RILASCIO
#2 frizione di rendering BOv2 sensibilmente mitigata (devTool o clarity report) + validazione qualitativa dal team (w25) -- CONFERMATO, NESSUNA SEGNALAZIONE DAL TEAM E NESSUN DOWN BE
#3 miglioramento performance di risposta della ricerca semantica: validazione qualitativa e in base a log sentry dal team (w25) -- CONFERMATO, TEMPI PIù REATTIVI NUMERICAMENTE | - | - | |||||||||
Errors, Logs, Sessions Monitoring | internal efficiency | Closed | 2025-06-16 | 0 / 0 activities 0 / 0 SP | - reduced investigation time, less distractions during the sprints
- better support and faster solution for reported issues
- better insights for product development
DONE // STEP 1 (clarity activation in prod) we will be able to
- easily identify a specific session recording with a problem occurrence
- use the session recording to analyze the scenario, reproduce it, debug, fix
- use the session recordings to analyse trends, funnels, heatmaps, etc....
- (out of scope) gather occurrences of any custom event (i.e: "user clicks on checkout btn"), set and analyse metrics
STEP 2 (sentry integration cleaning/revamp) we will be able to
- reduce the notifications noise and be alerted just upon real errors
- minimize the risk of losing an error occurrence
STEP 3 (TBC custom event tracking + tooling evaluation) | Not needed, just internal alignment.
shared tech doc HAS BEEN updated with sentry+clarity debug workflow relevant details: https://docs.google.com/document/d/1V70iYCFEDrtXYhmPxzas8X0LqaWddyCDGgJyqTEMsbA/edit?tab=t.l6w9vv698nih | No tagged master issue step 1 before mid-April (DONE)
step 2 within 9/05 (DONE) | positive tech team feedback, shorter report-to-hotfix times and context-switch from sprint activities in w25 -- CONFERMATO, TEAM CONFERMA EFFICACIA DEGLI STRUMENTI IN ESSERE | steps TBD:
possible follow-ups - evaluate Clarity effectiveness and compare with Mixpanel recordings | - | - | ||||||||
BO Productization Prototype | internal efficiency | Blocked | Not closed | 0 / 0 activities 0 / 0 SP | - Validate that there is at least one customer willing to sign the "early adopter" plan for using out internal platform | - entro W40 (rolling) rilascio specificità
tutte le modifiche valutate fino ad ora sarebbero retrocompatibili => no internal communication | No tagged master issue
step 5: implementazione issues e rilascio prima whitelabel (from w32 until W39) | - up'n'running from W40 --> ACHIEVED
- No major unexpected issues when activating for an external agency | - Outlook integration will require some activities in 1° sprint of october (usable with some limitations since end of Sept) | - | - | ||||||||
Show supplier's usage history and team feedback | internal efficiency | Closed | 2025-10-06 | 0 / 0 activities 0 / 0 SP | - Time saving during the scouting by EE team
- Time saving for linking an invoice to an event for Finance team
- Supplier base quality & detail improvement | - Standard training EE/FIN post release in w36 | No tagged master issue DONE | Valutare numero di recensioni vs numero di eventi deliverati in w40 (valutazione in w41) - ACHIEVED | - 29% of events closed/lost after 25/08 (excluding reinvoices) have at least 1 reviews
- Interviewed EEs express satisfaction with both the insertion and usage of reviews
- Events history of suppliers appreciated by interviewed EEs are additional decision element during scouting | - | - | ||||||||
Make email sync flow reliable and comprehensive | internal efficiency | Closed | 2025-10-20 | 0 / 0 activities 0 / 0 SP | - More documents in our Supplier DB --> More data for search during scouting
- More documents to perform items extraction with AI | Training W36 | No tagged master issue W42 | After release of new algorithm (w42):
- Verify all emails are correctly tracked, including in branches, with manual tests
- Check for selected email conversations of EEs that all emails are synced
--> ACHIEVED | - | - | |||||||||
Scaling SSO | internal efficiency | Defined | Not closed | 0 / 0 activities 0 / 0 SP | - reduce forecasted costs for SSO
- reduce frictions in contract negotiations
- have a fairer feature scaling perspective towards infinite capacity | nessuna comunicazione per ora, in attesa delle prime implementazioni
NOTA: integrazione alfasigma attesa "per dicembre se non gennaio" (Chiara P.) | No tagged master issue 2.a con Irene si manda PEC e si sblocca cantiere multiplexer/broker (DONE)
2.b implementazione infrastruttura (w35 - DONE)
3. configurazione connessione di test e validazione (w36 - DONE)
4. documentazione e BO kampaay SSO signup validation (w7) | - costi operativi inferiori e più stabili rispetto all'asis → per il 2026, saremmo passati da 1650€ a 8800€ (di cui 5500€ imputabili a SSO) per aumentare cap SSO a 5, avremmo poi pagato 1100€ in più per ogni SSO aggiuntivo fino ad un massimo di 15. Post intervento, il costo per SSO è stato ridotto a 200/400€ su una scala di crescita meno che lineare ACHIEVED
- nessun vincolo al numero di SSO cliente supportati + raggiungere uno status di "attivazione BAU" a livello di sviluppo/commerciale → centinaia supportate, tetto ideale a 1000 ACHIEVED
- corretto funzionamento e continuità di servizio dopo prima integrazione | - | - | |||||||||
RBAC - Improve roles and permissions management in BO | internal efficiency | Closed | 2025-11-10 | 0 / 0 activities 0 / 0 SP | - More security for Kampaay (permissions assigned correctly)
- Increased compliance toward ISO 27001
- Permission system applicable to external agencies (flexible and scalable) |
DONE
Messaggio da Marco a tutti i team per informarli che abbiamo nuovo sistema di gestione permessi e informarci se non riescono a fare qualcosa che devono poter fare | No tagged master issue w45
27/10 the big bang (DONE)
Follow-ups senza grossi impatti (vedi "latest master" sopra e master feats a lato) | - Soluzione completa e non ostativa all'operatività post rilascio
- Numerosità admin regolare
- Documentazione completa e chiara
monitoring rolling + verifica achievements a valle della #3821 (W46)
--> ACHIEVED | all issues in current sprint except for possible Follow-Ups | - | - | ||||||||
Handle multiple payments with credit card per event for amount variations, advance and balance payments, from a single payer | customer experience | Defined | Not closed | 0 / 0 activities 0 / 0 SP | - Reduced effort for Sales, EE and Finance to manage such card payments
- Better customer experience related to card payments | - Sharing and validation pre-development (team + SBB/MA/GM) DONE
- Sales/Finance communication + Costa deep dive DONE
- Training post release with Sales+EE+Finance DONE
- sharing a presenti e non di video e note gemini DONE (allegati al calendar)
- aggiornare playbook EE/materiale Sales W6 (Giorgia già sul pezzo)
- quando/come attiviamo i clienti interessati --> Sales avvisati su come procedere, ppt di spiegazione condivisa, coordinamento con Chiara per Costa in essere (w6) | No tagged master issue W5 | All cases of card payments with advance-balance splits in Q1 26 after feature release are performed with the new solution all-in-platform (w14)
Note: managing multiple payers is out of scope | - | - | |||||||||