3 tips for better planning meetings


Imagine a 4-hour scrum planning meeting where you talk, discuss stories, estimate points, drag things into the sprint, and quietly question your life choices.

I've done my fair share of those. It's not fun.

But there are three things you can do to never have a boring planning meeting again.

1 — Groom the backlog ahead of time

Having 400 items in the backlog is not a goldmine where profit will be made once you eventually reach the ones on the bottom.

The truth is that old stories are less than worthless; they have negative value, and most are probably no longer relevant to the current business situation.

A clean backlog with as many relevant items as possible is a productive backlog.

Ideally, if you're working in small chunks, your backlog is just what you're about to tackle next.

2 — Prepare and collaborate ahead of time

Get your team members to contribute to well-defined tickets ahead of time. Nothing is more wasteful than having one person type in missing information while the rest of the team watches.

The meeting is there for a good discussion and for making decisions, not writing tickets.

3 — Facilitate a structured meeting

Timebox in advance, make sure the decisions that need to be made are on the menu and ensure the discussions stay relevant to the goals—no tangents.

Here's the thing...

As a strategic lead, you are responsible for ensuring that your planning meetings are valuable and engaging.

But doing that requires zero tolerance for boring, wasteful gatherings and investing time in setting up the processes and guidelines that ensure your meetings are palatable.

They won't be "fun," but they'll be valuable and efficient, and that's the goal.

Yours,

Taj

The TP Daily Newsletter

Hi, I’m Taj Pelc. I write about technical leadership, business mindset and enterpreneurship. Daily advice on building fantastic tech teams that deliver great products. I'll see you inside.

Read more from The TP Daily Newsletter

I was making a sandwich analogy. The butter makes things run smoothly. The other components are good tech/business alignment, an agile dev process, testing, and automated deployments. To succeed, you can't get just some parts right; you need to get all the parts right. However, one of the most underrated aspects is the developer experience. I'm constantly surprised by how much pain people suffer through just because it's always been this way. Here's what you can do today ... Make it run in a...

Yesterday, I attended the Czech Executive meetup in Brno, which was held in a WWII-era bunker. As the communists had a top-secret base there, I thought creating a little old-school digital business card to share at the networking event might be fun. I generated the code with Claude, uploaded it to GitHub pages, and programmed an NFC tag with the URL so that you can just tap it with your phone. A hacking game in the middle "protects" the links to my website. Eat the red packet, and you're...

Find out how much <the thing you want to do> is worth. This can help in two ways. If it’s internal it helps you to prioritize and focus on doing the most impactful things. If it’s for a client it helps you set a price as a fraction of that value. That’s not always easy, but it’s worth it. Problem is people don’t even try. Here’s what you can do. Break it down into spefic measurable outcomes like increased sales, time saved or reduced costs. Then assign a reasonable estimate to each. Like 10%...