"The vibes were off": Adapting Agile story points estimation to technical writing
summary
Adapts story points to technical writing by building a team-specific scoring rubric, storing scores in Jira number field and importing results with the Jira Cloud for Sheets plugin, then analyzing averages and trends in Google Sheets. Finds most tickets cluster at one–two points, only 6% exceed ten and the max is 17, and the team consistently completes 10–12 points per week per writer. Lessons include overlong scale, late calibration, busted completion dates, and that the system meaningfully reduces vibe-based estimates.
AI-written summary · about
chapters (13)
- 0:00Welcome
- 2:28Traditional metrics fail
- 5:18Vibes-based estimation problems
- 7:27Story points for tech writing
- 8:50Goals and non-goals
- 11:16Scoring rubric design
- 13:22Scoring rubric factors
- 16:31Work categorization
- 18:39Key statistics
- 20:46Mistakes and lessons
- 26:45Implementing story points
- 28:55Next steps
- 30:18Q&A
related talks
35mGo Big with Supercharged Agile
05mIgnite - How to Use Scrum Poker to Slay Estimations
57mThe Science of not estimating
41mI Estimate this Talk will be 20 Minutes Long, Give or Take 10 Minutes
35mScrum Overview
46mEstimates and complexity: a tale in 42 and a half minutes
01h 02mAgile Metrics: Velocity is NOT the Goal
01h 02mImproving Performance of Agile Teams using Statistical Analysis