Agile: Users Stories

Had some interesting discussions around User Stories in Agile.  Unfortunately I see far too many “developers” focus on technical aspect that results in acceptance criteria immediately. Real authors take time to write stories and edit them on a semantic vs. syntactic level.  This is you write a User Story like regular author you’d  have a story with begining problem, journey, and an end that has the problem solved.  Then examine whether the actual story provides value.  Then finally looking at how to measure success (acceptance criteria) or rather measurement strategy…if the solution that is built really meets the spirit of the story rather than an artificial measure that doesn’t related to the value or operation or only the operation of the story.

Advertisements

About briankseitz
I live in PacNW in a small town and work for Microsoft as a Enterprise strategy and architecture SME. I enjoy solving big complex problems, cooking and eating, woodworking and reading. I typically read between 4-8 business and technology books a month.

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s

%d bloggers like this: