UserStoriesinLeanSixSigmaSoftwareDevelopment.docxVIP

  1. 1、本文档共4页,可阅读全部内容。
  2. 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
  5. 5、该文档为VIP文档,如果想要下载,成为VIP会员后,下载免费。
  6. 6、成为VIP后,下载本文档将扣除1次下载权益。下载后,不支持退款、换文档。如有疑问请联系我们
  7. 7、成为VIP后,您将拥有八大权益,权益包括:VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
  8. 8、VIP文档为合作方或网友上传,每下载1次, 网站将根据用户上传文档的质量评分、类型等,对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档
查看更多
UserStoriesinLeanSixSigmaSoftwareDevelopment

User?Stories in Lean Six Sigma Software Development /members/David-Hallowell/David L. Hallowell February 26, 2010The term “user story” is emerging in the practice of Agile software development, but the notion is very applicable in all types of products and services. A user story is a simple, one-sentence description of what an actor (any person or entity with behavior that expects things of a particular system) would find valuable to be able to do as the actor interacts with a product or service. The simplicity is part of the power. A user story is written in language that the most basic user and most sophisticated system analyst can readily understand?– and which they can review and refine together to reach a shared understanding. That’s a sometimes rare, and always valuable, thing.Examples?of User StoriesA user story is a complete sentence with an actor, a verb and enough context to convey clear meaning. Examples include:“A service technician can anticipate network degradation.”“A patient understands the status of her procedure as she is going through it.”“The search engine suggests alternative spellings that may be more effective.”User?Stories Are Not Use CasesThe focus on verbs makes many people think of use cases. While the verbs and functional view are a common thread, use cases are most often employed to detail requirements into the underlying workflows and exceptions that are implied. In that way, use cases decompose requirements to uncover underlying action that is worth understanding.User stories, on the other hand, are generally more compositional, starting as rough sketches that support the discovery of stated and latent requirements. User stories start with context data and needs data. They may state or imply functionality that should be better understood. A verified and valuable user story may become a requirement. A user story is discovery.Use cases, on the other hand, often start with requirements. Use cases detail workflows, starting conditions and

文档评论(0)

kakaxi + 关注
实名认证
文档贡献者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档