I’m no scrum master so take this with a grain of salt. I can see the need for user stories, it’s just that they don’t always work. They are designed to convey a lot of information in a simple sentence but they often degrade to a vague sentence about nothing.

The format of a user story is typically:

As a role, I want goal

But this can lead to someone saying:

As a user of the site I want to view events

As a user of the site? As a user of a kite? As a user of a volcano? It’s probably as a user of the site. Users usually want to view things too. This same sentence could simply be:

Events listing

That’s the name of a feature and everyone gets what you mean. User stories sometimes state the obvious and when it gets to that point you may as well use a dot point.

Kickstarter Coming January

I'm launching a board game called Delivery Duck. You're a duck, in a truck, delivering packages. It's a strategic family game for 2 to 6 players.

Check out the board game!