Hello 👋, It’s Vibhor. Welcome to the 🔥 paid member only🔥 edition of Winning Strategy: A newsletter focused on enhancing product, process, team, and career performance. Many subscribers expense this newsletter to their Learning & Development budget. Here’s an expense template to send to your manager.
Have you ever… EVER… ended a backlog refinement session feeling more confused than when you started?
Recently, I watched a product team in a similar situation.
The PO was frustrated, the developers didn’t know where to start, and the SM was desperately trying to keep everyone aligned.
It was all a BIG mess!
It reminded me of my early days when I'd walk into these sessions armed with nothing but a list of user stories and optimism.
Optimism!
Effective refinement sessions don’t need optimism. They need… like everything else… the right process.
In this post, I will share the process that I was forced to develop after years of trial and error and plenty of painful refinement sessions.
I have converted it into a Notion based checklist so it's easy for everyone to follow.
Got an urgent question?
Get a quick answer by joining the subscriber chat below.
Prerequisite
Before we get into the details of backlog refinement checklist, there’s something you might want to check out first.
I wrote a post called Backlog Refinement 101 a while ago.
If you’re new to this whole process or want to brush up on the basics, that post is the perfect starting point.
Without a solid understanding of what backlog refinement is and why it matters, even the best checklist won’t save you.
So, if you need a quick refresher, head there first.
But if you’re already familiar with the basics, let’s get straight to the checklist below!