8. ── Alberto Brandolini
It is not the domain expert’s knowledge that goes
into production, it is the developer’s assumption of
that knowledge that goes into production …
“
37. 規格 v1
User Story Requirement
As a Role,
I want to …
So that…
▌User Story
Background…
Epic
User
Story
User
Story
User
Story
▌Acceptance Criteria
• User can do XXX
• User cannot do XXX
• Changes & di
ff
erences
• Out-of-scope
注意可讀性。
保持 High-level 的活動與規則,
明確表⽰責任範圍並減少 UI 與技術細節
48. Example Mapping 經驗談
• 當所有問題都被解決時,就可以結束了。
• 不必堅持要窮舉所有實例(時間有限),重點是探索你不知道的東⻄
• 可以在進票前(確定即將要開發前)進⾏,每次 30-50 mins
• 當 Rules & Examples 多出原先的期待,可以考慮拆新的 User Story 並重新調
整時程
• 注意:⼩⼼過於發散,重點在解決疑問上。因此主持⼈要注意時間,可以⽤
Time Box 協助。
49. 規格 v1.1
User Story Requirement
As a Role,
I want to …
So that…
▌User Story
Background…
▌Acceptance Criteria
• User can do XXX
• User cannot do XXX
• Changes & di
ff
erences
• Out-of-scope
調整 Acceptance Criteria 以符合討論結果
▌Details & Examples
針對⼀些複雜的 AC 規則做補充
• Rule 1 details
• Rule 2 details
• Rule 3 details
55. 精煉過程:⽤ Gherkin 表達預期⾏爲
Scenario:升級爲 VIP
Given Judy 是⼀名⼀般會員
And Judy 已經累積積分 40 點
When Judy 下單了 3000 元買了⼀臺腳踏⾞
Then 訂單下單成功
And Judy 收到了⼀封成功訂購的通知信
And Judy 積分變成 50 分
And Judy 升級爲 VIP 會員
56. 規格 v2
User Story Requirement
As a Role,
I want to …
So that…
▌User Story
Background…
▌Acceptance Criteria
• User can do XXX
• User cannot do XXX
• Changes & di
ff
erences
• Out-of-scope
加上 UI 畫⾯與細節邏輯補充
▌Details & Examples
挑選出複雜的規則,⽤⽂字、表格或是
Gherkin 來舉例表達
• Rule 1 details
• Rule 2 details
• Rule 3 details
▌UI Details
Given…
When…
Then
• Link: https://
fi
gma…
• User steps
• Component interaction