Speed-Up and Accelerate
- Engineering orgs slow down as they age.
- Two different economical models
- A “cost center,” where every engineer hour not spent on features must translate to (at least) one engineer hour saved
- "investment", which speed to delivery, rather than number of engineer hours paid, is the dominant economic factor–and in which considerable, sustained investment in that speed can reap massive economic returns.
- If you can ship faster, you can then gather feedback, and
- Sell to Someone Else
- How to Invest in Latency Reduction
- Activities Engineers Bitch About
- Things Only Person X Can Do
- Look for Queues
- Automated Tests
- Post Mortems (How to Run a Post-Mortem (With Humans, Not Robots), Velocity 2013)
- Decentralization with Safety Nets / Impact Reduction Schemes
This article reminded me of Accelerate: The Science of Lean Software and DevOps1, one of the best software engineering books I've read in 2019.
- They both use the same metaphor "speed" for organization growths.
- They both emphasize on this "growth"/"investment" mindset/model.
The Accelerate book explains why we need to speed up with tons of evidences from the surveys they conducted over the last several years. The Speed-up post explains it in theory. So I would highly recommend you read them both.