What do you think?
Rate this book
Scrum and XP from the Trenches
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.
140 pages, Paperback
First published January 1, 2007
70 people are currently reading
1332 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 30 of 136 reviews
October 14, 2011
Scrum and XP from the Trenches was written as the author's testament that Scrum worked for his software development team. Here, Henrik Kniberg shares his actual war stories and shows us why Scrum is beneficial for the company and their clients.
While there are several books about Agile software development and Scrum, explaining philosophies, theories, and all about the conceptual framework, this book went down to the details on how to actually do it. The book begins with a little introduction and headed straight to the 'How-To' chapters starting from the most significant activity for a team to start doing Scrum down to the solutions of challenges they have encountered throughout the process, ended by a checklist for the Scrum Master role. This makes it a light reading experience for someone who is not familiar with Scrum at all. The illustrations and actual pictures really helped me in understanding the concepts especially the different approaches in handling obstacles (i.e. managing testing, multiple scrum teams, and handling geographically distributed teams) which I think are very common in today's software development teams.
I consider this written piece as a case study of the author's team development over a year of actually doing it. The experiments and approaches are explained well. The author did a good job explaining why a particular approach did or did not work and why he recommends a certain way of doing things for different situations.
However, if you are particular with typography and design, you would not like the typefaces used or how the book was laid out. It is just a simple paper full of content.
Overall, I strongly recommend this book to beginners or to those who are planning to apply Scrum for their teams. This is also a good reference even for Certified Scrum Masters.
While there are several books about Agile software development and Scrum, explaining philosophies, theories, and all about the conceptual framework, this book went down to the details on how to actually do it. The book begins with a little introduction and headed straight to the 'How-To' chapters starting from the most significant activity for a team to start doing Scrum down to the solutions of challenges they have encountered throughout the process, ended by a checklist for the Scrum Master role. This makes it a light reading experience for someone who is not familiar with Scrum at all. The illustrations and actual pictures really helped me in understanding the concepts especially the different approaches in handling obstacles (i.e. managing testing, multiple scrum teams, and handling geographically distributed teams) which I think are very common in today's software development teams.
I consider this written piece as a case study of the author's team development over a year of actually doing it. The experiments and approaches are explained well. The author did a good job explaining why a particular approach did or did not work and why he recommends a certain way of doing things for different situations.
However, if you are particular with typography and design, you would not like the typefaces used or how the book was laid out. It is just a simple paper full of content.
Overall, I strongly recommend this book to beginners or to those who are planning to apply Scrum for their teams. This is also a good reference even for Certified Scrum Masters.
February 2, 2020
This book is a must read for every scrum novice or mid level practitioner, which will help avoid common mistakes and give advices about the best approach to do Scrum in a daily basis since the Scrum guide is quite short and theoretical.
About the XP chapter, it's a brief poor summary of the methodology and maybe the title of the book makes you think different.
Last, clearly the author is not a professional writer and the way he writes and the vocabulary shouldn't be the reason to rate this book. It's quite easy to read and re read whenever you find yourself struggling with scrum teams in order to get some good ideas and best practices.
About the XP chapter, it's a brief poor summary of the methodology and maybe the title of the book makes you think different.
Last, clearly the author is not a professional writer and the way he writes and the vocabulary shouldn't be the reason to rate this book. It's quite easy to read and re read whenever you find yourself struggling with scrum teams in order to get some good ideas and best practices.
Read
June 13, 2017good book if you are interested in agile project management
October 21, 2017
That feeling when you already practice Scrum exactly the way described in this book. Overall, it's a great real life manual on how to implement Scrum on the project.
February 26, 2023
(I read the second edition) It was greatly insightful and informative. The added annotations were greatly appreciated, but as the author put it; some things were unnecessary - but was kept.
September 20, 2020
This is an easy to read book, full of examples that everyone can use on their own practice.
The book is written in a very direct format, almost like a dialog. We can feel the wins, the joy and sometimes the frustration of the author.
Most of the examples are described with great detail, however, in some cases, the author skips some steps and does not share the rationale behind the decisions made.
I will take some very interesting ideas from this book, and as an example: "Slack time between sprints".
Finally, to me, the biggest take from this book is: "don't be afraid do experiment", after all, it's all about agility :)
The book is written in a very direct format, almost like a dialog. We can feel the wins, the joy and sometimes the frustration of the author.
Most of the examples are described with great detail, however, in some cases, the author skips some steps and does not share the rationale behind the decisions made.
I will take some very interesting ideas from this book, and as an example: "Slack time between sprints".
Finally, to me, the biggest take from this book is: "don't be afraid do experiment", after all, it's all about agility :)
January 9, 2015
First of all: I like the style of writing. Very informal speech, feels like he's really talking to you, which in turn makes it easy + fun to read and understandable.
Secondly: The content (Henriks experience on Scrum plus tricks and recommendations how to do it) is valuable to me right now and probably anybody who is in the early (or even middle) stages of doing Scrum. But it should be read after already having some basic knowledge of Scrum and maybe even after having some practical experience with it. That way you know where your problems are and can pay more attention to his suggestions.
Secondly: The content (Henriks experience on Scrum plus tricks and recommendations how to do it) is valuable to me right now and probably anybody who is in the early (or even middle) stages of doing Scrum. But it should be read after already having some basic knowledge of Scrum and maybe even after having some practical experience with it. That way you know where your problems are and can pay more attention to his suggestions.
May 26, 2024
This is a solid book. With any 'framework' which states that it does not dictate implementation, it is easy to get lost in how to do the implementation. For some people this can be a struggle. So it is good that Henrik Kniberg came out with something as simple as "well this is how we did it".
It's important to know that implementation of Scrum is also an iterative process which tends to develop over time, and this does come across in Kniberg's book, especially the 2nd edition (the one that I read). The way it is presented is just the content of the 1st edition with additional note panels, some of which are used to berate the original text with reasons why he now understands the old thinking was bad. So it is like seeing iterative improvements in action.
The book is short and simple to read, and had a chatty style which might suit some readers more than others. All the features of Scrum are covered and Kniberg goes into some detail in most of them depending on their nuances. I found myself glossing over some paragraphs because I don't do those things on my team, but they were still interesting and I'm sure I will read them again if I do implement those things.
I think there were a few parts which needed more information, for example Kniberg doesn't discuss who should be present at Sprint Demos/Reviews, which is often a question I ask myself. I expect it is in the Scrum guide, but it would have been helpful to know Kniberg's thoughts on this and some other things.
There is a chapter on doing XP which I didn't really get much out of - it is not given as much though as Scrum which was a little disappointing. But this is followed by an excellent chapter on Testing.
Overall a recommended read to help team leaders and scrum practitioners simply see how someone else implemented Scrum, and what worked for them and what didn't. There will be useful information for all readers, even if it is simply validation that someone else is doing what you are doing.
It's important to know that implementation of Scrum is also an iterative process which tends to develop over time, and this does come across in Kniberg's book, especially the 2nd edition (the one that I read). The way it is presented is just the content of the 1st edition with additional note panels, some of which are used to berate the original text with reasons why he now understands the old thinking was bad. So it is like seeing iterative improvements in action.
The book is short and simple to read, and had a chatty style which might suit some readers more than others. All the features of Scrum are covered and Kniberg goes into some detail in most of them depending on their nuances. I found myself glossing over some paragraphs because I don't do those things on my team, but they were still interesting and I'm sure I will read them again if I do implement those things.
I think there were a few parts which needed more information, for example Kniberg doesn't discuss who should be present at Sprint Demos/Reviews, which is often a question I ask myself. I expect it is in the Scrum guide, but it would have been helpful to know Kniberg's thoughts on this and some other things.
There is a chapter on doing XP which I didn't really get much out of - it is not given as much though as Scrum which was a little disappointing. But this is followed by an excellent chapter on Testing.
Overall a recommended read to help team leaders and scrum practitioners simply see how someone else implemented Scrum, and what worked for them and what didn't. There will be useful information for all readers, even if it is simply validation that someone else is doing what you are doing.
February 28, 2019
Wow! This book is a must read. Not only because it is short, well written and freely available online, but because it does what very few books manage to do lately: actually showing you how to practically apply the knowledge and the consequences of that. Basically, it's like a technical book with a story.
As the title suggests, Scrum and XP from the Trenches is a book about software management, moving step by step through all the requirements of the management process in a Scrum environment and showing in detail what Henrik's actual implementation was, the problems he encountered, the options he had and why he chose one, the other, or a combination thereof. Even if he talks mostly about Scrum, he does mix in the elements of XP that he thought worthy of borrowing, making this not a book on any management theory, but of a real life process.
As previously mentioned, the book is freely available on InfoQ, although you are highly encouraged to buy the book to support Henrik Kniberg and other endeavours like his. A must have for any manager or team lead, and a very good read for any developer, having the chance to glimpse at a real software work environment.
For me I am glad to have read it and to see more of my current job in the book than the previous one, which means I have actually moved upwards and not only horizontally.
As the title suggests, Scrum and XP from the Trenches is a book about software management, moving step by step through all the requirements of the management process in a Scrum environment and showing in detail what Henrik's actual implementation was, the problems he encountered, the options he had and why he chose one, the other, or a combination thereof. Even if he talks mostly about Scrum, he does mix in the elements of XP that he thought worthy of borrowing, making this not a book on any management theory, but of a real life process.
As previously mentioned, the book is freely available on InfoQ, although you are highly encouraged to buy the book to support Henrik Kniberg and other endeavours like his. A must have for any manager or team lead, and a very good read for any developer, having the chance to glimpse at a real software work environment.
For me I am glad to have read it and to see more of my current job in the book than the previous one, which means I have actually moved upwards and not only horizontally.
June 13, 2025
Voy a empezar por decir que este NO sería un libro que recomendaría a día de hoy.
¿Por qué le doy entonces 4*? Porque fue el libro con el que yo empecé a entender como aplicar los marcos de trabajo ágiles allá por 2011-2012. Este libro es una implementación concreta de Scrum con XP, la implementación que Henrik hizo en sus equipos en 2005-2007 y que plasmó en este libro explicando sus motivaciones y como le funcionaba a ellos. Evidentemente esta implementación concreta no funcionaba por igual para cualquier equipo (ni el libro lo pretendía) pero tener un enfoque práctico concreto de como aplicar las cosas era una maravilla allá por 2011 entre tantos manuales exclusivamente teóricos o muy centrados en valores, principios... pero no en prácticas concretas ni en proveer de un paso a paso.
En su día era un libro muy notable. Hoy día el libro está bastante desfasado, y cualquiera que esté al día de tendencias "recientes" (de hace 15 años fuera de España, y quizás 5 dentro de nuestras fronteras, porque aquí en agilidad seguimos yendo con una década de atraso) así lo percibirá, y así lo percibió Henrik cuando en 2015 escribió la segunda edición, que reseñaré próximamente.
Por último, y el motivo por el cual reseño en español, es que el libro que leí en su momento fue la traducción de Ángel Medinilla, disponible en la web de Proyectalis y que me parece una buena traducción aunque nunca pasara de la fase "borrador" y no esté dada de alta en goodreads.
¿Por qué le doy entonces 4*? Porque fue el libro con el que yo empecé a entender como aplicar los marcos de trabajo ágiles allá por 2011-2012. Este libro es una implementación concreta de Scrum con XP, la implementación que Henrik hizo en sus equipos en 2005-2007 y que plasmó en este libro explicando sus motivaciones y como le funcionaba a ellos. Evidentemente esta implementación concreta no funcionaba por igual para cualquier equipo (ni el libro lo pretendía) pero tener un enfoque práctico concreto de como aplicar las cosas era una maravilla allá por 2011 entre tantos manuales exclusivamente teóricos o muy centrados en valores, principios... pero no en prácticas concretas ni en proveer de un paso a paso.
En su día era un libro muy notable. Hoy día el libro está bastante desfasado, y cualquiera que esté al día de tendencias "recientes" (de hace 15 años fuera de España, y quizás 5 dentro de nuestras fronteras, porque aquí en agilidad seguimos yendo con una década de atraso) así lo percibirá, y así lo percibió Henrik cuando en 2015 escribió la segunda edición, que reseñaré próximamente.
Por último, y el motivo por el cual reseño en español, es que el libro que leí en su momento fue la traducción de Ángel Medinilla, disponible en la web de Proyectalis y que me parece una buena traducción aunque nunca pasara de la fase "borrador" y no esté dada de alta en goodreads.
April 15, 2020
Simple. Practical. Quick read! I'm a seasoned Agile / Scrum practitioner. So initially I felt it very basic and a bit outdated and thought may not add real value to me. However Henrik's writing style (especially those comments he added in the second edition of the book) engaged me through out and things got interesting and insightful gradually. I could really finish the entire book in one - go! (it's rather a paper, which author wrote it just over the weekend it seems.)
I liked the specific examples and various approaches the author and his team tried out before figuring out what best suits them. The key message throughout the book (which is my core belief too) is that - 'There's no one size fits all solution'... We need to keep experimenting and find the best possible option for our specific teams and again focus on continuous improvement.
The topics on XP practices, Agile testing and multiple teams are very insightful. I can't say that I agree with everything what is written in this book. But there's a lot for all of us (whether you are Agile beginner or a seasoned) to take back from the book. Give it a try. You'll not be disappointed.
I liked the specific examples and various approaches the author and his team tried out before figuring out what best suits them. The key message throughout the book (which is my core belief too) is that - 'There's no one size fits all solution'... We need to keep experimenting and find the best possible option for our specific teams and again focus on continuous improvement.
The topics on XP practices, Agile testing and multiple teams are very insightful. I can't say that I agree with everything what is written in this book. But there's a lot for all of us (whether you are Agile beginner or a seasoned) to take back from the book. Give it a try. You'll not be disappointed.
May 3, 2020
Title Tiếng Việt là "Scrum và XP từ những chiến hào"
Đây là một quyền must-read với tất cả những ai quan tâm đến Agile Software Development nói chung, hay chỉ đơn giản là tò mò về Scrum/XP. Tác giả là Henrik Kniberg, là một người rất giỏi về Agile, Lean nói chung hay cụ thể với Scrum, XP và Kanban nói riêng.
Đây là một quyển sách thực chiến, nói về kinh nghiệm thực tế của tác giả khi thực hành Agile với Scrum và XP, chi tiết ở mọi góc cạch với từ
- mọi events, artìacts, actors, practises trong Scrum, XP
- làm việc với team nhỏ, hay Scaling Scrum
- coding, testing, quản lý con người, quản lý code etc...
Ngoài ra, ở 2nd edition, tác giả còn bổ sung thêm vào những bài học mà trải qua thời gian mới lĩnh hội được, rất thẳng thắn và rõ ràng. Giúp nâng cao mức độ "thực chiến" của quyển sách, cũng như hiểu thêm rõ ràng hơn về mindset Agile: Non-fixed, Inspect & Adapt...
Quyển sách thực sự giúp người đọc có góc nhìn thực tế khi cụ thể hoá được những principles, practises trong Agile, Scrum và XP một cách dễ hiểu và "thực dụng". Tuy nhiên việc áp dụng mù quáng là ko hợp lý, như tác giả đã mention
"There really isn’t a one-size-fits-all – just about any approach can be highly successful or a total failure depending on the context.". Keep experimenting
Some Take Aways:
Basic things for success: work in cross-functional teams, visualize things, deliver often, involve real users, automate your tests and release process, and experiment a lot. The basic agile principles, really.
The value of stuff half-done is zero
Yesterday's weather technique
"Story breakdown to Tasks" is a great opportunity to identify dependencies
Story's Acceptance Criteria helps understand expectation, but "How To Demo" make everything better
Slack time between sprints is crucial
Release-planning with acceptance thresholds
Đây là một quyền must-read với tất cả những ai quan tâm đến Agile Software Development nói chung, hay chỉ đơn giản là tò mò về Scrum/XP. Tác giả là Henrik Kniberg, là một người rất giỏi về Agile, Lean nói chung hay cụ thể với Scrum, XP và Kanban nói riêng.
Đây là một quyển sách thực chiến, nói về kinh nghiệm thực tế của tác giả khi thực hành Agile với Scrum và XP, chi tiết ở mọi góc cạch với từ
- mọi events, artìacts, actors, practises trong Scrum, XP
- làm việc với team nhỏ, hay Scaling Scrum
- coding, testing, quản lý con người, quản lý code etc...
Ngoài ra, ở 2nd edition, tác giả còn bổ sung thêm vào những bài học mà trải qua thời gian mới lĩnh hội được, rất thẳng thắn và rõ ràng. Giúp nâng cao mức độ "thực chiến" của quyển sách, cũng như hiểu thêm rõ ràng hơn về mindset Agile: Non-fixed, Inspect & Adapt...
Quyển sách thực sự giúp người đọc có góc nhìn thực tế khi cụ thể hoá được những principles, practises trong Agile, Scrum và XP một cách dễ hiểu và "thực dụng". Tuy nhiên việc áp dụng mù quáng là ko hợp lý, như tác giả đã mention
"There really isn’t a one-size-fits-all – just about any approach can be highly successful or a total failure depending on the context.". Keep experimenting
Some Take Aways:
Basic things for success: work in cross-functional teams, visualize things, deliver often, involve real users, automate your tests and release process, and experiment a lot. The basic agile principles, really.
The value of stuff half-done is zero
Yesterday's weather technique
"Story breakdown to Tasks" is a great opportunity to identify dependencies
Story's Acceptance Criteria helps understand expectation, but "How To Demo" make everything better
Slack time between sprints is crucial
Release-planning with acceptance thresholds
June 27, 2020
I keep asking for real-world applications of scrum to be able to learn from. This book provides it, communicates it in simple easy-to-read language. It reads like someone talking to you over coffee about their experiences with scrum and why they picked certain options and followed them.
I immediately lifted a couple practices from the book. One was setting sprint-goals, I hadn't wanted to do it as my team has so many projects and services to work on. Doing it though revealed the complexities of the team and why we rushed through our standups so quickly. That lead to the next practice which was breaking the team into two, but the two being feature based rather than service based. Also making the times for the two standups one after the other. That way I could attend both and if people worked on several features they could attend both too. It really worked better I thought.
Highly recommend it!
I immediately lifted a couple practices from the book. One was setting sprint-goals, I hadn't wanted to do it as my team has so many projects and services to work on. Doing it though revealed the complexities of the team and why we rushed through our standups so quickly. That lead to the next practice which was breaking the team into two, but the two being feature based rather than service based. Also making the times for the two standups one after the other. That way I could attend both and if people worked on several features they could attend both too. It really worked better I thought.
Highly recommend it!
May 8, 2017
Reading old books opens up an interesting window in time about the values and practices in the past. It allows us to understand the timeless values more deeply, as well as explore opportunities for improvement in line with the recent advances in tech, etc.
While Scrum and XP are over two decades old, a lot of teams still struggle with the basics. For those teams, this is a great book. On the other hand, for seasoned teams, this book is perhaps too elementary and not worth the time. In any case, it is a good reading over and evening, and if you are starting your agile journey, you will come out with some practical insights that most people won't tell you - even in an agile or a scrum class! So, based on your context, decide if this book helps you or not.
While Scrum and XP are over two decades old, a lot of teams still struggle with the basics. For those teams, this is a great book. On the other hand, for seasoned teams, this book is perhaps too elementary and not worth the time. In any case, it is a good reading over and evening, and if you are starting your agile journey, you will come out with some practical insights that most people won't tell you - even in an agile or a scrum class! So, based on your context, decide if this book helps you or not.
August 8, 2022
Книга, хотя и написана относительно недавно, на мой взгляд уже устарела. На это сильно повлиял коронавирус и повсеместная работа из дома, что привело к необходимости онлайн-адаптации всех механизмов скрама. Не понравилось, что автор всё рекомендует делать на бумажках на большой доске. С современными программами по управлению задачами этот совет выглядит старомодным. Что касается самой теории скрама, то в книге не нашел для себя чего-то особо полезного. Автор пишет о прописных истинах, которые могут заинтересовать преимущественно новичков. Те же, кто уже работает со скрамом и канбаном, данную книгу, вряд ли, оценят.
August 25, 2017
This book would be a valuable read to anyone doing or considering doing Scrum. It isn't anything mind blowing or jaw dropping, but it also shouldn't be. This is a story of how Scrum can be adjusted and adopted. A source for thoughts and inspirations for your own version of Scrum and organising software development.
This is one of those books which anyone could have written, but no one else has, at least not so concise, clear and useful. For some reason, I enjoyed "Lean from Trenches" more, but this one's good too.
This is one of those books which anyone could have written, but no one else has, at least not so concise, clear and useful. For some reason, I enjoyed "Lean from Trenches" more, but this one's good too.
August 14, 2020
This book is short but full of great examples on how Henrik best implemented scrum on his teams. It's not a "you should do this cause it's what works" kind of book but rather a "if you also have this problem then you can attempt to do the same we did and maybe you'll be successful too".
I could identify many of these situations with some I lived myself while working for many different companies that say to do agile development, particularly scrum. I only wish I had the opportunity to at least try some of the proposed solutions in this book. Maybe things would be better sometimes.
I could identify many of these situations with some I lived myself while working for many different companies that say to do agile development, particularly scrum. I only wish I had the opportunity to at least try some of the proposed solutions in this book. Maybe things would be better sometimes.
September 16, 2021
A very nice book for Scrum novices. It goes beyond the Scrum guidelines, and covers a lot of specific real world questions and has answered most of my questions including part time workers, scrum of scrums, chief scrum leader, etc. I would highly recommend it to people who are new to Scrum.
The book also recommends other great books which helps me to know what to read next.
Downside: the author chose to comment instead of directly updating the book for the 2nd edition. I would have preferred if he could have directly updated some of the mistakes.
Overall, I highly recommend the book.
The book also recommends other great books which helps me to know what to read next.
Downside: the author chose to comment instead of directly updating the book for the 2nd edition. I would have preferred if he could have directly updated some of the mistakes.
Overall, I highly recommend the book.
December 4, 2022
Yaaaaassssss! A concise book that describes the key aspects of scrum and XP. The examples feel authentic and are easily relatable. Being mostly familiar with the subject, I was able to read the book fairly quickly and skip through each chapter as items on my mental check-list were ticked off. Nevertheless, I enjoyed it and would recommend that all early career software engineers should buy, read and reference it as they move into the 'engineering' aspects of writing code.
This book is my goto!
This book is my goto!
September 17, 2020
Almost everything in this book will read as "obvious" in 2020. You probably have experienced all the best practices this book has to offer. However, back in the past, these practices weren't that obvious. A good read for anyone starting a career in programming. It will help you understand why people spend time on meta-activities instead of dedicating all the time to programming.
Some advice in this book, like how to use branches in git, is definitely outdated.
Some advice in this book, like how to use branches in git, is definitely outdated.
November 17, 2020
A very useful book to know how Scrum and XP is applied in a successful team. The author is a talented scrum master that has faced different situations similar to the ones that I have suffered by my own. I've reached different solutions but I have to agree with him in the way that his team works.
Very good book for any Scrum lover (with the unique exception to use man-day or any time measure to explain/apply StoryPoints)
Very good book for any Scrum lover (with the unique exception to use man-day or any time measure to explain/apply StoryPoints)
January 28, 2022
The book is well-structured and easy to read, gives very practical tips and ideas how to use Scrum. On the other hand, I was surprised when I was reading about focus factor and continuously changing setup of teams. To be fair, in the second edition Henrik uses strong self-criticism on those parts, I enjoyed how he looked back on it.
I really liked Henrik’s other book, the Lean from the Trenches - probably because of that I started this book with really high expectations. 3 star on 1st edition, 4 on 2nd one.
I really liked Henrik’s other book, the Lean from the Trenches - probably because of that I started this book with really high expectations. 3 star on 1st edition, 4 on 2nd one.
March 27, 2019
Easy reading book. You must get the second edition (the directors' cut), since it has plenty annotations from the author challenging some of his own ideas and validating others on experience basis. The book is all about showing how his teams implemented Scrum and XP (mainly scrum), giving advices and in between teaching some concepts for the rookies.
January 29, 2022
Reread as part of professional scrum developer learning path. Very easy reading, presenting opinion without over verbose stories to try to validate the opinion without becoming too dry and unreadable. As with all hard (impossible?) to proof subjects I’d rather have this style of writing than the more prosaic style of some books that try to validate their opinion that way.
May 15, 2017
War stories! Once you have the grasp of a methodology... you need some war stories to secure your knowledge. This is the book. Tips and tricks coming from real experience to help you to understand the theory of Scrum Framework.
October 30, 2017
I’m a fan of Henrik Kniberg’s practical and no nonsense approach. I found the Director’s Cut notes to be very informational and entertaining, but I wish that he had taken the time to write the ‘focus factor’ out of this second edition.
May 2, 2018
Якщо вам цікаво що таке Scrum і чи підійде він для вашого проекту, то читайте Scrum Джефа Сазерленда. А якщо ви ідете на ваш перший спрінт, тоді прочитайте цю книжку. Тут ви знайдете практичний досвід, tips, lessons learned, different scenarios, все що потрібно for newcommer!
June 6, 2020
É um livro bastante interessante, em que o autor explora diferentes abordagens "fora da caixa" para aplicarmos o Scrum. Além disso, algumas técnicas do XP também são apresentadas o que acrescenta bastante ao time de desenvolvimento. Com certeza, irei testar algumas das ideias apresentadas no livro.
July 3, 2023
This book is a great example of lessons learned along the way by real people on real teams. Those lessons are generously shared with us, the readers. It's not a very deep dive into the topic, but neither was it meant to be.
April 26, 2024
Nice short and breezy read.
Read the second edition and the author's additional notes were much appreciated - would gladly read a third edition now, with newer learnings!
Lots that don't apply to the kind of team(s) I've been working with, but also quite a lot that still does. Food for thought.
Read the second edition and the author's additional notes were much appreciated - would gladly read a third edition now, with newer learnings!
Lots that don't apply to the kind of team(s) I've been working with, but also quite a lot that still does. Food for thought.
Displaying 1 - 30 of 136 reviews