Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your email address or mobile phone number.
Scrum and XP from the Trenches (Enterprise Software Development) Paperback – October 4, 2007
Top 20 lists in Books
View the top 20 best sellers of all time, the most reviewed books of all time and some of our editors' favorite picks. Learn more
Frequently Bought Together
Customers Who Bought This Item Also Bought
Henrik's book is a starter kit of basic practices that help teams move beyond trying to do Scrum to executing Scrum well.
Henrik goes on to describe some of the more difficult - and rarely covered - aspects of working in an agile organization, including coordinating the efforts of multiple Scrum teams.
A great contribution to the body of Agile knowledge, and a fun read!
The most useful book on agile development that I've read, and I've read lots of them!
From the Back Cover
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.
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
More About the Author
Top Customer Reviews
This book is an extremely well written (almost narrated) account of the issues they encountered and how they overcame those. You will immediately relate to those and will find yourselves saying ..."ahh thats it!" This book is very well written and is very easy and quick to read.
Because the book is a narrative of someone's efforts, it is also easily read by people who dont really know Scrum. I have given copies of this book to people who i want to get excited about Scrum, so that they themselves will realize that there are alternatives out there to doing software development, rather than the traditional waterfall process.
First, you can decide to support the author and purchase the paper book, like I did, or you can download the free version from: [...]
Then, the book itself. It's structured fairly logically. It starts with looking at the Product Backlog, from there goes over all the Scrum meetings in chronological order. For every meeting, the author describes how he did it in his company, what other things he tried and what his conclusions were.
After all the Scrum meetings, the book dives in a couple separate topics, like combining Scrum with XP practices, having breaks between sprint and some other topics. It ends with scaling and distributed teams, common questions.
The book is basically a how-to book, though its very clear that it just gives an example, to make Scrum more concrete, but does recommend for everyone to look for "their Scrum" instead of blindly copying the suggestions in the books. This is also the books strength, it provides very concrete tips without saying "this is how it must be done".
I have different experiences than the author in some areas, which makes me frown sometimes, though I enjoyed Henriks explanations. They helped me gain a different perspective on some issues.
I was doubting between 3 and 4 stars for this book. 3 stars would be since the book doesn't offer more than it promises. It is an experience story of Henrik and didn't add much surprises or extra content. Also 3 stars since its so small. 4 stars would be because there is probably not any more concrete Scrum story than this one.Read more ›
Why? Because we had urgent issues of mounting chaos. We were not advancing. It was obvious from Henrik's luminously clear descriptions of practice that Scrum could be a solution.
This book served us very well in setting up. Everything Henrik says is practical, and images leap to your mind from his words. You read him, and you know what to do.
This is not to say that we haven't had problems and questions. Starting Scrum is challenging. Henrik doesn't provide all the answers. But he is very helpful indeed, and this book is very good.
I read Henrik Kniberg's book, Scrum and XP (Extreme Programming) from the Trenches, on his suggestion and, well, he's right!
Kniberg's book is a concise "how to" on how his company implements Agile in their software development business. It's chock full of great ideas and details that come only from those that have actually practiced something. As such, I gained a good insight into how Agile and Scrum work, and you will too.
What I want to explore more, however, is the idea that Agile can be applied as a model for leadership, or, more precisely, how can the practices of Agile be applied more broadly to knowledge workers? I think the best way to think about it to briefly recap the points of Agile and at every point where you see the word "product" think "culture." Let's see how that works.
1. The Agile process starts with describing stories about how the product should work. The focus is not on how things aren't working but how they should work. Process step 1: collect stories.
2. In preparation for the sprint planning meeting, have the product backlog (the list of stories about how we want our culture/product to be) in shipshape. This means being clear about the outcome including an defined "when done." This invokes the element of clarity and measurability. When we do workshops on changing culture this reminds me of the step where I ask, "...and how would we know...."
3. Have the sprint planning meeting with the team. Allow the team to determine the scope of what projects will be included in the upcoming sprint.Read more ›
Most Recent Customer Reviews
Using this book as a guide for ramping up a scrum project. It was recommended to me by a colleague from another office location. So far so good.Published 11 months ago by Paul
I am the type of person who learns a lot more from a quick example than from a lengthy explanation. Although tons of information on Scrum and agile development exist, I was having... Read morePublished 14 months ago by Christof Leuenberger
I thought this was an extremely practical book and found it very useful on my Scrum project. Highly recommend it. It is a very quick read and well worth the time.Published 16 months ago by LovetoLearn
I have bought this book but it is one-time reading one.
The content of the book is good. But the quality is very poor. Pages just fall of from the book.
It's just one guy's story, and he says pretty clearly that your mileage may vary. But, if you're trying to get your mind around Scrum & XP and how it would look/feel to work on a... Read morePublished on October 13, 2011 by Todd Trimble
I make it a point to give out this book for all new team members. Great, short and engaging reading with practical, real-life examples.Published on June 8, 2011 by S. Chatterjee
If you are new to Scrum, you need to read this book. It's not introductory, you have to learn before the basis of Scrum, but after that, take this book and read it completely. Read morePublished on May 4, 2011 by José M. Blázquez
We started to use this book a year ago. Looking backward, it helps a lot to establish simple, effective and successful development process. Smart and humble. Highly recomended.Published on February 27, 2010 by Dorian Averbuch