SPRINT.
HOW TO MEASURE EFFORT
SPRINT. HOW TO MEASURE EFFORT
“CORE: Development effort is more than just commits. It's the sum of code changes, focus areas, and team coordination.”
📊 EFFORT METRICS
Understanding effort requires measuring multiple dimensions:
| Metric | Description | Weight |
|---|---|---|
| Commits | Base unit of work | 1.0 |
| Lines Added | New code contribution | 0.1/line |
| Lines Deleted | Code cleanup/refactoring | 0.05/line |
| Files Changed | Scope of change | 0.5/file |
| Issue Reference | Connected work | 2.0 bonus |
| PR Merge | Integration effort | 3.0 bonus |
🎯 EFFORT SCORE
The Effort Score is a weighted calculation:
Effort = (Commits × 1) + (Lines Added × 0.1) + (Lines Deleted × 0.05)
+ (Files Changed × 0.5) + BonusesThis provides a normalized way to compare development effort across:
- Different time periods
- Different authors
- Different types of work
🏷️ COMMIT CATEGORIES
Commits are categorized by their prefix:
| Prefix | Category | Focus |
|---|---|---|
| FEAT. | Feature | New functionality |
| FIX. | Bug Fix | Issue resolution |
| THINK. | Research | Investigation/planning |
| UX. | Design | User experience |
| DEBT. | Tech Debt | Maintenance |
| UNPARTY. | Platform | Core infrastructure |
| WORKFLOW. | Workflow | Automation |
| STAGE. | Staging | Deployment |
| STORY. | Story | Content/narrative |
| LLM. | AI | LLM integration |
| DEPEND. | Dependencies | Package updates |
| DOC. | Documentation | Writing |
| LEARN. | Learning | Education |
📁 FOCUS AREAS
File changes are categorized to understand where effort is directed:
| Area | Pattern | Indicator |
|---|---|---|
| 🧩 Components | /components/, .tsx | UI building |
| 📄 Pages | /pages/, /app/ | Routing |
| 🔌 API | /api/ | Backend |
| ⚙️ Scripts | /scripts/, .sh | Automation |
| 🧪 Tests | .test., .spec. | Quality |
| 🎨 Styles | .css, .scss | Design |
| ⚡ Config | config, .json | Setup |
| 📝 Docs | .md | Documentation |
📈 USAGE
CLI Commands
# Analyze last 7 days (default)
npm run effort
# Analyze last week
npm run effort:weekly
# Analyze 2-week sprint
npm run effort:sprint
# Analyze full month
npm run effort:month
# JSON output for integration
npm run effort:jsonDirect Script Usage
# Custom period
node scripts/sprint-effort-analysis.js --days 14
# Filter by author
node scripts/sprint-effort-analysis.js --author "unparty"
# Help
node scripts/sprint-effort-analysis.js --help🪩 WEEKLY SUMMARY ANALYSIS
This issue represents analysis of the weekly summary:
Period: 2026-03-30 to 2026-04-03
| Metric | Value |
|---|---|
| Total Commits | 88 |
| Lines Added | 13,976 |
| Lines Deleted | 3,359 |
| Net Change | +10,617 |
| Direction | Growth |
Key Insights
1. High Growth Period - Net positive change of 10,617 lines indicates active feature development
2. Diverse Contributors - Mix of human (unparty, justin murry) and AI (copilot-swe-agent, claude) commits
3. Category Distribution - Mix of FEAT., FIX., THINK., UX. prefixes shows balanced development
4. New Files Created - 35 new files created, indicating expanding codebase
🔗 CONNECT
- Script: scripts/sprint-effort-analysis.js
- Related: story-029.md (runway features analysis)
- Data: Uses git log analysis
Created: 2026-04-04
SPRINT. Effort measurement for development focus and performance.
