曾几何时开始,用户故事的写法成了 用户故事经典句式+验收条件。
在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"
按照笔者的故事叙

本文探讨了如何将传统的用户故事句式转变为更具故事性的叙述方法,以增强理解和交流。通过一个关于高管过滤部门数据的仪表板用户故事为例,对比了经典句式与故事叙述法的差异,并提出了故事的起点、基本步骤和异常情况,强调了在不同场景下选择合适故事表达方式的重要性。
最低0.47元/天 解锁文章
109

被折叠的 条评论
为什么被折叠?



