Carpaccio Methodology: Connecting the dots between ‘the work engineers do’ and a ‘profitable org’
summary
This proposes the Carpaccio methodology as a practical measurement system that counts features, defects and invisible work into a Healthy Productivity Index, using one ticket system with three ticket types (stories, bugs, tasks) and task cycle times of 2–5 days. Productivity ratio = (stories + bugs deployed) / (all tickets produced); target 70–90% sweet spot. Adds two metrics (Carpacho service and production), a per-engineer 1–5 accountability weighting tied to business goals, and a web calculator to apply it.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:51Measuring engineering productivity
- 3:41What is Carpaccio methodology
- 6:14One ticket system for all work
- 8:23Carpaccio vs existing metrics
- 10:08Productivity ratio explained
- 12:15Connecting to business goals
- 14:25Q&A and resources
related talks
28mMeasuring Success
49mProductivity Panel
33mMeasuring Developer Productivity: the good, the bad and the data
47mCan We Measure Developer Productivity?
44mEnhancing the Performance of Engineering Teams
02h 31mDeveloper Productivity Engineering - Extended Session
43mMeasuring Developer Productivity: The Good, the Bad and the Data
30mHow to Visualize Impacts to Your Workflow & Metrics