[Myth Busting] What Is A User Story?

(Australia)

August 29, 2020

What's up, awesome people? I hope you are having a good weekend. Recently, many people asked me how to write a perfectly detailed user story. Many of these people came from project management and business analysis background. Many people think that User Story is about a template for writing requirements. Is this what user stories is about? Well, we have to listen to Ron Jeffries, as one of the individual who came up with the User Story practice, to know what User Stories is about. In today's vlog, I visualise the real concept of User Story based on Ron Jeffries blog. Hopefully it can give you a better overview that User Story is not about the template. I also bust other myths on user stories on this vlog. Let's reduce this misconception about User Stories in the industry together. Thanks for watching this video folks.

What did you think about this post?

Share with your network

Comments (6)

Guru Rao

10:57 am August 29, 2020

It was a best article which I had gone through, thanks for sharing with us!

Source: https://tractorguru.in/seco...

Pablo Matti

09:24 pm August 29, 2020

So what about technical work? If it is not done with a user story? Thabka

Sujit

11:07 pm August 29, 2020

I think technical work will not be called as a user story, but, it is a part of user story. So, we can refer it as a task which is carried out as part of the user story, in order to get the story done, in order to deliver the increment.

Joshua Partogi

06:32 am August 30, 2020

You can write Product Backlog item as UML or Use case. That's why I said don't be bounded by tools like JIRA. Just because it is not listed as option in JIRA, it doesn't mean you can write the PBI with other techniques or format.

Govindraj Tungenwar

06:59 pm September 27, 2020

Nice short and sweet video. I am agree with you writing user stories is a complimentary practices NOT described in Scrum Guide. The characteristics of user story INVEST - Independent, Negotiable, Valuable, Estimable, Small, Testable and the Acceptance criteria characteristics - SMART - Specific, Measureable, Achievable, Relevant, Time Bound.. Cheers

Raghu

02:51 pm July 24, 2021

Backend or technical work can be defined at story level as well. In an other framework, it is called "enabler" story which do not follow any template. However, it is recommended to link it with user story/feature to which the "enabler" serves.