Enjoy fast, free delivery, exclusive deals, and award-winning movies & TV shows with Prime
Try Prime
and start saving today with fast, free delivery
Amazon Prime includes:
Fast, FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with Fast, FREE Delivery" below the Add to Cart button.
Amazon Prime members enjoy:- Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
- Unlimited Free Two-Day Delivery
- Streaming of thousands of movies and TV shows with limited ads on Prime Video.
- A Kindle book to borrow for free each month - with no due dates
- Listen to over 2 million songs and hundreds of playlists
- Unlimited photo storage with anywhere access
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, your membership will automatically upgrade to a monthly membership.
Buy new:
$14.60$14.60
FREE delivery: Tuesday, March 19 on orders over $35.00 shipped by Amazon.
Ships from: Amazon.com Sold by: Amazon.com
Buy used: $12.99
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Scrum and XP from the Trenches (Enterprise Software Development) Paperback – June 11, 2007
There is a newer edition of this item:
Purchase options and add-ons
- Reading age1 year and up
- Print length140 pages
- LanguageEnglish
- Dimensions5.98 x 0.35 x 9.02 inches
- Publication dateJune 11, 2007
- ISBN-101430322640
- ISBN-13978-1430322641
Customers who viewed this item also viewed
Editorial Reviews
Review
Henrik's book is a starter kit of basic practices that help teams move beyond trying to do Scrum to executing Scrum well.- Jeff Sutherland, Co-creator of Scrum
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.- InfoQ.com
A great contribution to the body of Agile knowledge, and a fun read!- ExtremePlanner.com
The most useful book on agile development that I've read, and I've read lots of them!- Lisa Crispin, Author of Agile Testing
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
Product details
- Publisher : Lulu Press, Inc. (June 11, 2007)
- Language : English
- Paperback : 140 pages
- ISBN-10 : 1430322640
- ISBN-13 : 978-1430322641
- Reading age : 1 year and up
- Item Weight : 2.31 pounds
- Dimensions : 5.98 x 0.35 x 9.02 inches
- Best Sellers Rank: #3,153,265 in Books (See Top 100 in Books)
- #4,107 in Software Development (Books)
- #4,806 in Microsoft Programming (Books)
- Customer Reviews:
Important information
To report an issue with this product or seller, click here.
About the author

Henrik Kniberg is a coach and consultant at Crisp in Stockholm, he has spent many years working at Spotify, LEGO, and other product companies. Henrik’s background is a mix of development and management, and his passion is applying Lean and Agile principles to help companies improve. Henrik is the author of "Scrum and XP from the Trenches", "Kanban & Scrum, making the most of both", and "Lean from the Trenches". He is a popular keynote speaker at conferences worldwide, and author of viral videos about Spotify engineering culture and Agile product ownership. Henrik lives in Stockholm with his wife and four kids, and in his “spare time” plays bass and keyboard with two local bands.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
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. Principle: give control, don't take control. Corollary: move authority to information, not information to authority.
4. Determine overall sprint goal prior to closing the planning meeting. This ensures the necessary supporting condition of clarity is in place.
5. Launch the team and get managers, coacher, owners, out of the way. Again, giving control to the people who know (the coders, testers, developers).
6. Always test the product with a demo before saying "done." This emphasis on actual products is very helpful, especially when changing business cultures where sometimes there is a tendency to think in terms of vague changes in mindset. Instead, we should focus on specific behavioral changes that we can observe and measure.
7. Conduct an assessment of how the Sprint went and measure team velocity. This would apply to following up on whether behavioral changes are sticking or not?
OK, well, that seems clear enough but when it came down to it, what was the leadership team actually working on -- the parallel to the code the developers were writing? Well, I think the code (sometimes I call it the DNA) for the company's culture is written in the policy documents that give authority for making decisions and detail how we will interact with each other. The cultural "coders" work on these policy documents in the same way the software developers work on the code.
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. If you are wondering about concrete implementation after reading Ken Schwaber's books, then this is the book for you! Also 4 starts because its small, which is also an advantage. There is no unnecessary blah blah in the book, Henrik tells how it is!
A recommended book for Scrum practitioners and people starting with Scrum to learn about "How Henrik did it!" :)
Kniberg's writing style is informal, taking a conversational approach, which I found refreshing and somewhat humorous.
Top reviews from other countries
Ignoring the paper, quality of the images, and some of the errors in the language used, the content is actually very useful. It's basically how one company does Scrum and XP, and so I found it interesting to compare how the company I work for does it against the company that Henrik Kniberg works for does it. I certainly picked up a few ideas that I will propose trying where I work, some of which could be big improvements, making things more efficient and more sustainable. It also reminded me that a few things we used to do, we have slipped out of the habit of doing. Reading this has spurred me on to get those things done again as they did add value. Of course, there are also things that the author's company does that we do differently, and I see no reason to change. As the author says, there are many ways of doing things with Scrum, and each team/company should identify what works for them.
So, for me as somebody who has been working in a distributed Agile team, doing both Scrum and Kanban, as well as aspects of XP (which the book touches on, but not in detail), this book has been useful in spurring me on to make some changes. I suspect it would be very useful for people completely new to Agile as well.
Recommended.
In questo testo si possono reperire tante informazioni pratiche che dimostrano, con un approccio molto pragmatico, l'implementazione delle pratiche Scrum e XP. Copre quasi tutti gli aspetti, ad un livello di approfondimento non eccessivo ma di certo più che sufficiente, ed è davvero leggero da leggere e facile da capire.
Sebbene a mio parere non esista in assoluto una pratica migliore di altre su come essere agili, questo libro illustra un approccio sicuramente efficace. E rappresenta sicuramente un ottimo inizio per cominciare a conoscere le pratiche agili.



