What’s a retrospective? According to Scrum.org, “The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

https://www.flickr.com/photos/pdamsten/50765755578 I was speaking to a friend recently about a production incident he was involved with. He said he noted several things that could be improved to help the team with their response.

Recently someone asked me, “Does code have to be tested by code to be considered tested? Who tests the code that tests the code?

A few years ago, one of my friends took a new role and talked about the work we’d been doing on DevOps.

Measuring humans changes behavior and often not how we’d like. Some metrics are more dangerous than others. The most dangerous metric goal I’ve found so far in software engineering is code coverage.

The job of management is to ensure that staff is fully utilized at all times. Resources are being paid for a day’s work, they need to head down working for at least a full day, preferably more.

Since Accelerate was published in 2018, “DORA metrics” have become increasingly popular for measuring IT performance. More vendors are creating dashboards or integrating these metrics into their existing pipeline tooling.

I frequently find myself in conversations about Scaled Agile Framework (SAFe) and its utility or lack thereof. My opinions are based on both direct experiences in an organization that started using it and from comparing notes with colleagues in other large organizations, including many who are SAFe certified.

Continuous delivery can be a frustrating topic. Those of us who use this workflow will never go back to legacy ways of working.

A “deepity” is a statement that sounds profound but isn’t. “To the extent that it’s true, it doesn’t have to matter.