DEV Community

Book Review: Accelerate

Mario Fernández on March 07, 2021

This seminal book aims to answer one simple yet fundamental question: What makes an organization that develops software successful? This is a top...
Read full post
Collapse
 
learnitmyway profile image
David •

Glad to hear you also appreciated the book! I have two questions that you might find interesting.

  1. Is TBD better because of causation or correlation?
  2. How on earth do low performing teams have any idea what there mean time to anything is!?
Collapse
 
sirech profile image
Mario Fernández •
  1. That's a good point. I've seen tbd being a contentious point in non-TW environments. In the end, you can do continuous integration with pull requests as well (though it requires a lot of discipline), so I guess the important part is to ensure the underlying goal (faster deployments is happening).
  2. Yeah, you can sort the 4 key metrics in order of easier to harder to measure:

releases > lead time > change fail % > MTTR

The easiest thing to measure is number of releases, if you release like once a week then there is probably no point of talking about the others...

Collapse
 
learnitmyway profile image
David •
  1. In the Dev Ops Handbook they mention the value of tension when doing TBD, which could be a reason for causation?
  2. Yeah, that makes sense!