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.

Code coverage is the measure of the amount of code being executed by tests. It’s an easy number to measure and a minimum value is frequently set as a goal.

Are you leading teams and want to make sure they are productive? There are many ways to do that. Many are doing it incorrectly.

Ah, holiday traditions. Christmas carols, Black Friday, Cyber Monday, fruit cake, egg nog, and change feeze. It’s that time of year again where companies everywhere stop allowing production changes.