4 ms·
The first thing mentioned in this article can be summed up: minimize pauses. He calls it "eliminate dependencies" but it's really about finding out where work s
by koliber 3y ago
The first thing mentioned in this article can be summed up: minimize pauses. He calls it "eliminate dependencies" but it's really about finding out where work stops and needs to wait for something.
This is so important. It's one of the key tenets of agile (not only software agile, but real world agile too) as embodies in the TPC (Toyota Production System).
I recently wrote a bit more on this topic if you're interested in that aspect of speeding up product velocity, or improving the overall efficiency of any system: https://koliber.com/articles/the-waits-cause-all-the-pain https://koliber.com/articles/the-waits-cause-all-the-pain
- peterbell_nyc 3y agoLean software development has a lot to say about this too - check out anything on value stream mapping and if you haven't already, try "Principles of Product Development Flow". It's dry but good.
- koliber 3y agoYou’re right. I worded it poorly in my original reply. I fixed it.
- mratsim 3y agoIt's not dependencies, it's bottlenecks that you need to fix.
- makerdiety 3y agoYeah. Sleeping during a marathon defeats the purpose of a marathon. Which is to test your superhuman ability and seeing if you can run without resting or stopping.
- koliber 3y agoIt used to be common wisdom that for hyper marathons you needed to sleep. People thought that you can not run a few days non stop. And then Cliff Young proved that theory wrong. And now they run non-stop, at least for the Sydney to Melbourne Ultramarathon.