Skip to content
0:00 / 0:00

#agile#scrum#object-orientedprogramming

The Dehumanisation of Agile and Objects • James Coplien • GOTO 2017

GOTO Conferences

1M subscribers • 111 videos on Hallway • Conference channel

YouTube
  • Recommended by 4 people: 1 on Lobsters and 3 in engineering communities.
  • A classic. People kept recommending it from 2018 to 2022.
  • Presented by James Coplien, Lean/Agile Process & Architecture Coach
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

56K views8 years ago4 recommendations

Software designTools and practiceCode review and teamworkDesign patternsHistory of computing

James Coplien explores the history of Agile and object-oriented programming, arguing they have lost their human-centric roots.

This presentation was recorded at GOTO Berlin 2017. #GOTOcon #GOTOber gotober.com James Coplien - Lean/Agile Process & Architecture Coach; Founder of the Pasteur Organizational Patterns Project @jamescoplien5257 ABSTRACT It can easily be argued that agile grew out of the spirit of object orientation: its focus on change, on anthropomorphism, and on people. Alan Kay saw objects as a way for people to connect with their environments through their machines. As late as the 1980s people were still talking about anthropomorphic [...] TIMECODES Intro A Family Tree The Agile Manifesto Genetic Epistemology Where have objects gone wrong? Where has Agile gone wrong? Agile has lost its roots and the good parts are little understood The Common Enemies Restoring Focus Elusive lands over the horizon Organizational Learning Models Failure to Dream Download slides and read the full abstract here: gotober.com/2017/sessions/297 RECOMMENDED BOOKS Subramaniam & Hunt • Practices of an Agile Developer • amzn.to/2XjbWor Uncle Bob • Clean Agile • amzn.to/3tpAqb5 Derby, Larsen & Schwaber • Agile Retrospectives • amzn.to/3hB4eNk Kent Beck & Cynthia Andres • Extreme Programming Explained • amzn.to/3muIlCm Jeff Sutherland • Scrum: The Art of Doing Twice the Work in Half the Time • amzn.to/2X4GQAD twitter.com/GOTOcon linkedin.com/company/goto- instagram.com/goto_con facebook.com/GOTOConferences #Agile #AgileManifesto #XP #AgileDevelopment #JamesCoplien CHANNEL MEMBERSHIP BONUS Join this channel to get early access to videos & other perks: youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket at gotopia.tech Sign up for updates and specials at gotopia.tech/newsletter SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily. youtube.com/user/GotoConferences/?sub_confirmation=1

Why it's here

4 people recommend this

What people say. Recommended for its historical perspective on Agile and for clarifying that daily standups are meant for planning rather than status updates.

Moments people linked to

u/BrownBearPDXin r/ExperiencedDevs • Recommends

On “Tested shitty code vs high quality code without tests”

…pile of crap you own, if it is such. It's your only hope. Adding anything to the pile will be just more dead developer souls and crap. Then ... do it simply with tried and true tooling and simple patterns that you can explain to a 7 year old ... and stick to it. \------------------------------------------------------------------------------- [video [video watch the whole thing [video [video [video **[video [video [video [video [video [video…

u/sinagogSoftware Engineerin r/ExperiencedDevs • Recommends

On “Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones”

Coming from a historical perspective, Agile isn't a methodology. It's a movement - it has a manifesto. Twenty years ago, a bunch of prominent names in the industry got together to talk about what they had in common. This amazing talk by Jim Coplien has an agile family tree at the linked timestamp, but includes: 1. Toyota Production System (1950) 1. New New Product Development Game (1986) 1. Scrum (1993) 1. Extreme Programming (1996) 1. Simula (1967) 1. OO (1980) 1. Patterns (1992) 1. Agile (2001) Proponents of these systems came together, and discussed what they all had in common. The result was The Agile Manifesto, linked above. The manifesto itself is 68 words: > #Manifesto for Agile…
2View on Reddit

GeoffWozniakon Lobsters • Recommends

The Dehumanisation of Agile and Objects

u/adorable-commitsin r/ExperiencedDevs • Recommends

On “Do You Find Daily Scrums/Stand-ups to Be Useful?”

I used to wonder until I heard a talk by James Coplien where he explained that standups aren't meant to be a status update - they're meant to be a mini-sprint planning. (roughly 35 min mark) The idea is that it gives the team an opportunity to change what they're doing (pivot) based on the feedback, eg if a story is bigger than it seemed then it can be re-prioritized. It doesn't really work if a) no one pays attention other than management, and b) you can't change the sprint plan. If you don't mind the screaming, that whole talk is worth a listen. I don't agree with him about unit tests but he's got a lot of valuable wisdom and experience with Agile.