I can’t remember when there wasn’t some emphasis on participating in a team—starting back in college when our assignments moved from individual to team assignments and continuing into every single job I’ve had since. Even when moving into consulting,...

As I promised in my newsletter (Which you should be reading) I offered thoughts around two books or at least an article series on two topics. What comes next are the core questions I want to answer in each one.

It was about three years before I saw a retrospective that didn’t have the basic three-column setup. You know, the one where you have +, -, Change. Maybe yours is start, stop, continue.

Let’s talk about a situation that happens in almost every team I see. After meeting everyone and getting access to things, I will look at whatever tools they use to manage their work. I do this because while most people are adamant they use the tool,...

Today I’m going to rant a little bit because I’m over-caffeinated, and a few things have come up all related to quality and testing.

There is a lot that I can say about the magic of breaking work down into workable chunks, but I want to focus on one particular lens in this article.

A friend of mine asked a group of us for our little sayings that we keep repeating in our heads as we coach organizations and developers. While I have a few tried and true ones, I put together a list of ones on the spot for him based on my experience...

There exists a trait common to most developers and development groups that causes lots of delays and costly mistakes. That trait is when you believe you can figure it out if you have more time.

Today I’m going to make a few people mad, get a few things that have been bothering me out there, and hopefully, get a few folks to try something a little different.

There are a lot of prioritization techniques that exist, and it’s worth getting comfortable with a handful of them. Each one has strengths and weaknesses, so having a few you can use rounds out your ability to prioritize.