Adrian Stanek, of Bits in Motion, joins me to relate his success story of transforming his organization's software development process via baby steps.

We can count retrospectives, but that feels like a vanity metric. How do we know if we're actually improving?

Did Facebook's recent outages prove that they're moving too fast? I don't know. And neither do you. We don't have all the information.

Facebook has revealed the cause of their 6-hour outage: human error. I hope those pesky humans learned their lesson! Or is there more to it?

Normally when we think of up-skilling, we think of taking a class. But what if you never use that knowledge? A knowledge option is a tool to reduce this risk.

If your team is open to it, by all means, start doing retrospectives. But if you sense resistance, here are some reasons to start with postmortems.

DevOps is a big topic, and simply knowning where to start can be a mystery. I have two suggestions for how you can start with DevOps today.

Even in a static environment, improvement may slow down, but it doesn't have an upper bound.

"Improving daily work is even more important than doing daily work." — Gene Kim

Next time you have an unexpected outage, take note, document it, and consider coming up with a mitigation strategy.

Sometimes you simply cannot be ready before comitting.