InfoQ

Minibook

Scrum and XP from the Trenches

Posted by Henrik Kniberg on Jun 27, 2007

Community
Agile
Topics
Stories & Case Studies ,
Agile Techniques
Tags
Introducing Agile ,
Collaborative Technologies ,
Distributed Teams ,
XP ,
Scrum


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

168 pages, 6" x 9", ISBN: 978-1-4303-2264-1

Free download

Courtesy of Henrik Kniberg and InfoQ.com, we're happy to offer a free version for download, to get this knowledge in as many peoples hands as possible. Login to download this book FREE (PDF)

Buy the print version for $22.95

If you enjoyed reading the free (non-printable) download version, please support the author and InfoQ's book series by buying the print version for only $22.95.

Translations

Here you can find the translated versions of the book:

  • French version, thanks to Guillaume Mathias, Bruno Orsier, Emmanuel Etasse, Christophe Bunn
  • Chinese version, thanks to Jacky Li
  • Japanese version, thanks to Shoichi Goto
  • Spanish version, thanks to Ángel Medinilla
  • Portuguese version, thanks to various volunteers
  • Russian version, thanks to various volunteers
  • German version, thanks to Robert Sösemann & Andreas Schliep
  • Traditional Chinese version, thanks to Ko Jen-Chieh

Table of contents

Foreward by Jeff Sutherland

Foreward by Mike Cohn

1. Introduction

2. How we do product backlogs

3. How we prepare for Sprint planning

4. How we do Sprint planning

5. How we communicate Sprints

6. How we do Sprint backlogs

7. How we arrange the team room

8. How we do daily Scrum

9. How we do Sprint demos

10.How we do Sprint retrospectives

11.Slack time between Sprints

12.How we do release planning and fixed priced contracts

13.How we combine Scrum with XP

14.How we do testing

15.How we handle multiple Scrum teams

16.How we handle geographically distributed teams

17.Scrum master checklist

18.Parting words

Recommended reading

About the Author

About the Author

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.

  • This article is part of a featured topic series on Scrum

Educational Content

Brian Marick on 4 Challenges and 5 Guiding Values of Agile Software Development

Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).

Are You a Software Architect?

The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?

Agile – A Way of Life and Pragmatic Use of Authority

The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.

Getting Started with Grails, Second Edition

"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?

Using ITIL V3 as a Foundation for SOA Governance

Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.

Adrian Colyer on AspectJ, tc Server and dm Server

SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.

Adam Wiggins on Heroku

Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.

SOA as an Architectural Pattern: Best Practices in Software Architecture

For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.