It’s Difficult to Give User Story Advice over the Internet

I often get and see questions on internet forums related to helping someone slice their User Stories or Product Backlog Items. This can be very difficult to do, because the slicing conversation really requires so much context around the parties/teams involved, the nature of the business domain, and the technical structure of the system under development. Due to this complexity, this is why I always recommend that Product Owners and Development teams do slicing together in Product Backlog Grooming sessions.

Another problem with trying to provide the needed context to give good advice is that most people work at organizations that have some sort of information security policy that would be violated by providing enough context.

The best route that I’ve seen is trying to come up with a fictional story/PBI/context that demonstrates the key challenge that you’re having without improperly offering too much confidential information.

Another approach would be to have you and your team try Richard Lawrence’s User Story Splitting flow chart.

Anyway, I wish you well, and think about trying some of the suggestions above!

Other Good User Story Links


One Response

  1. […] [EN] It’s Difficult to Give User Story Advice over the Internet […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: