讲故事的用户故事样例之1

曾几何时开始，用户故事的写法成了 用户故事经典句式+验收条件。
在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：
【这下面的步骤是达成故事成功进行的，达成故事的目的】

1. executive select the department drop-down
2. system list all departments in drop-down
3. executive choose a specific department
4. 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那个故事当中。