awesome-talkscurated list on GitHubRecommends
Under “Methodologies”
7 minutes, 26 seconds, and the Fundamental Theorem of Agile Software Development by **JB Rainsberger** (Øredev 2013) 00:07:42
0:00 / 0:00
#agile#essentialcomplexity#accidentalcomplexity
7 minutes, 26 seconds, and the Fundamental Theorem of Agile Software Development
jbrains762
639 subscribers • 1 video on Hallway
- Recommended by 2 people: 1 in engineering communities and 1 curated list.
- Presented by J. B. Rainsberger, software development consultant
Intermediate. Assumes working knowledge.
31K views8 years ago2 recommendations
Software designTools and practiceDesign patternsRefactoring and legacy codeSimplicity and complexity
J. B. Rainsberger explains how minimizing accidental complexity through refactoring is the core value of Agile software development.
Fred Brooks' essay "No Silver Bullet" taught us that no single technique can bring us an order-of-magnitude improvement within a single decade. In spite of this, from his ideas of essential and accidental complication, we can conclude something stunning about the nature of agile software development. This talk was recorded at Øredev conference 2013, and yes, I named this talk "7 minutes, 26 seconds" before I went on stage. :) Many thanks to Øredev for recording this talk.Why it's here
2 people recommend thisWhat people say. Recommended as a classic talk on Agile, estimation, and managing complexity.
u/LogicRaven_in r/ExperiencedDevs • Recommends
On “Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones”
There is none I know of.
Estimates are worthless, because we mostly work with complex tasks, where the time needed for the unkown factors can overweight the time needed for the known factors with a magnitude or two.
This creates such a big variation in time needed that even if you pad your estimates with a high %, there will be cases when you will be over estimate.
So if your environment requires estimations, them do your best educated guess, but don't sweat over it. If you go over estimate, communicate and update expectations as soon as you have a better estimate.
link to this video
link to this video