敏捷开发之12条敏捷原则(12 agile principles for Agile Development).docVIP

敏捷开发之12条敏捷原则(12 agile principles for Agile Development).doc

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

敏捷开发之12条敏捷原则(12 agile principles for Agile Development) There are 12 principles in agile development, which are the characteristics of agile practices that differ from heavy processes. Patterns in Agile Software Practices (and, DevelopmentPrinciples, Chinese Title: agile software development: principles, patterns and practices) of these 12 principles are described respectively, I am not here to explain the contents of the book, from my personal understanding to explain these principles, I hope everyone can supplementary insights. 1. our priority is to satisfy our customers by delivering valuable software as early as possible and continuously. When planning iteration stories, you must first provide the most valuable function for the customer according to the priority. Through frequent iterations, we can form good early cooperation with customers, and timely feedback to improve product quality. Agile teams focus on the completion and delivery of user value functions rather than isolated tasks. We used to write detailed requirements using requirements specifications or use cases, and agile used user stories to list requirements. User stories are lightweight techniques that represent requirements, and they have no fixed form and mandatory syntax. However, there are some fixed forms that can be used for reference or are more useful. This template is used in agile estimation: as a user type, I want to be able to [business value].. Using user stories based requirements analysis methods may still require prototyping and documentation, but more emphasis is shifted to verbal communication. 2., even after the development of the late, also welcome to change demand. Agile processes use change to create competitive advantage for customers. Agile process participants are not afraid of change. They believe that changing demand is good because these changes mean that we understand market demand better. 3. often deliver software that can work, and the delivery interval can range from

您可能关注的文档

文档评论(0)

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

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

版权声明书
用户编号:8000054077000003

1亿VIP精品文档

相关文档