Any Product Manager involved in Agile Development would be familiar with the good ol’ user story:
As a type of user, I want feature, functionality, goal so that result, solution to some problem.
And today, I was reminded why. Sometimes user stories feel like a formality, like how you would write a homework plan for your teacher in school. Why can’t we just do?
I was writing a ticket today and as usual, prefaced with a user story for the devs (and me). While trying to fill in the “reason, solution to some problem” bit I realized – I couldn’t remember why this was important.
So I chatted up the requestor and he reminded me why (we had already gone through the whole “is this really necessary” portion). And I was able to fill it in, but more importantly, I knew why it was important, and could gauge the relative importance from there.
Lesson to self not to belittle the good ol’ user story.