本文阐述了如何撰写SMART用户故事，区分Epic、User Story与Feature，强调了拆分用户故事以提高开发效率。通过实例讲解了如何确保每个故事与业务目标和角色相关，并介绍了如何将大需求分解为小任务便于并行开发。
Short verb phases that describe what people do。
Purpose:
- Visualize product backlog
- Identify goals that deliver value
- Develop strategy to iteratively construct software
How to write user stories (“As a X I want Y so that Z)
- Be smart
- Specific
- Measurable
- Actionable
- Relevant
- Timebound -- e.g. a due date
Difference between an Epic, User Story, and Feature
- Features: “A cohesive bundle of externally visible functionality that should align with the business goals and objectives”
- e.g. “Calculate the tuition for a student, who is enrolled full-time.”
- Epic: A "big" User story that cannot be done in one sprint
- e.g. As a user, I can backup my entire hard drive.
- User Story: User need, Smallest unit of work in an agile framework
How to split user stories
- Why? smaller stories are easier to develop and manage, and allow parallel development.
Traceability – Every user story should trace to at least one business objective and at least one user role
扫一扫
6044
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
