-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refs #3 Signed-off-by: Tony Deng <[email protected]>
- Loading branch information
Showing
2 changed files
with
13 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,3 +11,4 @@ | |
* [规划发布和迭代](ch1/1.6.md) | ||
* [什么是验收测试?](ch1/1.7.md) | ||
* [为什么要变成用户故事?](ch1/1.8.md) | ||
* [小结](ch1/brief.md) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
# 小结 | ||
|
||
- 故事卡包含对用户或客户有价值的功能和简短描述 | ||
- 故事卡是故事可见部分,但客户团队和开发人员关于故事的对话更重要 | ||
- 客户团队包括那些确保软件符合潜在用户需求的人,可以包括测试人员、产品经理、实际用户和交互设计师 | ||
- 故事卡有客户团队编写,因为他们最了解如何表达需要实现的需求,也因为他们会在后期与开发人员共同确定故事细节并安排故事的优先级顺序 | ||
- 按照故事对客户的价值来安排故事的优先级顺序 | ||
- 将各个故事放入迭代,进行发布和迭代规则 | ||
- 效率是开发人员可以在一轮迭代中完成的工作量 | ||
- 如果故事太大以至于无法在一轮迭代中完成,可以考虑把它分成两个或更多的小故事 | ||
- 验收测试用于验证实现的故事是否开发成符合客户团队的设想 | ||
- 用户故事是很有意义的,因为它们强调口头交流,你和开发人员都可以理解,可用于进行迭代计划,子啊迭代开发过程中能很好的工作,而且它们鼓励推迟细节 |