曾幾何時開始，用戶故事的寫法成了 用戶故事經典句式+驗收條件。
在https://blog.versionone.com/agile-acceptance-criteria/ 上提供瞭如下一個故事的樣例。
As an executive, I want to be able to filter the dashboard by department so that I can isolate data by a specific department.
Acceptance Criteria:
Given the Executive Dashboard default view, when I select the department drop-down, I have the ability to select a specific department to so only that data throughout the dashboard.
Given the department drop-down, when I select a specific department, the entire dashboard filters to display only that department data.
以上的故事正文就是故事經典句式所帶來的一句話，加入了2個GWT，講故事的味道顯得比較淡。
討論的問題有
“Hey Product Owner, does the Executive need to be able to Multi-select several departments?”
“How about grouping by division?”
"who can access the Executive Dashboard"
按照筆者的故事敘述方法（也稱爲講故事方法，Story telling），試着來改寫下以上故事，看看兩個不同方法的比較。【此括號爲說明，不是故事的內容】
Title: filter the dashboard by department
【簡短的故事標題有利於看板展現和交流】
Brief:
As an executive, I want to be able to filter the dashboard by department so that I can isolate data by a specific department.
Start Point： the dashboard is shown
【明確整個故事的起點，有利於展開後續的故事情節】
Happy/Basic Steps：
【這下面的步驟是達成故事成功進行的，達成故事的目的】
- executive select the department drop-down
- system list all departments in drop-down
- executive choose a specific department
- the entire dashboard filters to display only that department data.
- 4.1 department data is grouped by division(@furture，此標記意味着本次不包括，未來再考慮).
Sad/Exception Steps:
【這下面的步驟是上述正常步驟中可能碰到的異常步驟，3a意味在是第3步正常步驟出現的第1個異常情況】
- 3a executive choose 2+ departments by shift click or multi-selection, only first department will be choosen, or no response.
對於who can access the Executive Dashboard這個問題，本用戶故事的起點是dashboard is shown，因此這個問題不在這個用戶故事的範圍之內，應當是在show dashboard那個故事當中。