USER STORIES: A TECHNICAL JARGON
We all have a little concept connected with the word “Story.” Maybe a childhood memory of listening to bedtime stories, the one who made you cry, or the one you never get tired of. Some stories live within you forever, while others are an integral part of your life. Either fiction or real-life, everyone has a story.
Since we are not up to discuss a novel or a book review here, what does a story have to do with a software development process? What does a turbo geek have to do with a story?
IS USER STORY A TECHNICAL JARGON?
Well, luckily enough, “User Stories” are easy to understand on both ends. They are actually written to make that mutual connection and understanding, which is missing most of the time, between the clients and the business developers.
User Stories are usually in natural language, an informal, formal description of what a customer truly wants.
Don’t get confused with System Requirements.
Sometimes a user story is confused with the system requirement documents. Requirements are a more formal description of user or project needs. To make it simple, user stories are like pointers to that direction in which you want to ultimately see your product.
WHAT PURPOSE DO THEY SERVE?
These stories are written from the perspective of the one who wants a new functionality or service; usually, the customer or user of the system is a short, precise, mostly casual, and simple explanation of the product/feature.
You don’t need a high-level programming software to get this done; user stories are initially written on sticky notes or small cards and are stored properly before the scheduling, discussion, and development. From an engineer’s point of view, it helps to answer questions like
• Who we are working for
• What we are working for
• What are the goals?
• Why we are building it
• What benefit will it bring to the end-user?
HAVING A FORMAT FOR YOUR WISHES
Agile doesn’t force you to have a proper format for User Stories, even though you can get correct parameters and avoid common mistakes by following the one you can get correct parameters. Mostly developers’ team and product owners don’t speak the same language. A User story enables both to understand the specific target. Anyone can write it, but it should not be written for the sake of writing. Utilize the proper words to show what you really want.
If you remember that old American TV series “Dragon Tales” in which Emmy and Max used this rhythm every time, “I wish I wish with all my heart….” User stories are mostly like a wish list. They typically follow this simple format:
As a [your role], I want [some objective] so that [benefits or values] For example,
As a user, I want my website design to be responsive, so that visitor’s screen size and orientation change the layout accordingly.
