The tricky part to agile software development is that there is no manual telling you exactly how to do it. You have to experiment and continuously adapt the process until it suits your specific situation.
This book aims to give you a head start by providing a detailed down-to-earth account of how one Swedish company implemented Scrum and XP with a team of approximately 40 people and how they continuously improved their process over a year's time.
Under the leadership of Henrik Kniberg they experimented with different team sizes, different sprint lengths, different ways of defining "done", different formats for product backlogs and sprint backlogs, different testing strategies, different ways of doing demos, different ways of synchronizing multiple Scrum teams, etc. They also experimented with XP practices - different ways of doing continuous build, pair programming, test driven development, etc, and how to combine this with Scrum.
Your team's constraints may dictate a different configuration of practices (and even compromises), but here is an example of how to approach the "continuous improvement" process that will make your Agile process work best for you.
This book includes:
* Practical tips and tricks for most Scrum and XP practices
* Typical pitfalls and how they were addressed
* Diagrams and photos illustrating day-to-day work
* Testing and test-driven development
* Scaling and coordinating multiple teams
* Dealing with resistance from inside and outside the team
* Planning and time estimation techniques
* Forwards by Jeff Sutherland and Mike Cohn
Download free online version at http://infoq.com/minibooks/scrum-xp-from-the-trenches
Henrik Kniberg is a consultant at Crisp in Stockholm (http://www.crisp.se), specializing in Java and Agile software development. He has founded several Swedish software companies and is passionate about learning, teaching, and applying the art of software development. Henrik takes a holistic approach and enjoys adopting different roles such as manager, developer, scrum master, teacher, and coach. For more info see http://www.crisp.se/henrik.kniberg.
如果用一段话来简单明了的描述一下SCRUM,应该是这样的: 1、我们需要把人进行分割,所以我们建议会组建一些小的团队,人数最好是在3-7人。 2、我们需要把任务切小,拆分成故事卡。 3、团队在一个sprint周期内权利冲刺去完成计划的故事卡。 4、做持续集成去从整体上把握任务的...
评分#阿一读书# 《硝烟中的Scrum和XP》:把它放在《Scrum要素》之后阅读绝对是个明智的选择:两书一本重理论一本重实践,一本是框架一本是方法,一本是授道一本解惑。这本书其实两年前就看过,只是那时候太稚嫩,只看到了最肤浅的东西……
评分首先,个人觉得这是一本不错的小书。 说它小,是因为这本书很薄,100多页吧,无非就是程序开发那点事。说它不错,是因为它很实用,没什么花哨的东西。 其次,这是一本scrum的实施指南。 周围的很多程序员,看了太多的敏捷的思想,听了太多的敏捷的原则,xp、scrum、sprint更...
评分作者对scrum 实践中点点滴滴总结,正中要害。我即将在 团队中实施 scrum,这本书给我很多启示。尤其是对团队成员能力的要求,scrum 是一种方法,而不是一个 对团队成员能力要求的标准,或者注解。一个自我激励,自我组织,提高效率的团队 是一个 理想的 scrum 状态,但这只是终...
评分本书作者是开发团队Leader,本书记录了他带领团队实施Scurm过程中的经验教训。全书短小精悍,言简意赅。 以下是书中一些观点信息的摘抄: 1:Nokia总结出的迭代开发的基本要求: 1.1:迭代要有固定时长,不能超过六个星期; 1.2:在每一次迭代的结尾,代码都必须经过QA的测试...
http://www.infoq.com/cn/minibooks/scrum-xp-from-the-trenches 中文译版,译者李剑。
评分我还是敏捷菜鸟 用这本书草草了解了下
评分让你了解Scrum中各种可能的activity, 以及作者是怎么实施的 --- 貌似作者公司的项目范围比较广,各种各样的情况他们都有所尝试
评分第二版做了不少修正
评分我还是敏捷菜鸟 用这本书草草了解了下
本站所有内容均为互联网搜索引擎提供的公开搜索信息,本站不存储任何数据与内容,任何内容与数据均与本站无关,如有需要请联系相关搜索引擎包括但不限于百度,google,bing,sogou 等
© 2026 book.wenda123.org All Rights Reserved. 图书目录大全 版权所有