Most teams have heard of the Daily Standup. Fifteen minutes, same time, same place, every day. In Scrum, it's called the Daily Scrum and it's one of the most consistently misunderstood events in the framework.

Done well, it's the heartbeat of the Sprint. Done poorly, it's the meeting everyone dreads and nobody learns anything from.

Ever watched a delivery team being forced to commit to a fixed plan for work they have not done before? Or equally as frustrating, watched another delivery team run experiments to solve a problem that was genuinely straightforward?

Kanban is one of the simplest agile methods to start, which is exactly why it's often misunderstood. Almost every team that puts tickets on a board says they're "doing Kanban." But are they really?

Ever started a transformation and six months in, nobody can actually explain what you're transforming into?

You have invested in DevOps. Tools, training, maybe even external help to get things wired together. And things have improved. Deployments are faster than they used to be. The team knows what a pipeline is and using the right tools.

Most senior leaders can identify their busiest teams. Very few can tell you which ones are high-performing.

Sprint Planning is where the team comes together as one. Not a collection of individuals with separate tasks, but a team with a shared goal, a shared plan, and a shared commitment to deliver.

When it works, that's exactly what it feels like.

When too much repetitive work, meetings, dependencies and quality debt slow everything down, teams stop improving. They get stuck in delivery mode with their heads down, working the same way they always have, with no time or creativity to step back and ask if there is a better way.

I created 3V over a decade ago to help agile software teams move beyond velocity as their only measure of success. The idea was simple: if you only measure speed, speed is all you'll get - and you'll pay for it in every other dimension of performance.

Ever stood in front of a big backlog of initiatives, maybe 50+ all sized but no idea which will deliver more value?

Leaders want strategic alignment, stakeholders are convinced their initiative is critical and Product Owners are trying to maximise the value of the work their teams deliver.

Remember those "guess how many lollies in the jar" fundraisers? Despite best efforts, everyone's guess was wildly wrong. But if you asked people to compare two jars and say which has more? They'd nail it every time.

Ever found yourself in a conversation where someone asks "What exactly is your product?" and you're not sure how to answer?

When my coaching becomes reactive, it loses its power.

Often my teams are busy, their leaders stretched, and as a coach I unintentionally end up responding to the noise rather than focusing on the work that will truly lift performance.

If you’ve ever tried to talk about performance in a team and ended up with everyone nodding politely but thinking completely different things, this one’s for you.

If you feel like your team is constantly putting out fires despite having a CI/CD pipeline in place, you aren't alone. DevOps is a journey, but it often feels like navigating a dense forest without a map.

Why is it that when you ask your stakeholders to prioritise the backlog, suddenly everything becomes a “Must”?

Scrum is one of the best-known agile frameworks. Almost every team has heard of it and many will say they’re “doing Scrum.” But are they really?

Ever been halfway through a piece of work and realised everyone has a different answer to the question: “Who is our customer?”

A Quick Look at the Final Layer

Ever found yourself lost in the detail?

You’re about to start a new piece of work. Leaders want forecasts, the team wants clarity, and stakeholders want confidence. Instead, everyone’s staring at a flat backlog, drowning in tasks with no real sense of why.