Whenever we want to solve a problem or build something useful, we have decisions to make about the tools we choose.

Hope creep is the plague of value delivery. We assume that since something worked in the past it will work again.

I was talking to a friend the other day about how her management is tracking teams’ “maturity” using “DORA Metrics”, the four measures the correlate with high-performing organizations mentioned by DevOps Research and Assessment in “Accelerate” and the State of DevOps reports.

Should we use Scrum? Kanban? Is Kanban for support and Scrum for development? Is Scrum for newbs and Kanban for elites?

In my last post, we talked about common metric anti-patterns that are focused on the process instead of value. In this installment, we will cover alternatives that can help us remove waste and improve the flow of value.

I was speaking at a DevOps meetup in Finland recently and was asked, “what does DevOps mean to you?” I love that they started the conversation that way.

As we try to improve the flow of value to the end-user, the first item that usually gains focus is the productivity of development teams and how to measure it.

The following is fantasy. Any resemblance to persons living or dead is coincidental. However, too many people live this. ScrummerFall Jackie is a buyer who needs better tools for forecasting demand so she can make better-informed decisions.

Delivering value to the end-users means we need systems that are useful, secure, and resistant to the shark-filled acid bath of the cloud environment.

There are many misconceptions about CD. There are also many things about CD that are not obvious on the surface.