1. Lack of questions is the biggest symptom. It could mean that something is simple or obvious, but ofr anything more complicated, if there are no questions, that probably means you've refined it too much up-front without involving the team.
2. Story Mapping is great IMO, but I think you don't even need that. The key thing is collaborative writing of Product Backlog Items. That's where most of the value comes from.
(I think your actual article is insightful. Yes, I agree with pretty much everything you're saying. It would do the industry significant good to take your insights seriously on this.)
Provocative and useful, Maarten!
Two asks:
1. First, what concrete signals tell you a PM is already over the hill before a ticket hits refinement?
2. Second, which workshop moves help teams co-write just enough: story mapping, example mapping, or thin-slice prototypes?
I am also curious how you keep compliance and accessibility needs from bloating the scope. A checklist or before during after cadence would be gold.
Hi Stefan, I needed some time to think about it.
1. Lack of questions is the biggest symptom. It could mean that something is simple or obvious, but ofr anything more complicated, if there are no questions, that probably means you've refined it too much up-front without involving the team.
2. Story Mapping is great IMO, but I think you don't even need that. The key thing is collaborative writing of Product Backlog Items. That's where most of the value comes from.
Thank you for the clarification, Maarten!
[slightly off topic here, but ...]
I was so "inspired" by that AI generated image, that I posted about the image itself here:
https://mastodon.social/@JeffGrigg/115300798671852955
...
(I think your actual article is insightful. Yes, I agree with pretty much everything you're saying. It would do the industry significant good to take your insights seriously on this.)