Basically, I try to keep the size of my User Stories in the area of 1 to 10 man-days to complete. That keeps me from passing what Mike Cohn calls "Epics" or "Themes" as user stories to the developers, and on the other size stopping my user-stories to be so specific as to imply the solution (they should be describing the problem, not how it should be solved).
As far as content goes, I make sure that my stories contain only business value - it never describes how I (should) satisfy the demand, nor does it "require" non-user-domain knowledge to understand.
Good example: As a content manager, I want all users to have to log in before writing a talk-back, in order to deny them the ability to spam.
Bad example: Add captcha to the web site.
Tasks, on the other hand, are steps towards solving the solution - they describe components & functionality that need to be added / modified. This is where an "Add Captcha" solution comes in. As far as size goes, I try to have each task's size be between 1/2 a day and 2-3 days of work.
Tasks also include a set of standard tasks that apply to each and every feature / requirement / problem / bug, such as:
As long as you have users, user stories can be around things users can do. If you are providing an API for other developers, then they are your users. Things will get more technical at that point (i.e. User can update Employee records)
A user/ actor can be a system, not necessarily a person. Your services will have an API, expected input and results and a service level agreements (non-functional requirements). All of those can be specified in the story card.
Most importantly, your story card should specify acceptance criteria. Accpetance criteria will help drive the developers Test Deiven Development Unit Tests, the automated functional tests and the automated performance tests. If the acceptance criteria is meet, the card is accepted and approved by the product owner.
发布评论
评论（4）
基本上，我尝试将用户故事的大小保持在 1 到 10 个工作日内完成。 这使我无法将迈克·科恩（Mike Cohn）所说的“史诗”或“主题”作为用户故事传递给开发人员，并且在其他尺寸上阻止我的用户故事如此具体以暗示解决方案（他们应该描述问题，而不是应该如何解决）。
就内容而言，我确保我的故事仅包含商业价值 - 它从不描述我（应该）如何满足需求，也不“需要”非用户领域知识来理解。
好例子：作为内容管理员，我希望所有用户在撰写回话之前都必须登录，以防止他们发送垃圾邮件。
错误示例：向网站添加验证码。
另一方面，任务是解决解决方案的步骤 - 它们描述组件和结构。 需要添加/修改的功能。 这就是“添加验证码”解决方案的用武之地。就大小而言，我尝试让每个任务的大小在每天 1/2 到 2-3 天的工作之间。
任务还包括一组适用于每个功能/要求/问题/错误的标准任务，例如：
等等
希望这有帮助，
阿萨夫。
Basically, I try to keep the size of my User Stories in the area of 1 to 10 man-days to complete. That keeps me from passing what Mike Cohn calls "Epics" or "Themes" as user stories to the developers, and on the other size stopping my user-stories to be so specific as to imply the solution (they should be describing the problem, not how it should be solved).
As far as content goes, I make sure that my stories contain only business value - it never describes how I (should) satisfy the demand, nor does it "require" non-user-domain knowledge to understand.
Good example: As a content manager, I want all users to have to log in before writing a talk-back, in order to deny them the ability to spam.
Bad example: Add captcha to the web site.
Tasks, on the other hand, are steps towards solving the solution - they describe components & functionality that need to be added / modified. This is where an "Add Captcha" solution comes in. As far as size goes, I try to have each task's size be between 1/2 a day and 2-3 days of work.
Tasks also include a set of standard tasks that apply to each and every feature / requirement / problem / bug, such as:
etc.
Hope this helps,
Assaf.
我的故事基于类的公共接口。 对于任务粒度，我的目标是半天到两天的工作量。
I base the stories on the public interface of the classes. For task granularity I shoot for work effort of half a day to two days.
只要有用户，用户故事就可以围绕用户可以做的事情。 如果您为其他开发人员提供 API，那么他们就是您的用户。 那时事情会变得更加技术化（即用户可以更新员工记录）
As long as you have users, user stories can be around things users can do. If you are providing an API for other developers, then they are your users. Things will get more technical at that point (i.e. User can update Employee records)
用户/参与者可以是一个系统，不一定是一个人。 您的服务将具有 API、预期输入和结果以及服务级别协议（非功能要求）。 所有这些都可以在故事卡中指定。
最重要的是，你的故事卡应该指定接受标准。 验收标准将有助于推动开发人员测试 Deiven 开发单元测试、自动化功能测试和自动化性能测试。 如果满足接受标准，则该卡将被产品所有者接受并批准。
A user/ actor can be a system, not necessarily a person. Your services will have an API, expected input and results and a service level agreements (non-functional requirements). All of those can be specified in the story card.
Most importantly, your story card should specify acceptance criteria. Accpetance criteria will help drive the developers Test Deiven Development Unit Tests, the automated functional tests and the automated performance tests. If the acceptance criteria is meet, the card is accepted and approved by the product owner.