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:

MetricCommits
DescriptionBase unit of work
Weight1.0
MetricLines Added
DescriptionNew code contribution
Weight0.1/line
MetricLines Deleted
DescriptionCode cleanup/refactoring
Weight0.05/line
MetricFiles Changed
DescriptionScope of change
Weight0.5/file
MetricIssue Reference
DescriptionConnected work
Weight2.0 bonus
MetricPR Merge
DescriptionIntegration effort
Weight3.0 bonus

๐ŸŽฏ EFFORT SCORE

The Effort Score is a weighted calculation:

code
Effort = (Commits ร— 1) + (Lines Added ร— 0.1) + (Lines Deleted ร— 0.05) 
       + (Files Changed ร— 0.5) + Bonuses

This 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:

PrefixFEAT.
CategoryFeature
FocusNew functionality
PrefixFIX.
CategoryBug Fix
FocusIssue resolution
PrefixTHINK.
CategoryResearch
FocusInvestigation/planning
PrefixUX.
CategoryDesign
FocusUser experience
PrefixDEBT.
CategoryTech Debt
FocusMaintenance
PrefixUNPARTY.
CategoryPlatform
FocusCore infrastructure
PrefixWORKFLOW.
CategoryWorkflow
FocusAutomation
PrefixSTAGE.
CategoryStaging
FocusDeployment
PrefixSTORY.
CategoryStory
FocusContent/narrative
PrefixLLM.
CategoryAI
FocusLLM integration
PrefixDEPEND.
CategoryDependencies
FocusPackage updates
PrefixDOC.
CategoryDocumentation
FocusWriting
PrefixLEARN.
CategoryLearning
FocusEducation

๐Ÿ“ FOCUS AREAS

File changes are categorized to understand where effort is directed:

Area๐Ÿงฉ Components
Pattern/components/, .tsx
IndicatorUI building
Area๐Ÿ“„ Pages
Pattern/pages/, /app/
IndicatorRouting
Area๐Ÿ”Œ API
Pattern/api/
IndicatorBackend
Areaโš™๏ธ Scripts
Pattern/scripts/, .sh
IndicatorAutomation
Area๐Ÿงช Tests
Pattern.test., .spec.
IndicatorQuality
Area๐ŸŽจ Styles
Pattern.css, .scss
IndicatorDesign
Areaโšก Config
Patternconfig, .json
IndicatorSetup
Area๐Ÿ“ Docs
Pattern.md
IndicatorDocumentation

๐Ÿ“ˆ USAGE

CLI Commands

bash
# 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:json

Direct Script Usage

bash
# 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

MetricTotal Commits
Value88
MetricLines Added
Value13,976
MetricLines Deleted
Value3,359
MetricNet Change
Value+10,617
MetricDirection
ValueGrowth

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.

#stories

๐Ÿง—๐Ÿพโ€โ™‚๏ธ in progress

THOUGHTS.

โ€ฆ