Articles for category: Drive

What is your Overload?

We each have our own limit. Where we get to the end and then we go into overload. The key part is to ensure that we don’t go beyond that, that we operate at it or below it. We also know when it’s coming and to take on more, is asking for it to happen. The worst time to worry about Overload, is when you’re already overloaded, it’s too late, you have no bandwidth. The best time, is before it happens, way before it happens, when you are so far away from it that it can’t happen.  That’s the best

July 1, 2023

Greg Thomas

Who is the Expert in the Room?

It’s the person not declaring themselves as the expert. The person who works on the problem leads the team, stands up, and figures out what is going wrong and how to fix it. They don’t declare themselves expert and would never dare to declare themselves as such. But to everyone else on the team, they are the defacto expert and much more so than the one that is standing up to say “I’m the expert, I’m the master, ask me.”

June 27, 2023

Greg Thomas

The Gap Between Codes and Tickets

There is much discussion about what is written in a ticket and what is actually coded. In some cases, there is alignment, in others, it’s a quick close and onto the next ticket. In this case, the ticket doesn’t tell the story. The solution isn’t to shut down the world while you’re building and reworking all your tickets. The solution is to ensure there is alignment on what the final solution and if there is some “figuring out to do” while you’re coding, to update the ticket after the fact. When teams do this, not only do the developers know

The Simple Timer

The simplest path to getting rid of distractions, focusing on the work you need to do, and feeling good about it afterward is right in front of you. Pick a time, start the timer and don’t stop until it beeps.

June 21, 2023

Greg Thomas

Where Agile Burndowns Break

We all aim for the lines to intersect on a Burndown, and if we’re doing it right they intersect in the middle. The goal of course is to start with what you work on and finish it by the end of your sprint. The problem with Burndown charts is that if you add work, they don’t change, the math is the same as any history says – you add more work to do in a short time frame, and some of it isn’t getting done without herculean efforts. But regardless, we run the burndown and spend all of 30 seconds