<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Agile &amp; Scrum Books | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/category/knowledge/books/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Wed, 04 Feb 2026 16:39:33 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.scrumexpert.com/wp-content/uploads/favicon.png</url>
	<title>Agile &amp; Scrum Books | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Balancing Agility and Discipline</title>
		<link>https://www.scrumexpert.com/knowledge/balancing-agility-and-discipline/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 12 Nov 2025 17:35:44 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[scaling Agile]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8495</guid>

					<description><![CDATA[Balancing Agility and Discipline is a book written in 2004 by Barry Boehm and Richard Turner. The fact that it is already on its 6th reprint tells something about its value. This is a very pragmatic book that tries to put in perspective agile and plan-driven software development approaches. By the way, the funny thing is that the word &#8220;waterfall&#8221; is rarely mentioned in the book. This may be due to its negative connotation and also to the fact that Barry Boehm favors a spiral approach. The book has also adopted a clever structure with a first &#8220;quick-read&#8221; part of 150 pages that provide the core of the material and then 100 pages of appendixes to treat some parts more specifically. After a comparison of agile and plan-driven approaches, the book illustrates its vision of these two processes by presenting two project case studies. It also offers a risk-based approach for making methodology decisions that integrate agile and plan-driven practices. Even the book is not recent, it has the advantage of confronting agile and plan-driven approaches in a relatively objective way. Therefore, it is a very recommended reading for people that want to improve their software development process without wanting necessarily to be a &#8220;purist&#8221; of a particular approach. It is also a book where people that have already made their choice will be able to consider the &#8220;other&#8221; software development process with a different view and also gain a better insight on their own strengths and weaknesses. Reference: &#8220;Balancing <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/balancing-agility-and-discipline/" title="Balancing Agility and Discipline">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Book Review: Continuous Integration: Improving Software Quality and Reducing Risk</title>
		<link>https://www.scrumexpert.com/knowledge/book-review-continuous-integration-improving-software-quality-and-reducing-risk/</link>
					<comments>https://www.scrumexpert.com/knowledge/book-review-continuous-integration-improving-software-quality-and-reducing-risk/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 09 Apr 2025 16:19:54 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[continuous delivery]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8293</guid>

					<description><![CDATA[As a software developer, you know that one of the critical period in a project is when you try to make integrate your code in the overall application and push it towards the final user. It is sometimes a long process that you would like to accelerate so that you could obtain a quicker feedback on the quality of your code. &#8220;Book Review: Continuous Integration: Improving Software Quality and Reducing Risk&#8221; is a book written by Paul Duvall, with Steve Matyas and Andrew Glover to help you improve the way you build and deliver software. After a initial presentation of the continuous integration (CI) concepts and objectives, the content of the book goes far beyond the simple “continuous build” aspect to cover all disciplines concerned by CI: risk management, configuration management, database evolution, software testing, inspections, deployment. It is clear that CI is just not installing a suite of tools, but is mainly changing software development practices and process. Each chapter is well-structured with practical examples related to real life situations. The book reach also nicely the objective of maintaining a balance between a somewhat tools- and language-neutral position, but still giving enough practical advice so that you could quickly adapt the advice to your own software development environment. Final appendixes give valuable information on CI resources and evaluating available CI tools. Reference: Continuous Integration: Improving Software Quality and Reducing Risk; Paul M. Duvall, Steve Matyas, Andrew Glover; Addison-Wesley Professional]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/book-review-continuous-integration-improving-software-quality-and-reducing-risk/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Book Review: Introduction to Agile Methods</title>
		<link>https://www.scrumexpert.com/knowledge/introduction-to-agile-methods/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 26 Jun 2024 16:44:30 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7923</guid>

					<description><![CDATA[The book Introduction to Agile Methods by Sondra Ashmore and Kristin Runyan has the goal to provide an introduction to the wide landscape of Agile software development approaches. A very ambitious goal in my mind. From the start, you quickly see that the content has a strong &#8220;textbook&#8221; flavor and this review might have a certain bias as I have left university several decades ago and have already more than 10 years of familiarity with Agile software development. The book is well-structured and provides a lot of valuable material about a wide range of Agile approaches, dealing even with methods that have a more limited following like Feature Driven Development or Crystal. The book is well written, even if I found it sometimes a little &#8220;dry&#8221; as it lacked the more &#8220;from the trenches&#8221; reports provided my other Agile authors that work as consultants. There is however in each chapter an interview with a recognized Agile expert who shares a personal perspective on the topic that has just been discussed. The further reading sections are also well done. It is however difficult to make all the different Agile approaches coexist in the same structure as the authors decided to structure their book around software development phases. I had sometimes the feeling of jumping from one method to the other without many explanations or that the content about each method was too much scattered around the book. I also had the impression that the book was lacking nuances when comparing the <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/introduction-to-agile-methods/" title="Book Review: Introduction to Agile Methods">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Book Review: Agile Analytics</title>
		<link>https://www.scrumexpert.com/knowledge/agile-analytics/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 03 Jun 2024 14:45:48 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7893</guid>

					<description><![CDATA[The Agile Analytics book aims to provide an adaptation of the Agile development approach to the specific characteristics of Datawarehouse (DW) and Business Intelligence (BI) systems development. The book is divided into two parts. The first part focuses on Agile project management techniques and delivery team coordination. The book includes chapters on Agile project management, customers and collaboration, user stories for BI systems and self-organizing teams. The second part of the book focuses on the technical methods that are necessary to enable continuous delivery of value at production-quality levels. This part contains material on evolutionary design, TDD Warehouse development, version control or project automation. The book is well written and well-structured. The concepts are illustrated with many anecdotes and examples. An important list of references and further reading material is available at the end of the book. My favorite part is the chapter 6 that deals with evolving design, a key factor for successful agile projects. I will naturally recommend this book to every developer or manager involved DW and BI projects, but this book has also a much broader appeal. The issues specific DW or BI are not far for every large project, where databases play a major role, as it might be for instance in a mainframe environment. There you usually have to balance the architecture, performance and stability needs expressed on the database and operation sides of your organization with the goal of delivering frequently new working software. With his process of adapting Agile to data analytics, <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/agile-analytics/" title="Book Review: Agile Analytics">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Book Review: Leading Lean Software Development</title>
		<link>https://www.scrumexpert.com/knowledge/leading-lean-software-development/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 12 Feb 2024 21:17:54 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[kanban]]></category>
		<category><![CDATA[lean]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7773</guid>

					<description><![CDATA[What fascinates me the most in the Lean software development approach is the quality of the people that support it. Mary and Tom Poppendieck are not an exception to this rule. Their book &#8220;Leading Lean Software Development&#8221; achieves the seemingly contradictory goals of being very insightful but still easy and captivating to read. It might be however easier to have the right flow when you are a Lean adept ;o) The book starts with a chapter on systems thinking that takes also examples outside the software development world, like Southwest Airlines. The next chapter on technical excellence is dedicated to a panorama of the software development approaches. Chapter three is kind of my favorite part of the book, extracting process management knowledge from the history of the construction of the Empire State Building, a project that took only one year to be completed. Chapter four presents the tools for improvement. Finally, the last part of the book is dedicated to the people and the leadership aspects of Lean. The structure of the book &#8220;Leading Lean Software Development&#8221; makes it very pleasant to read, mixing the presentation of lean concepts with case studies and short personal stories. It is definitively a book that I will recommend to every person involved in software development&#8230; and wish that every software developer, project manager and development or IT manager had read. Even if you think that Lean is not for you, or you are a Toyota owner, this book provides a mind-opening text about <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/leading-lean-software-development/" title="Book Review: Leading Lean Software Development">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Book Review: Lean Agile Software Development</title>
		<link>https://www.scrumexpert.com/knowledge/lean-agile-software-development-by-alan-shalloway-guy-beaver-and-james-r-trott/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 06 Dec 2023 15:00:19 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[lean]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=84</guid>

					<description><![CDATA[The goal of the book “Lean-Agile Software Development &#8211; Achieving Enterprise Agility” by Alan Shalloway, Guy Beaver and James R. Trott, is to propose a vision of Agile software development that goes behind the current practices, more specifically Scrum, to integrate the principles of Lean development. To achieve this objective, the authors draw on their own experience in Agile software development consulting. The book starts with a presentation of Agile and Lean principles. The second part explains how Lean adoption can improve the usage of Scrum with an interesting table comparing Scrum and Lean accompanied by a list of practices to avoid. It devotes specific chapters to topics like release planning, visual control, quality assurance, product coordination and architecture. A final part is dedicated to more insight in the Lean approach. The book &#8220;Lean-Agile Software Development&#8221; is pleasant to read. Each chapter has an abstract and the beginning and a summary at the end with some questions and further reading recommendations. Besides the sometimes-annoying references to the authors&#8217; consulting firm, this book provides interesting material on specific aspects of Agile software development projects at an enterprise level. Its main difference with other books on the same topic is for me the treatment of the management aspects of software development, as the authors make their point for a stronger management role and intervention in Agile projects. This book will therefore bring more benefits to project and development managers that work for large organizations where the control aspect is important and the <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/lean-agile-software-development-by-alan-shalloway-guy-beaver-and-james-r-trott/" title="Book Review: Lean Agile Software Development">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>The Scrum Field Guide</title>
		<link>https://www.scrumexpert.com/knowledge/the-scrum-field-guide/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 30 Oct 2023 16:26:15 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7688</guid>

					<description><![CDATA[Scrum offers minimal guidelines for Agile project management. In his book &#8220;The Scrum Field Guide&#8221;, Mitch Lacey provides Scrum practitioners with material that should help them improve their Scrum practices. The book is divided in four parts. The first part gives you advice on getting started with Scrum. The second part will help you overcome some of the initial stumbling blocks met by Agile teams and organizations. The third part of the book deals with some of the larger, deeper issues that companies face, like adding people to projects or fixing dysfunctional daily standup meetings. The final part of &#8220;The Scrum Field Guide&#8221; presents less discussed topics such as budgeting projects, writing contacts or writing documentation in Scrum projects. You can read this book from start to finish or pick a chapter about a specific issue that you want to solve. Each chapter of The Scrum Field Guide book starts with a story that put the topic in perspective. It is followed by a discussion on the conceptual aspects. At the end of the chapter, a &#8220;Keys to Success&#8221; part that summarizes the important content of the chapter and a reference section provides pointers to additional knowledge. I have particularly appreciated the chapters about the sprint length determination, doing new development and maintenance at the same time or the sprint emergency procedures. The book is easy to read and I will recommend this book to every Agile and Scrum practitioner and every non-Agile practitioner too ;O) Reference: &#8220;The Scrum Field <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/the-scrum-field-guide/" title="The Scrum Field Guide">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Management 3.0</title>
		<link>https://www.scrumexpert.com/knowledge/management-3-0/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 02 Oct 2023 16:15:02 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[people]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7658</guid>

					<description><![CDATA[In his foreword of the book &#8220;Management 3.0&#8221; by Jurgen Appelo, Robert C. Martin wrote that he hates management books, but &#8220;this book is smart&#8221;. I think that this book might be smart because Jurgen is smart. If I try to summarize what you get from the book &#8220;Management 3.0&#8221; by Jurgen Appelo, you can consider the author as the hidden son resulting from a relationship between a Springer Verlag journal&#8217;s editor and Mike Cohn, with some influence from Aardman Studios in the education. You will therefore jump from sentences like &#8220;It is often seen as the opposite of reductionism, although complexity scientists believe that complexity is the bridge between the two, and both are necessary but insufficient [Corning 2002:69]&#8221; (I hope that you have all recognized the definition of &#8220;holism&#8221;) to a checklist for Agile Goals that contains questions like &#8220;is the goal manageable and measurable so that success can be determined?&#8221; You will therefore go back and forth between high level system or behavioral theories and practical management situations and practices. Despite its high theoretical content, the book is very enjoyable and easy to read and you shouldn&#8217;t be afraid by what could appear initially as a strong theoretical content. Jurgen Appelo is so smart that he even make the own assessment of his book at the end, based on the quote that &#8220;all models are wrong but some are useful&#8221; He says &#8220;It makes no sense discussing which idea is wrong, because they all are. The real <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/management-3-0/" title="Management 3.0">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Disciplined Agile Delivery</title>
		<link>https://www.scrumexpert.com/knowledge/disciplined-agile-delivery/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 11 Sep 2023 14:39:39 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7645</guid>

					<description><![CDATA[It is ironic to start reading a book about a new Agile approach and to find the following quote in it: &#8220;The explosion of “branded” agile methods has resulted in a jargon-filled confusion of siloed tribes made up of uncollaborative zealots. — Mark Kennaley, Author SDLC 3.0&#8221; Disciplined Agile Delivery (DAD) is defined as &#8220;a hybrid approach which extends Scrum with proven strategies from Agile Modeling (AM), Extreme Programming (XP), and Unified Process (UP), amongst other methods. DAD extends the construction-focused lifecycle of Scrum to address the full, end-to-end delivery lifecycle from project initiation all the way to delivering the solution to its end users. The DAD process framework includes advice about the technical practices purposely missing from Scrum as well as the modeling, documentation, and governance strategies missing from both Scrum and XP.&#8221; Disciplined Agile Delivery is strongly influenced by RUP and by Scott Ambler&#8217;s Agile Modeling and Agile Data approaches that are often cited in the additional resource sections. Starting with the realistic diagnostic that many teams are unable to customize up or down existing software development processes for their own context, the authors have tried to provide a hybrid, goal-driven and lightweight (although it needs 500 pages to describe it) process that will provide a &#8220;start from the middle&#8221; way. The question remains open if teams that are unable to customize other approaches could easily absorb and adopt DAD? There might be a partial answer in the book &#8220;Your organization needs to invest in mentoring, training, and <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/disciplined-agile-delivery/" title="Disciplined Agile Delivery">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Coaching Agile Teams</title>
		<link>https://www.scrumexpert.com/knowledge/coaching-agile-teams/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 14 Aug 2023 15:57:31 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7598</guid>

					<description><![CDATA[Transmitting human experience through written material is not easy. As Rachel Davies did in &#8220;Agile Coaching&#8220;, Lyssa Adkins manages to do it brilliantly in this book that covers the same topic. Based on her own experience of &#8220;recovering command-and-control project manager&#8221;, she writes about all the circumstances where you can coach people, explaining both what you should and shouldn&#8217;t do. With a lot of modest comments about the fact that being a good coach is a journey and not a status, the book is structured around the different aspects of coaching (mentoring, facilitating, teaching, &#8230;) It provides both a conceptual view backed by experience reports and some &#8220;tools&#8221; and check-lists that will help coaches. My favorite parts are two lists presenting the preferred skills that agile coaches should have and the failures modes that a coach could encounter. Coaching Agile Teams by Lyssa Adkins is a very well written book that I will warmly recommend to everyone working in software development. Its message is not only about coaching or managing software developers, but rather encompass the whole values of working together in project teams. Reference: &#8220;Coaching Agile Teams &#8211; A Companion for ScrumMasters, Agile Coaches, and Project Managers in Transition&#8221;, Lyssa Adkins, 315 pages, Addison-Wesley Professional Website: https://lyssaadkins.com/ Quotes To figure out how to coach from the center, providing just the right touch, you must first understand a few things about the world you coach in and the people you coach. Believe it or not, you are not the best <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/coaching-agile-teams/" title="Coaching Agile Teams">[...]</a>]]></description>
		
		
		
			</item>
	</channel>
</rss>
