A user story is a atomized (Single idea zettels boost brain connections) chunk of work that needs to be completed on a project that is defined by focusing on the user rather that the engineering solution. The story is complete when it simultaneously meets the spirit of the story as well as the defined Acceptance Criteria (Acceptance Criteria).

It's written in a specific format:

As a {User Type}, I want to {do some action} so I can {achieve some result}.

For example:

• As a dog, I want to have access to my bacon bits all the time so I can always eat the best tasting food.
• As a mom, I want to potty train my son so I can stop fighting him with diapers.
• As a mom, I want to potty train my son so I can stop buying diapers.

Notice how the last two user stories are nearly identical, but the desired result is different. While both are focused on potty training, one is because the mom is having fights with their son and the other is about money. This is valuable insight during the design process.

Citations

• Find writers' true needs with market research

#DPM #toolong