TEAM METRICS WITH OUTLIERS FINAL
================================================================================ INVESTIGATION: Why Are Metrics Showing 0.0? ================================================================================
Data Availability Analysis
ACQREG - Acquisition & Registration
Total issues: 1000 Issues with resolved_at timestamp: 440 Issues with transition history: 860 Completed issues (Done/Closed/Resolved): 440 Defect issues (Bug/Defect/Incident): 80 Sample issue keys: ACQREG-216, ACQREG-215, ACQREG-214, ACQREG-213, ACQREG-212
LGMT - MarTech
Total issues: 1000 Issues with resolved_at timestamp: 530 Issues with transition history: 760 Completed issues (Done/Closed/Resolved): 520 Defect issues (Bug/Defect/Incident): 90 Sample issue keys: LGMT-2843, LGMT-2842, LGMT-2841, LGMT-2840, LGMT-2839
O2C - Order to Cash
Total issues: 1000 Issues with resolved_at timestamp: 370 Issues with transition history: 770 Completed issues (Done/Closed/Resolved): 370 Defect issues (Bug/Defect/Incident): 100 Sample issue keys: O2C-989, O2C-988, O2C-987, O2C-986, O2C-985
SSH - SSH & User Management
Total issues: 1000 Issues with resolved_at timestamp: 730 Issues with transition history: 830 Completed issues (Done/Closed/Resolved): 730 Defect issues (Bug/Defect/Incident): 150 Sample issue keys: SSH-305, SSH-304, SSH-303, SSH-302, SSH-301
UAS - User Authentication Services
Total issues: 1000 Issues with resolved_at timestamp: 650 Issues with transition history: 740 Completed issues (Done/Closed/Resolved): 650 Defect issues (Bug/Defect/Incident): 120 Sample issue keys: UAS-1057, UAS-1056, UAS-1055, UAS-1054, UAS-1053
================================================================================ TEAM METRICS REPORT WITH OUTLIERS FOR LEADERSHIP REVIEW ================================================================================
Report Generated: 2025-11-17 09:58:18
PURPOSE: This report enables each team to review their own KPIs and identify improvement opportunities. Teams are presented alphabetically.
NOTE: Metrics are NOT comparable between teams due to different project contexts, constraints, and priorities.
================================================================================
ACQREG - Acquisition & Registration
Flow Framework Metrics
Velocity (completed): 370 issues Load (WIP): 160 issues Avg Flow Time: 6.75 days Median Flow Time: 3.78 days P85 Flow Time: 16.83 days Flow Efficiency: 40.0% Distribution: - feature: 350 issues - defect: 20 issues
DORA Metrics
Lead Time (avg): 5.49 days Lead Time (median): 2.71 days Deployment Frequency: 58.3 per week MTTR: 0.00 hours Change Failure Rate: 4.0%
OUTLIERS FOR LEADERSHIP REVIEW
Issues with Exceptionally Long Lead Times:
1. ACQREG-139: Build "Feature Grid" Section Lead Time: 30 days (2.8x average) Type: Task | Status: Done Created: 2025-10-14 | Resolved: 2025-11-13 JIRA Link: https://statista.atlassian.net/browse/ACQREG-139
2. ACQREG-138: Build “Institutions Section” Tabs Element Lead Time: 28 days (2.6x average) Type: Task | Status: Done Created: 2025-10-14 | Resolved: 2025-11-11 JIRA Link: https://statista.atlassian.net/browse/ACQREG-138
3. ACQREG-171: Redirect on monolith side /register -> /registration Lead Time: 23 days (2.1x average) Type: Task | Status: Done Created: 2025-10-21 | Resolved: 2025-11-14 JIRA Link: https://statista.atlassian.net/browse/ACQREG-171
No WIP issues found
================================================================================
LGMT - MarTech
Flow Framework Metrics
Velocity (completed): 350 issues Load (WIP): 130 issues Avg Flow Time: 8.62 days Median Flow Time: 6.06 days P85 Flow Time: 15.88 days Flow Efficiency: 40.0% Distribution: - feature: 310 issues - defect: 20 issues - risk: 20 issues
DORA Metrics
Lead Time (avg): 6.35 days Lead Time (median): 4.34 days Deployment Frequency: 46.7 per week MTTR: 0.00 hours Change Failure Rate: 10.0%
OUTLIERS FOR LEADERSHIP REVIEW
Issues with Exceptionally Long Lead Times:
1. LGMT-2745: [Cookie Banner] signet save for later AB Test Lead Time: 54 days (4.2x average) Type: Sub-task | Status: Done Created: 2025-09-18 | Resolved: 2025-11-12 JIRA Link: https://statista.atlassian.net/browse/LGMT-2745
2. LGMT-2772: [CDP] Update API schema to allow new field "Company Size" Lead Time: 34 days (2.6x average) Type: Task | Status: Done Created: 2025-10-02 | Resolved: 2025-11-06 JIRA Link: https://statista.atlassian.net/browse/LGMT-2772
3. LGMT-2750: Success Stories - video & audio Lead Time: 32 days (2.5x average) Type: Task | Status: Done Created: 2025-09-19 | Resolved: 2025-10-21 JIRA Link: https://statista.atlassian.net/browse/LGMT-2750
Issues Stuck in WIP for Extended Periods:
1. LGMT-2746: [Cookie Banner] prepare and roll out cookie signet + categories, 2nd level accor... Days in WIP: 59 days Type: Bug | Status: In Progress Created: 2025-09-18 JIRA Link: https://statista.atlassian.net/browse/LGMT-2746
2. LGMT-2754: O2KR1: Bowtie - Automating Onboarding Communication Days in WIP: 55 days Type: Epic | Status: In Progress Created: 2025-09-22 JIRA Link: https://statista.atlassian.net/browse/LGMT-2754
================================================================================
O2C - Order to Cash
Flow Framework Metrics
Velocity (completed): 280 issues Load (WIP): 210 issues Avg Flow Time: 7.82 days Median Flow Time: 1.98 days P85 Flow Time: 18.05 days Flow Efficiency: 40.0% Distribution: - defect: 40 issues - feature: 240 issues
DORA Metrics
Lead Time (avg): 12.15 days Lead Time (median): 16.65 days Deployment Frequency: 42.0 per week MTTR: 0.00 hours Change Failure Rate: 11.1%
OUTLIERS FOR LEADERSHIP REVIEW
Issues with Exceptionally Long Lead Times:
1. O2C-895: KL: Credit note is not created for Fraud/credit card dispute/ wrong amount termi... Lead Time: 44 days (2.1x average) Type: Bug | Status: Done Created: 2025-09-23 | Resolved: 2025-11-06 JIRA Link: https://statista.atlassian.net/browse/O2C-895
2. O2C-893: KL: Termination with goodwill is not generating the credit note Lead Time: 43 days (2.0x average) Type: Bug | Status: Done Created: 2025-09-23 | Resolved: 2025-11-05 JIRA Link: https://statista.atlassian.net/browse/O2C-893
3. O2C-901: Run script for starter accounts invoices Lead Time: 41 days (1.9x average) Type: Sub-task | Status: Done Created: 2025-09-24 | Resolved: 2025-11-04 JIRA Link: https://statista.atlassian.net/browse/O2C-901
Issues Stuck in WIP for Extended Periods:
1. O2C-892: Personal account: Cancellation/termination of a contract in SF triggers the welc... Days in WIP: 55 days Type: Bug | Status: In Progress Created: 2025-09-23 JIRA Link: https://statista.atlassian.net/browse/O2C-892
2. O2C-899: Add currency conversion to legacy invoice templates for LTD Days in WIP: 54 days Type: Sub-task | Status: In Progress Created: 2025-09-23 JIRA Link: https://statista.atlassian.net/browse/O2C-899
================================================================================
SSH - SSH & User Management
Flow Framework Metrics
Velocity (completed): 610 issues Load (WIP): 100 issues Avg Flow Time: 3.80 days Median Flow Time: 2.41 days P85 Flow Time: 6.01 days Flow Efficiency: 40.0% Distribution: - feature: 490 issues - defect: 110 issues - risk: 10 issues
DORA Metrics
Lead Time (avg): 2.78 days Lead Time (median): 1.69 days Deployment Frequency: 88.7 per week MTTR: 0.00 hours Change Failure Rate: 28.9%
OUTLIERS FOR LEADERSHIP REVIEW
Issues with Exceptionally Long Lead Times:
1. SSH-229: Infra | Enable Communication between Services Lead Time: 28 days (4.9x average) Type: Task | Status: Done Created: 2025-10-17 | Resolved: 2025-11-14 JIRA Link: https://statista.atlassian.net/browse/SSH-229
2. SSH-226: Fix "large initial icons" Lead Time: 25 days (4.4x average) Type: Subtask | Status: Done Created: 2025-10-15 | Resolved: 2025-11-10 JIRA Link: https://statista.atlassian.net/browse/SSH-226
3. SSH-239: Documentation | Guide other teams on the tech definitions of seats Lead Time: 22 days (3.9x average) Type: Spike | Status: Done Created: 2025-10-20 | Resolved: 2025-11-12 JIRA Link: https://statista.atlassian.net/browse/SSH-239
Issues Stuck in WIP for Extended Periods:
1. SSH-220: Setup testing session with QA [2 weeks before release] Days in WIP: 33 days Type: Story | Status: In Progress Created: 2025-10-14 JIRA Link: https://statista.atlassian.net/browse/SSH-220
2. SSH-224: Restrict page access to logged-in users with pro admin accounts Days in WIP: 32 days Type: Subtask | Status: In Progress Created: 2025-10-15 JIRA Link: https://statista.atlassian.net/browse/SSH-224
================================================================================
UAS - User Authentication Services
Flow Framework Metrics
Velocity (completed): 200 issues Load (WIP): 70 issues Avg Flow Time: 10.17 days Median Flow Time: 5.38 days P85 Flow Time: 24.66 days Flow Efficiency: 40.0% Distribution: - feature: 170 issues - defect: 30 issues
DORA Metrics
Lead Time (avg): 6.59 days Lead Time (median): 1.28 days Deployment Frequency: 21.0 per week MTTR: 0.00 hours Change Failure Rate: 22.2%
OUTLIERS FOR LEADERSHIP REVIEW
Issues with Exceptionally Long Lead Times:
1. UAS-1003: SSO ticket generation tool: Add edit and revoke function Lead Time: 49 days (4.9x average) Type: Task | Status: Done Created: 2025-09-24 | Resolved: 2025-11-12 JIRA Link: https://statista.atlassian.net/browse/UAS-1003
2. UAS-997: Remix wireit config update Lead Time: 49 days (4.9x average) Type: Task | Status: Done Created: 2025-09-23 | Resolved: 2025-11-12 JIRA Link: https://statista.atlassian.net/browse/UAS-997
3. UAS-1002: Investigate: SAML Single Logout setup Lead Time: 48 days (4.8x average) Type: Task | Status: Done Created: 2025-09-23 | Resolved: 2025-11-11 JIRA Link: https://statista.atlassian.net/browse/UAS-1002
Issues Stuck in WIP for Extended Periods:
1. UAS-995: Clean up SSO Docs Days in WIP: 55 days Type: Task | Status: In Progress Created: 2025-09-22 JIRA Link: https://statista.atlassian.net/browse/UAS-995
2. UAS-1004: Decrease UAS support efforts Days in WIP: 53 days Type: Epic | Status: In Progress Created: 2025-09-24 JIRA Link: https://statista.atlassian.net/browse/UAS-1004
================================================================================
REPORT USAGE GUIDANCE: - Use this report to identify YOUR TEAM'S improvement opportunities - Focus on outliers that may indicate process bottlenecks - Do NOT compare metrics across teams - Each team operates in a unique context