Project Utopia
summary
Explains a concrete process: upfront weekly billing instead of fixed bids, a kickoff + discovery + sprint cadence, checklist items (version control, reproducible dev env, CI), and measurable rituals—one-week sprints, standups, demos, and retros. Recommends design sprints early to deliver visible value, insists on pair programming and cross-discipline pairing, under-commit/over-deliver, document domain language, and run small experiments. Gives actionable meeting agendas, demo framing, and how multiple concurrent projects stay manageable.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:10Project Utopia Jesse O'Brien & Caryn Humphreys
- 4:30Takeaways 1. Working collaboratively 2. Pair programming 3. Sprint management 4. Managing meetings 5. Applying Product design
- 14:05Checklist Issue Tracking/ Communication Tools + Version Control + Reproducible, documented dev environment + Automated execution of tests, linting, code quality analytics, other conventions + Documented, single-step deploy process
- 37:03Experiments
