--- name: developer-productivity description: Improve developer productivity through tool optimization, workflow streamlining, CI/CD improvement, developer experience management, and engineering metrics tracking. Use when improving developer workflow, optimizing CI/CD pipelines, managing developer tools, reducing lead time, or measuring engineering velocity. Triggers on phrases like "developer productivity", "engineering velocity", "CI/CD optimization", "lead time", "deploy frequency", "developer experience", "DevEx", "engineering metrics", "DORA metrics". --- # Developer Productivity & Engineering Metrics Optimize developer workflows and measure engineering effectiveness using industry-standard metrics and practices. ## Workflow ### 1. DORA Metrics & Engineering Performance 1. **Core DORA metrics tracking**: - Deploy frequency: how often production deployments occur - Lead time for changes: code commit to production deployment - Change failure rate: percentage of deployments causing failure - Mean time to recovery (MTTR): time to restore service after failure - Benchmark comparison (Elite, High, Medium, Low performers) 2. **Extended engineering metrics**: - Cycle time: work start to deployment - Work in progress (WIP) and batch size - Throughput: deployments or features per period - Code review time and merge rate - Incident frequency and impact 3. **Metrics dashboard and reporting**: - Real-time engineering metrics dashboard - Team-level and individual metric visibility (careful with individual metrics) - Trend analysis and benchmarking - Metric improvement goal setting - Executive summary and strategic insight ### 2. CI/CD Pipeline Optimization 1. **Pipeline architecture and design**: - Build, test, and deployment stage design - Parallel execution optimization - Caching strategy (dependency, build artifact) - Container and environment reuse - Pipeline-as-code management 2. **Build and test optimization**: - Build time reduction (parallelization, incremental builds, caching) - Test optimization (unit, integration, e2e split, test sharding) - Test flakiness reduction and reliability - Test coverage measurement and enforcement - Security scanning integration (SAST, DAST, dependency) 3. **Deployment optimization**: - Deployment time reduction - Blue/green and canary deployment automation - Rollback automation and speed - Zero-downtime deployment implementation - Multi-region deployment coordination ### 3. Developer Experience & Tooling 1. **Development environment setup**: - Local development environment standardization - Container-based development environment - Cloud development environment (GitHub Codespaces, Gitpod) - Environment parity (dev, staging, production) - Onboarding time reduction 2. **Tool optimization and integration**: - IDE and editor configuration standardization - Git workflow and branching strategy - Code quality tools (linting, formatting, static analysis) - Package and dependency management - API and service mocking for development 3. **Developer self-service**: - Infrastructure self-service provisioning - Service catalog and template library - Automated environment provisioning - Documentation and runbook accessibility - Internal developer platform (IDP) ### 4. Code Quality & Review Process 1. **Code review optimization**: - Review size and scope guidance - Review turnaround time targets - Automated pre-review checks (CI gate) - Review checklist and template - Reviewer assignment and load balancing 2. **Code quality automation**: - Automated linting and formatting - Static code analysis integration - Code coverage enforcement - Security vulnerability scanning - Dependency vulnerability checking 3. **Knowledge sharing and learning**: - Architecture decision records (ADRs) - Code walkthrough and design review - Post-incident blameless review - Tech talk and brown bag session - Pair programming and mob programming ### 5. Process Improvement & Culture 1. **Engineering process optimization**: - Sprint planning and estimation improvement - Definition of ready/done refinement - Impediment identification and removal - Technical debt management - Incident and on-call process improvement 2. **Blameless culture and psychological safety**: - Blameless post-incident review - Failure learning and sharing - Experimentation and innovation encouragement - Constructive feedback culture - Work-life balance and burnout prevention 3. **Continuous improvement measurement**: - Developer satisfaction survey - Engineering effectiveness assessment - Process feedback collection - Tool satisfaction and adoption tracking - Improvement initiative tracking and ROI ## Templates & Frameworks ### DORA Metrics Dashboard ``` DORA METRICS — Engineering Performance April 2025 =================================================== CORE METRICS (CURRENT QUARTER): Deploy Frequency: 47 deployments/week (Elite: >daily ✓) Lead Time for Changes: 2.4 hours (Elite: <1 hour — close ⚠) Change Failure Rate: 4.2% (Elite: 0-15% ✓) MTTR: 28 minutes (Elite: <1 hour ✓) PERFORMANCE TIER: Elite (3/4 metrics) Target: Improve lead time to <1 hour for full Elite status TREND ANALYSIS (LAST 6 MONTHS): Deploy Frequency: 32 → 36 → 38 → 41 → 44 → 47/week (improving ✓) Lead Time: 4.2h → 3.8h → 3.1h → 2.8h → 2.5h → 2.4h (improving ✓) Change Failure Rate: 8.1% → 6.7% → 5.9% → 5.2% → 4.8% → 4.2% (improving ✓) MTTR: 52min → 45min → 38min → 34min → 31min → 28min (improving ✓) EXTENDED METRICS: Cycle time (start to deploy): 6.2 hours avg Code review turnaround: 3.4 hours avg (target: <4 hours ✓) Build time: 4.2 minutes avg (target: <5 minutes ✓) Test execution time: 8.7 minutes avg (target: <10 minutes ✓) Deployment success rate: 95.8% ✓ Flaky test rate: 2.1% (target: <3% ✓) TEAM COMPARISON: Team Alpha: Deploy 52/wk, Lead 1.8h, CFR 3.1%, MTTR 22min Team Beta: Deploy 41/wk, Lead 2.6h, CFR 5.2%, MTTR 34min Team Gamma: Deploy 38/wk, Lead 3.1h, CFR 6.8%, MTTR 41min ⚠ IMPROVEMENT INITIATIVES (Q2): 1. Build cache optimization — target: 30% build time reduction 2. Test sharding implementation — target: 40% test time reduction 3. Automated rollback improvement — target: MTTR <20 minutes 4. Developer onboarding acceleration — target: <1 day to first deploy ``` ### Developer Satisfaction Survey ``` ENGINEER SATISFACTION SURVEY — Q2 2025 ======================================== DEVELOPER EXPERIENCE SCORECARD: TOOLING & ENVIRONMENT: Development setup ease: 4.1/5.0 ✓ Build speed satisfaction: 3.8/5.0 ⚠ Local environment reliability: 4.0/5.0 Tool quality satisfaction: 4.2/5.0 ✓ Documentation quality: 3.6/5.0 ⚠ WORKFLOW & PROCESS: Code review experience: 3.9/5.0 Sprint planning effectiveness: 3.7/5.0 Deployment confidence: 4.3/5.0 ✓ Incident response experience: 3.5/5.0 ⚠ Technical debt management: 3.2/5.0 ⚠ COLLABORATION & CULTURE: Team communication: 4.2/5.0 ✓ Cross-team collaboration: 3.8/5.0 Knowledge sharing: 3.9/5.0 Psychological safety: 4.4/5.0 ✓ Leadership support: 4.1/5.0 ✓ WORK-LIFE & WELLBEING: Workload balance: 3.6/5.0 ⚠ On-call experience: 3.1/5.0 ⚠ Meeting load satisfaction: 3.4/5.0 ⚠ Focus time availability: 3.7/5.0 Career growth opportunity: 4.0/5.0 OVERALL ENGINEER SATISFACTION: 3.8/5.0 Net Promoter Score (would recommend team): +42 TOP IMPROVEMENT REQUESTS: 1. Reduce flaky tests and build failures (47% of respondents) 2. Improve documentation quality and accessibility (38%) 3. Reduce on-call frequency and after-hours pages (35%) 4. Allocate dedicated tech debt sprint time (32%) 5. Reduce unnecessary meetings (28%) ``` ## Integration Points - CI/CD platforms (GitHub Actions, GitLab CI, Jenkins, CircleCI): Pipeline execution - Code hosting (GitHub, GitLab, Bitbucket): Repository management - Container platforms (Docker, Kubernetes): Environment management - Monitoring tools (Datadog, Prometheus): Deployment and incident tracking - Engineering analytics (DORA tools, Pluralsight Flow, SwiftBranch): Metrics collection - Developer experience platforms (Backstage, Humanitec): Internal developer platform - Communication platforms (Slack, Teams): Developer collaboration - Project management (Jira, Linear, GitHub Projects): Workflow tracking ## Edge Cases - **Legacy systems with slow CI/CD**: Incremental pipeline modernization; parallel legacy and modern pipeline; test automation investment; strangler fig pattern migration - **Multi-team dependency bottlenecks**: API contract testing; service virtualization; dependency version pinning; async communication protocols - **Remote/distributed team challenges**: Async code review process; documented decision making; overlapping hours for sync; timezone-aware scheduling - **High incident frequency impacting productivity**: Incident root cause elimination; alert fatigue reduction; on-call rotation optimization; error budget management - **Individual metrics causing unhealthy competition**: Team-level metric focus; collaborative goal setting; avoid public individual leaderboards; emphasize collective improvement ## Output ### Developer Productivity Dashboard ``` ENGINEERING PRODUCTIVITY — April 2025 ======================================= VELOCITY METRICS: Features delivered: 34 (↑ 12% from last quarter) Bug fixes: 127 (↓ 8% from last quarter ✓) Technical debt items addressed: 23 Total story points completed: 342 Sprint completion rate: 89% ✓ PIPELINE HEALTH: Pipeline success rate: 94.2% ✓ Avg build time: 4.2 minutes Avg test time: 8.7 minutes Avg deployment time: 3.1 minutes Pipeline flakiness rate: 2.8% (target: <3% ✓) CODE QUALITY: Code coverage: 82% (target: >80% ✓) Code review avg time: 3.4 hours Code review acceptance rate: 91% Static analysis issues (critical): 0 ✓ Security vulnerabilities (high): 2 (remediation in progress) INCIDENT IMPACT: Production incidents: 8 (↓ 25% from last quarter ✓) Mean time to detect: 12 minutes Mean time to resolve: 34 minutes Deployment-related incidents: 3 (CFR: 4.2%) Rollback frequency: 2 (0.3% of deployments) TEAM HEALTH: Developer satisfaction: 3.8/5.0 On-call rotation fairness: Balanced ✓ Burnout risk indicators: Low ✓ Meeting load: 14.2 hours/week avg (target: <15 ✓) Focus time availability: 22.4 hours/week avg IMPROVEMENT TRACKING: Active initiatives: 6 Completed this quarter: 4 Expected impact: Lead time ↓ 30%, Deploy time ↓ 25% Developer adoption of new tools: 89% ``` ## Trigger Phrases "developer productivity", "engineering velocity", "CI/CD optimization", "lead time", "deploy frequency", "developer experience", "DevEx", "engineering metrics", "DORA metrics", "change failure rate", "MTTR", "code quality", "developer satisfaction", "technical debt", "engineering culture"