YOUTUBE Avs70dZ3Vlk Martin Fowler presents What Does Tech Excellence Look Like
We're not saying that high performance in IT causes a good organizational performance, but we are saying they go together. Don't take this insight too far because correlation isn't causation.
Key performance criteria are 1. Deployment Frequency 2. Deployment lead time 3. Mean time to recovery -- 5:57
"Meantime to recovery is more important than mean time between failures for more failures" -- we're learning it's more important to respond than to try prevent.
Cycle time is really important to get feedback on our ideas.
There's discussion about gambling, and good bets. Martin makes a point that you get a bigger payoff for knowing a little bit of information about a bet than what your gut might tell you.
If you think there shouldn't be silos in organizations, you're living with false optimism. You can't avoid these, but you should think about making these into business oriented teams.
How to keep your cycles healthy -- 22:00
If you say you've got to go as fast as possible, you're just going to break down. The software development function is concerned about the health of the vehicle. The vehicle in this case is the codebase, but also the team. Are the team working well with each other, are they learning.
This is a sense of a well functioning technical organization from conversations that Fowler has had with people around industry. He asks can we do this throughout a big organization? The answer is no, it has to be done in pieces.