Flow: the worst software development approach in history
summary
Asserts Flow is a satire that deliberately combines the worst practices from waterfall, Scrum, SAFe, Kanban and tooling into a money-making methodology, shows a real case where a stalled Java project led to 300 hires from India and never met its deadline after years, demonstrates a burn chart of two years of continuous work without progress, mandates Jira and 20+ board columns, warns interruptions cost 10–23 minute re-entry to coding flow, and sells quick certifications that primarily generate revenue.
AI-written summary · about
chapters (24)
- 0:00Intro
- 8:45Who is Su
- 9:48Who is Kim
- 13:15Sprints
- 16:50Gamification
- 17:51Working space
- 18:27Roles and resources
- 24:36DevOps
- 26:48Meetings
- 32:56Enterprise
- 35:58Nun
- 41:08Manifesto
- 42:58Certification
- 47:08Roles in Flow
- 49:08Evolution
- 49:48Personal communication
- 50:48Trust and safety
- 51:53Focus and flow
- 52:53Continuous learning
- 54:08Governing your own work
- 55:23Hierarchy
- 56:33Experience still counts
- 57:08Reduce complexity
- 57:58Have fun
related talks
33mCI/CD is just the Beginning: Optimize Value Creation with Flow Framework
50mHow Flow Works
43mThe Digital Flow Organisation
50mHow Flow Works & Other Curiosities
29mFlow Engineering - boost velocity, quality & happiness
44mCreating flow at Waters out of thin air
51mImproving Software Flow
31m Finding the Flow