Inspect & Adapt, then What?
summary
Examples from PowerReviews and Hearken show concrete changes: the team drops time estimates and remove estimation by splitting features into small tasks and sequencing by scope instead of time; one moderation tweak is given a dollar value and $1,500/day saved so it leaps the queue; a rule enforces short-lived branches (delete after a day) to force small, frequent merges; a startup replaces weekly prioritization with a scripted Friday showcase (using Elm on the frontend) to drive weekly goals and demos.
AI-written summary · about
chapters (17)
- 0:00Start
- 0:58Agility
- 2:09Agile
- 7:36PowerReviews
- 8:35Planning Problem #1: Estimation
- 11:20Replace with small, similar tasks by splitting feature?
- 12:32Often don't have to do everything
- 13:57Planning Problem #2: Prioritization
- 21:04Value-Based Sequencing
- 21:24Example: Fraud Flags
- 22:19Value Calculation
- 23:25This can't work!
- 26:53Problems
- 28:20Communication
- 31:56New Product Weekly Planning
- 33:13Script-based Planning
- 35:35Context Matters
related talks
45mPanel Discussion Refactoring
43mScalable Best Practices for Your Development Team
22mContinuous Improvements of The Code Review Process
33mTen Angry Comments Later: Stories About Code Reviews, Teams, and Yesterday’s Code
25mDeveloper Joy – How great teams get s%*t done
38mCompassionate Refactoring
45mKeynote: On the Care and Feeding of Feedback Cycles
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal