Implementing Programmer Anarchy
summary
Claims that stripping managers, BAs and separate QA speeds delivery: teams of 5–8 of poly-skilled developers adopt continuous deployment and microservices. Examples: Forward pushes new code every 3–5 minutes during a workweek; click tracker drops from 32 to 22 servers after a Node rewrite; energy calculator rewrites in Ruby then Clojure and runs on one VM under load; MailOnline replaces 130,000 lines of Java with 4,000 lines of Clojure and finishes front end in months. HR shifts to master journeyman apprentice.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:56Emerging Experiences at...
- 3:39Agile is a Social Change
- 4:21Story Tyranny
- 5:06Requirements Hierarchy
- 6:40Agile Roles
- 7:36Anarchy Roles
- 8:12Fate of Roles: QA
- 10:25Fate of Roles: BA
- 12:10Fate of Roles: Manager
- 16:07forwardtechnology.co.uk
- 18:28Example: Energy Revolution
- 20:51Example: Click Tracking
- 23:34Agile 2013: Implementing Anarchy
- 24:00Transformation Summary
- 26:21Pervasive Change Required: So change everything!
- 27:58People Focus
- 30:04Matching HR Focus
- 32:45Training in Working Together
- 33:57Flexible Project Approach
- 34:43MailOnline Scorecard
- 36:01For last year, creating
- 36:14Like MailOnline, Plus...
related talks
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
32mCode First, Ask Questions Later
46mWhen Software Becomes Everyone's Job
01h 02mSurviving the Innovators Dilemma
01h 00mBeyond the innovator’s dilemma
33mSoftware development practices for companies that want to make an impact
53mHatching software development ecosystems (the gordian knot)
21mScaled Agile DevOps