user story

What is a user story?

A user story is a short description of something that your customer will do when they come to your website or use your application/software,  focused on the value or result they get from doing this thing.

重点是 这个 story  value and result, 如果 你不确定 自己的story  写的到底对不对，就要搞清楚，value  or result 到底是什么，找到最根本的东西

User stories are:

• written from the point of view of a person using your website or application
• written in the language that your customers would use.

How to write user story

The basic technique is simple. You take this format: An an [actor] I want [action] so that [achievement].

actor: the customer or the user, figure out the actor, if you can not figure out , then you have to reconsider whether you need it. 不能写customer或者 user,需要写具体的用户类型，如DBA，如果确实想不到，需要考虑用户建模，

action: describe what will happen , not how it will happen, should not too detailed. 写清楚用户要做什么，但是不能具体怎么做，

achivement: the value or the result, describe the purpose of the feature, if you can not think up the achivement, then you have to reconsider whether the feature is import or not  用户这样子做的目的是什么，考虑一下value

when to use user story

User stories should be written at the beginning of your project, before you start making any decisions about technical solutions or design. Once they’re written they should be prioritised, from most important to your customer to least important. One of the beauties of Agile is that you can keep writing and reprioritising your user stories throughout the development period. - 在 agile  team里面，应该是一直都有在写user story，因为总是会不断的有story，只能说，如果一个task 没有 user story的话， 是不能  groom

Why use user stories?

user stories don’t make you think about how something will be implemented; instead they focus on the who and the why. This lets clients/commissioners/Product Owners bring their expertise to bear on defining the who and the why, and lets designers and developers bring their expertise to bear on the how. -更加方便 沟通，不会太具体的东西，用户不需要关注你的细节如何实现，只要关注 why and who, 设计和开发可以更加关注 how

方便创建task，然后用来做计划以及估算时间

在整个 agile process里面，都可以进行增加 删除和修改

可以让开发从用户的角度来思考问题

link from here

https://www.boost.co.nz/blog/2010/09/user-stories