How to design behavior with user stories

1. Knowledge

   

   Processes captured in the everyday language of the end user.

1. User stories are written from a user's perspective, and describe how and why the user is using the software.
2. User stories should satisfy the INVEST principles.
3. For a user story to be ready for development, the team should be able to describe the technical tasks (develop, test, deploy) for the bug fixes and new features required to complete that user story.
2. Strategy
1. Just about all user stories follow this structure:
1. As a <type of user>, 
2. I want <some goal>, 
3. so that <some reason>.
2. User stories must be prioritized by the product owner so that highest value features are completed and delivered first.
3. Execution