User Stories and the Alternatives

[@ThugLifeModafocah]

I believe you can just give the feature a name, acceptance criteria and then write the details as Scenarios of the guerkin language of BDD.
Feature: User account creation
Acceptance Criteria:
* Should require the user email
* Should require the user password
* Should not allow the password to have less than 5 characters
* Should not allow the password to not have capital letters...
Scenario: When user informs a password with less than 5 characters
Given the user informs a password with less than 5 characters
When the user actionate the login button
Then he should see a message that his password hasn't the minimum accepted length
And he should not be able to create his account
Something like this...

[@frotes]

I always hear use user story all the time in agile but was struggling to find good practices to outline needs that don’t start from the user without going back to the old ways of just requirement/function specs. Really good to see these alternatives

[@vivekkadoo]

Very Insightful ... How come very less views for such an important topics.. It helped a lot .Thanks Scrum Team.

[@ScrumInc]

Our pleasure!

[@YourTechHomeboy]

Extremely valuable