It is quite easy to operate with a good user story both in development as well as software testing and quality assurance processes. Though mostly used in Agile environments user stories may be of great value to many software projects. I feel there is no need of defining true value of user stories so I will simply skip that part. Straight to the story creation we go.
- Where do I begin? Oh, right, with users. A good user story does what? It is describing possible actions a customer/user may take within your product. This means you will be required to step in your user’s shoes and to see things from his perspective (which is challenging by default as you are aware of your product’s insides). This will go easier if you will focus on step by step scenarios describing one particular action as a login process. Etc.
- Another helping trick is using so called ‘personas’. The goal of this method is in allowing you with a wider view of your stories. Simply create a plausible user and ask what your solution should do to provide this user’s goals with required success. There are even many templates for different personas available for downloads so this step may prove to be easier than expected.
- One man may not work on one story. Good user stories require collaboration. Only developers are never to be in charge of user story creation. Things are best done when both the product owner as well as other involved teams are working on user stories together.
- Stories are to be precise and simple. Great user stories usually are using active voice and contain zero confusion. Leave all the information that does not qualify as essential behind a story. Basically a great user story consists of a persona stating what it wants exactly and why does it want things that way. Other information is unnecessary and is adding complications that are presenting minimal value when resolved. Although this step may be considered personal to any team as projects do tend to differ. Yet it is great in 95% cases.
- Minimalistic stories are actually unachievable without starting with something large and epic. Create big and meaningful user stories consisting of multiple steps and break them in smaller portions. And remember to add criteria allowing user stories to succeed or to fail. Meaning conditions that are to be met for the story to become your personas success.
- Try using visualization like paper cards or any other tools to keep user stories visible all the time.
- User stories are not panacea and your team will never be possible to recreate all your users might be doing within your product. This method is still great, but don’t expect it to cover 100% of all customers will be doing to your software.