User Stories

This is the granular level of information that is commonly used for designing the Product. In the beginning when we have just started to think about the features of the product then User Story

Would bring the all necessary inputs.

Let's understand one story. You are the Product Manager and you need to bring the real features for electronic wearables. Already multiple electronic wearables/watches are available in the market.

As Product Manager, you have conducted the survey to just have ideas from the different age groups of people from different cities. Now you need to understand this survey and bring the validated features. User Stories are used to make life simple for the Product Manager who actually always involves ambiguity. Yes, you heard it right, the Product Manager does not have a clear cut answer as yes or no.

User Stories would bring some kind of qualified understanding and using this he/she can introduce these features to the crossfunctional team and thereafter it would be incorporated.

Now, understand, how to Write the User Stories. While collecting the response from different surveys, the Product Manager segregates similar requirements to one individual group. Analyze the data and make User personas. We already know about what User Personas mean and how to design the User Personas.

After careful analyzing and proper validation, User Stories be created and their structures are:

AS A ...............................

I WANT .............................

SO THAT.............................

Now just understand, here it would have the exact profession(demographics data), their actual needs (Requirement), and goal which they want to achieve.

I am sure you would like it by solving problems using this structure.

<USER: Working Professionals>

AS A "Working professional"

I WANT "to measure the number of steps and sleeping pattern,"

SO THAT "I could evaluate my health."

<USER: Diabetic>

AS A "Diabetic patient"

I WANT "to monitor my blood pressure"

SO THAT "I Could monitor my health."

Above two User Stories, we understand that it must include two features in the wearable device:

1. Calculate the Number of steps and must identify the body postures so that wearables calculate the sleeping hours and pattern

2. Measure the blood pressure level

The Product Manager would bring the features to be validated and thereafter features would be added and these features would increase the probability of the product's success.

While creating the User Stories, it should follow one small principle(INVEST) which is shown as:

I- Independent(Story should be independent with other User Personas)

N- Negotiable(Must be negotiable with respect to other features)

V- Valuable(Brings value to the organizations)

E- Estimable(Allow metrics measurement)

S- Short(Should be short enough to accomplish)

T- Testable(It could be tested and verified).

This is how User Stories be created and the Product managers bring the new features which should solve the user's need.