Here are 100 books that Extreme Programming Explained fans have personally recommended if you like
Extreme Programming Explained.
Book DNA is a community of 12,000+ authors and super readers sharing their favorite books with the world.
I have always been fascinated by the magic that happens at the intersection of bits and atoms. Circuits, sensors, and algorithms, for better or worse, have permeated every part of our lives. Itâs impossible to understand our environment now without understanding the subtle influence of the code that manages and monitors it.
With this textbook disguised as a novel, Goldratt tells a story that sneaks up on you, revealing how simple digital thinkingâlike tracking bottlenecks and using systems analysisâcan revolutionize physical processes. Itâs not just about manufacturing; itâs about seeing challenges as opportunities to improve again and again.
This is a story about inspiration and being ready to look at the world differently to make every processâfrom your own projects to global operationsârun a little smoother.
*A Graphic Novel version of this title is now available: "The Goal: A Business Graphic Novel"
30th Anniversary Edition. Written in a fast-paced thriller style, The Goal, a gripping novel, is transforming management thinking throughout the world. It is a book to recommend to your friends in industry - even to your bosses - but not to your competitors. Alex Rogo is a harried plant manager working ever more desperately to try improve performance. His factory is rapidly heading for disaster. So is his marriage. He has ninety days to save his plant - or it will be closed byâŚ
It is April 1st, 2038. Day 60 of China's blockade of the rebel island of Taiwan.
The US government has agreed to provide Taiwan with a weapons system so advanced that it can disrupt the balance of power in the region. But what pilot would be crazy enough to runâŚ
I am an organizational psychologist interested in how leadership decision-making influences organizational culture. Iâve studied this for the last 5 years and developed models that pinpoint specific decisions that led to specific cultural attributes and related performance outcomes. I led a team that worked with the top 100 leaders at NASA after the Columbia Space Shuttle disaster.Â
Deming showed me how to think about organizational performance improvement. I was moving from a clinical psychologist in private practice to an organizational psychologist helping companies develop change strategies. I had studied and loved statistical variation in the context of scientific research, but not in the context of addressing real-world challenges.Â
But Deming does something very surprising. He starts by understanding variation and then moves on to understanding organizational culture. Not the theoretical frameworks we all know, but the work world from the view of the front-line employee. Demingâs insight is that the central challenge of culture change is understanding the view of people closest to the work, the ones who perform operations.
They are not motivated by slogans and lofty ideas but by producing great products and services. Taking pride in the work they are doing is central to performance; lost by management fads and enhanced by doing itâŚ
Essential reading for managers and leaders, this is the classic work on management, problem solving, quality control, and moreâbased on the famous theory, 14 Points for Management
In his classic Out of the Crisis, W. Edwards Deming describes the foundations for a completely new and transformational way to lead and manage people, processes, and resources. Translated into twelve languages and continuously in print since its original publication, it has proved highly influential. Research shows that Demingâs approach has high levels of success and sustainability. Readers today will find Demingâs insights relevant, significant, and effective in business thinking and practice. ThisâŚ
I'm a programmer and technical author at Octopus Deploy and I'm deeply interested in DevOps. Since the 1950s, people have been studying software delivery in search of better ways of working. Weâve seen many revolutions since Lincoln Labs first introduced us to phased delivery, with lightweight methods transforming how we wrote software at the turn of the century. My interest in DevOps goes beyond my enthusiasm for methods in general, because we now have a great body of research that adds to our empirical observations on the ways we work.
Well, Doug McGregor was one of the earliest proponents of healthy workplace culture. The Human Side of Enterprise was written during the 1950s and contains the kind of advice you might associate with Dan Pinkâs more recent book, Drive.
If you want to read a book from the pivot point between command and control management and modern theories of motivation, this is the place to start.
"What are your assumptions (implicit as well as explicit) about the most effective way to manage people?"
So began Douglas McGregor in this 1960 management classic. It was a seemingly simple question he asked, yet it led to a fundamental revolution in management. Today, with the rise of the global economy, the information revolution, and the growth of knowledge-driven work, McGregor's simple but provocative question continues to resonate-perhaps more powerfully than ever before.
Heralded as one of the most important pieces of management literature ever written, a touchstone for scholars and a handbook for practitioners, The Human Side of EnterpriseâŚ
The Year Mrs. Cooper Got Out More
by
Meredith Marple,
The coastal tourist town of Great Wharf, Maine, boasts a crime rate so low you might suspect someoneâs lying.
Nevertheless, jobless empty nester Mallory Cooper has become increasingly reclusive and fearful. Careful to keep the red wine handy and loath to leave the house, Mallory misses her happier selfâand soâŚ
Iâve been a professional software engineer and maintaining open-source software for 16 years. My work on open source has been heavily informed by industry best practises and my work on proprietary software has been heavily informed by open source best practises. Without these books, Iâd be a worse engineer on many dimensions. Some of them may feel antiquated but all are still full of relevant wisdom for every open-source (and proprietary) software engineer today.
This is the oldest book on my list and is the most underrated. It describes, with serious rigour and detail, how to run more effective software projects and teams.
Most of this advice has been ignored by most of the industry for most of the time but itâs a big part of the reason Iâve worked from home for 14 years and am as productive as I am today.
Demarco and Lister demonstrate that the major issues of software development are human, not technical. Their answers aren't easy--just incredibly successful. New second edition features eight all-new chapters. Softcover. Previous edition: c1987. DLC: Management.
Markus Gärtner works as Organizational Design Consultant, Certified Scrum Trainer, and Agile Coach for it-agile GmbH, Hamburg, Germany. Markus, author of ATDD by Example - A Practical Guide to Acceptance Test-Driven Development, a student of the work of Jerry Weinberg, received the Most Influential Agile Testing Professional Person Award in 2013 and contributes to the Softwerkskammer, the German Software Craft movement. Markus regularly presents at Agile and testing conferences all over the globe, as well as dedicating himself to writing about agile software development, software craft, and software testing, foremost in an Agile context.
âGood agile testing is good context-driven testing applied in an agile context.â
I recall reading through the authorsâ lessons on software testing at about the same time I dived into more agile topics. Lessons Learned in Software Testing helped me keep the connection towards more traditional contexts â more so since I was still working in a more traditional context.
With their more than 100 lessons some of them applied to me, others did not. I am sure, other readers will find the same in their context.
Most companies developing software employ something they call "Agile." But there's widespread misunderstanding of what Agile is and how to use it. If you want to improve your software development team's agility, this comprehensive guidebook's clear, concrete, and detailed guidance explains what to do and why, and when to make trade-offs.
In this thorough update of the classic Agile how-to guide, James Shore provides no-nonsense advice on Agile adoption, planning, development, delivery, and management taken from over two decades of Agile experience. He brings the latest ideas from Extreme Programming, Scrum, Lean, DevOps, and more into a cohesive whole. LearnâŚ
Iâve always enjoyed mentoring folks whether new or experienced in programming. Whether it is teaching an intern or a high school robotics student, or onboarding an experienced Java developer, it brings me joy to see people learn. I also love to read. Being able to recommend some of my favorite books can help even more people absorb all of this information.
In addition to Java, you need to know about the Java ecosystem.
Each chapter covers a type of tool like version control, securing binaries, or mobile. Some chapters cover a variety of tools. I particularly liked the overview of Quarkus and Micronaut. I also liked the emphasis of tools vs a role. The analogies were great such as comparing identify/fix/deploy to an oil spill.
The book is 300 pages and easy to carry around. Despite having four authors, the book is very cohesive and reads well.
With the rise of DevOps, low-cost cloud computing, and container technologies, the way Java developers approach development today has changed dramatically. This practical guide helps you take advantage of microservices, serverless, and cloud native technologies using the latest DevOps techniques to simplify your build process and create hyperproductive teams.
Stephen Chin, Melissa McKay, Ixchel Ruiz, and Baruch Sadogursky from JFrog help you evaluate an array of options. The list includes source control with Git, build declaration with Maven and Gradle, CI/CD with CircleCI, package management with Artifactory, containerization with Docker and Kubernetes, and much more. Whether you're building applications withâŚ
Donât mess with the hotheadâor he might just mess with you. Slater IbĂĄĂąez is only interested in two kinds of guys: the ones he wants to punch, and the ones he sleeps with. Things get interesting when they start to overlap. A freelance investigator, Slater trolls the dark side ofâŚ
I have worked in IT for over 25 years, creating and securing software. I am completely obsessed with ensuring that our software is more reliable, that its integrity can be trusted, and that it keeps our secrets safe. I am not only a computer scientist but an ethical hacker who works hard to create a dialogue between software developers and all of the people who work in our security industry. I am a teacher, a community leader, and a computer nerd who shares messages and lessons wherever she goes.
The Unicorn Project book picks up where The Phoenix Project book ended.
There is a new character introduced named Maxine, and I want to be Maxine when I grow up! Her character is brave, fun, and endlessly patient as she transforms the way they build software to more effective and productive methods.
She has a family, and life outside her org, which is something I feel all of us can relate to, balancing life and work. She really saves the day, over and over again, as the book proceeds to change, update, and improve every single thing they do within parts unlimited, the fictitious company in this story.
The Phoenix Project wowed over a half-million readers. Now comes the Wall Street Journal Bestselling The Unicorn Project!
"The Unicorn Project is amazing, and I loved it 100 times more than The Phoenix Project..."-FERNANDO CORNAGO, Senior Director Platform Engineering, Adidas
"Gene Kim does a masterful job of showing how ... the efforts of many create lasting business advantages for all."-DR. STEVEN SPEAR, author of The High-Velocity Edge, Sr. Lecturer at MIT, and principal of HVE LLC.
"The Unicorn Project is so clever, so good, so crazy enlightening!"--CORNELIA DAVIS, Vice President Of Technology at Pivotal Software, Inc., Author of Cloud NativeâŚ
Iâve spent more than a decade working on infrastructure, from my early days at LinkedIn, where we had to do a massive DevOps transformation to save the company, to co-founding Gruntwork, where I had the opportunity to work with hundreds of companies on their software delivery practices. From all of this, I can say the following with certainty: the DevOps best practices that a handful of the top tech companies have figured out are not filtering down to the rest of the industry. This is making the entire software industry slower, less effective, and less secureâand I see it as my mission to fix that.
This is one of those books that changed how I thought about and approached software development. First, the book addressed the pain points that I had run into so often: the problems with infrequent, manual deployments, the outages caused by changing configuration rather than source code, the nightmare of merge conflicts that you get from long-lived feature branches, and so on.
Then, it showed how to flip the typical software development process on its head through CI / CD, changing the default from âour software is broken, and we need an integration and release process to get it workingâ to âour software is always working, and we can release it at any time.â Once I read it, I could never go back to the old way.
Getting software released to users is often a painful, risky, and time-consuming process.This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours-sometimes even minutes-no matter what the size of a project or the complexity of its code base.
Jez Humble and David Farley begin by presenting the foundations of a rapid,âŚ
Iâm a professional software developer for more than 22 years now. Iâve used many programming languages, platforms, frameworks, etc. throughout my career. However, the only constant for me personally was the practice of Test-Driven Development. Iâve never stopped learning about the principles and practices behind it, and it paid huge dividends throughout my career. Iâm very humbled and grateful to be able to learn from all those amazing people over the years, that I decided to write a book on the topic. Giving back some of the knowledge that I gathered about TDD throughout 18+ years.
This is the most recent book I'm recommending, and itâs also more than just a book on Test-Driven Development. I often proclaim that Test-Driven Development and software design are two sides of the same coin. One cannot separate one from the other. So learning about Test-Driven Development also means that one has to learn about software design principles. This book teaches both. The first part of the book is all about Test-Driven Development, while the remainder of the book also touches on object calisthenics, refactoring, code smells, design patterns, the S.O.L.I.D. principles, connascence, the four elements of simple design, and much more. Whether youâre new to programming software, or whether youâre a seasoned developer, thereâs much to learn from this book.   Â
Delve deep into the various technical practices, principles, and values of Agile.
Key Features
Discover the essence of Agile software development and the key principles of software design
Explore the fundamental practices of Agile working, including test-driven development (TDD), refactoring, pair programming, and continuous integration
Learn and apply the four elements of simple designBook Description
The number of popular technical practices has grown exponentially in the last few years. Learning the common fundamental software development practices can help you become a better programmer. This book uses the term Agile as a wide umbrella and covers Agile principles and practices, asâŚ
Markus Gärtner works as Organizational Design Consultant, Certified Scrum Trainer, and Agile Coach for it-agile GmbH, Hamburg, Germany. Markus, author of ATDD by Example - A Practical Guide to Acceptance Test-Driven Development, a student of the work of Jerry Weinberg, received the Most Influential Agile Testing Professional Person Award in 2013 and contributes to the Softwerkskammer, the German Software Craft movement. Markus regularly presents at Agile and testing conferences all over the globe, as well as dedicating himself to writing about agile software development, software craft, and software testing, foremost in an Agile context.
The second book from Gregory and Crispin brought me up-to-date on the different trends in the Agile world, ten years after having delved into their first book.
How do you share the quality mindset in a DevOps culture? What about Design Thinking? With many more examples from the industry, the two authors made me curious about some of the things that I had ignored until I read their book.
Janet Gregory and Lisa Crispin pioneered the agile testing discipline with their previous work, Agile Testing. Now, in More Agile Testing, they reflect on all they've learned since. They address crucial emerging issues, share evolved agile practices, and cover key issues agile testers have asked to learn more about.
Packed with new examples from real teams, this insightful guide offers detailed information about adapting agile testing for your environment; learning from experience and continually improving your test processes; scaling agile testing across teams; and overcoming the pitfalls of automated testing. You'll find brand-new coverage of agile testing for the enterprise,âŚ
