Here are 78 books that Ship It! fans have personally recommended if you like
Ship It!.
Shepherd is a community of 10,000+ authors and super readers sharing their favorite books with the world.
Shepherd is reader supported. When you buy books, we may earn an affiliate commission.
I would like to consider myself an experienced and successful designer, researcher, and educator. I'm an Associate Professor in Communication Design and the Head of Education for the School of Design at Northumbria University in the United Kingdom, where I've taught and researched for the last twenty years so I'm super passionate about this subject and love explaining how design works. Before joining academia, I worked internationally as a designer and creative director for numerous prestigious design and media organizations, including Philips, Time-Warner, Windmill Lane Pictures, and WPP in the UK, Ireland, USA, and Southeast Asia. Working in these different businesses and locations gave me a broad perspective on the role and importance of design.
This essential book by Don Norman does not need any more plugging, but it would be impossible to leave it out.
The book forms a brilliant introduction to User Experience Design by explaining how the design of everyday objects relies on an intuitive understanding of how they work. Once we translate this thinking from the physical to the digital world, we are halfway there as UX/UI designers.
Even the smartest among us can feel inept as we fail to figure out which light switch or oven burner to turn on, or whether to push, pull, or slide a door. The fault, argues this ingenious,even liberating,book, lies not in ourselves, but in product design that ignores the needs of users and the principles of cognitive psychology. The problems range from ambiguous and hidden controls to arbitrary relationships between controls and functions, coupled with a lack of feedback or other assistance and unreasonable demands on memorization. The Design of Everyday Things shows that good, usable design is possible. The…
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.
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.
I was lucky enough to read an early draft of this book and it’s simply the best analysis of the open-source software ecosystem around today.
The writing style is friendly and not formal despite the academic-level research that went into this book. It made me think differently about the open-source projects I maintain and how I interact and chose those I use.
An inside look at modern open source software development and its influence on our online social world.
Open source software, in which developers publish code that anyone can use, has long served as a bellwether for other online behavior. In the late 1990s, it provided an optimistic model for public collaboration, but in the last 20 years it’s shifted to solo operators who write and publish code that's consumed by millions.
In Working in Public, Nadia Eghbal takes an inside look at modern open source software development, its evolution over the last two decades, and its ramifications for an internet…
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 from an older generation of open source development, pre-GitHub, but much of the advice here is still incredibly relevant and astute today, helping provide advice on the interpersonal as well as technical sides to open source development.
Many of the underlying principles from this book are what form my grounding as an open-source maintainer for the last 15 years.
The corporate market is now embracing free, "open source" software like never before, as evidenced by the recent success of the technologies underlying LAMP (Linux, Apache, MySQL, and PHP). Each is the result of a publicly collaborative process among numerous developers who volunteer their time and energy to create better software. The truth is, however, that the overwhelming majority of free software projects fail. To help you beat the odds, O'Reilly has put together Producing Open Source Software, a guide that recommends tried and true steps to help free software developers work together toward a common goal. Not just for…
Defining and managing the requirements for a software system is hard! I’ve been interested in improving how projects handle their requirements for more than 35 years. I realized how important this was when I saw how many projects—including my own—struggled and failed when they neglected to build a solid foundation of well-understood and clearly communicated requirements. I’ve personally used nearly all of the techniques described in my book Software Requirements, and I got always better results when I applied those techniques. My books, articles, training courses, presentations, and videos on requirements have been helpful to thousands of business analysts worldwide for many years.
Suzanne and James Robertson have been writing insightful books on software requirements for many years. This book covers all the important topics, including understanding the real problem, different techniques for exploring solutions, and numerous ways to communicate requirements effectively. I especially like their treatment of quality attribute requirements and defining “fit criteria” to judge whether a solution adequately addresses them.
The book includes a comprehensive requirements specification template to guide writing a rigorous and complete specification on projects for which that is valuable. I also appreciate their use of visual models both to communicate with the reader and to guide the reader in communicating requirements to project stakeholders. I do prefer my book Software Requirements, but this is an excellent choice as well by two authorities in the field.
"If the purpose is to create one of the best books on requirements yet written, the authors have succeeded."
-Capers Jones
Software can solve almost any problem. The trick is knowing what the problem is. With about half of all software errors originating in the requirements activity, it is clear that a better understanding of the problem is needed.
Getting the requirements right is crucial if we are to build systems that best meet our needs. We know, beyond doubt, that the right requirements produce an end result that is as innovative and beneficial as it can be, and that…
You know what ages like milk? Programming books. I always cringe when someone glances at my programming bookshelf. Some of those books are so dated, they make me appear out of touch by association. Sometimes, I feel compelled to justify myself. “Yes, that's the first edition of Thinking in Java…I keep it for nostalgic reasons, you know!” Yesterday’s software book is today’s fish and chip wrapper. However, there are exceptions. A few classics stay relevant for years, or even decades. This is a shortlist of software books that might be older than you, but are still very much worth reading.
In my consulting gigs, I come across plenty of clueless remarks. Here's a classic one: “We're falling behind schedule, so let's hire more coders.” Or a more recent gem: “We'll be ten times more productive if we generate code with AI.”
When I encounter such nonsense, I don't facepalm or cringe. Instead, I put on my poker face and drop a quote from The Mythical Man-Month.
In an industry where last year’s book is already outdated, Fred Brooks' collection of essays has been a guiding light for nearly half a century. His aphorisms have become legendary. “The bearing of a child takes nine months, no matter how many women are assigned.” “Adding manpower to a late software project makes it later.” “There is no silver bullet.” The list goes on and on.
John Carmack, one of the greatest programmers of our times, used to revisit this book every year or…
Few books on software project management have been as influential and timeless as The Mythical Man-Month. With a blend of software engineering facts and thought-provoking opinions, Fred Brooks offers insight for anyone managing complex projects. These essays draw from his experience as project manager for the IBM System/360 computer family and then for OS/360, its massive software system. Now, 20 years after the initial publication of his book, Brooks has revisited his original ideas and added new thoughts and advice, both for readers already familiar with his work and for readers discovering it for the first time.
Frans Johansson is the Co-Founder and CEO at The Medici Group, an enterprise solutions firm that helps organizations build and sustain high-performing teams through our revolutionary team coaching platform: Renaissance. Our firm's ethos--diversity and inclusion drive innovation--is informed by our work with over 4,000 teams in virtually every sector and by his two books The Medici Effect and The Click Moment.
This is the most complete take on how to bring diversity, inclusion, and belonging into your team. This is a very practical guide that shows you how to implement this process step by step. Not only does she explain how to respond to the negative tropes, but she also lays out detailed approaches to make sure your allies and angels do maximum good. A must-read if you want to avoid the common mistakes that bog down this process.
In this groundbreaking guide, a management expert outlines the transformative leadership skill of tomorrow-one that can make it possible to build truly diverse and inclusive teams which value employees' need to belong while being themselves.
Humans have two basic desires: to stand out and to fit in. Companies respond by creating groups that tend to the extreme-where everyone fits in and no one stands out, or where everyone stands out and no one fits in. How do we find that happy medium where workers can demonstrate their individuality while also feeling they belong?
Business development and projects have fascinated me since my studies and my first experiences in companies. Time and again, I think I have understood what it's really all about... and shortly thereafter, completely new insights emerge that challenge previously perceived assumptions and thus enable leaps in performance. This is sometimes exhausting, but I wouldn't want to miss this path of development! Today I help management teams to improve their business results quickly and sustainably by guiding them to question assumptions, find new perspectives and thereby enable performance leaps.
When I read this book, it was like an epiphany. Suddenly, I understood what—beyond all the doctrines and pub talk—actually slows down projects and thus impairs the economic performance of companies. It is our own management mechanisms and beliefs about how we think we can get a grip on projects. Shortly after reading this novel, we were able to perform nothing short of miracles in a technology company I was working for at the time: Halving project times, doubling productivity. You have to have witnessed that to really believe it... Read this book!
This fast-paced business novel does for project management what The Goal and It's Not Luck have done for production and marketing. Goldratt's novels have traditionally slain sacred cows and delivered new ways of looking at processes which seem like common sense once you read them. Critical Chain is no exception. In perhaps Eli's most readable book yet, two of the established principles of project management, the engineering estimate and project milestones, are found wanting and dismissed, and other established principles are up for scrutiny - as Goldratt once more applies his Theory of Constraints. The approach is radical, yet clear,…
I’ve been doing large-scale software development at great US businesses from the introduction of the PC to the cloud explosion. From my earliest successes (online banking at US Bank in 1985!) to my biggest failures (Wells Fargo “Core” disaster in 2006), I’ve always sought better ways of doing things. These five books all were important to my learning and remain highly relevant, and I hope you find them useful as well.
When this book was released, I was immersed in a huge failing project at Wells Fargo, struggling to make sense of it all. This book helped me put the failure in perspective and showed a better way that I embraced for the rest of my career.
The key insight is that large-scale innovation is not like manufacturing – it is less about planning and control, more about people, rapid learning, and adaptation. Here we learn concepts such as the Chief Engineer, lightweight milestone—and responsibility-based project management, and focusing on engineering skills and vendor partnerships. Shelve the elaborate process frameworks consultants are selling you, focus on the basics Toyota emphasized throughout their glory years.
The ability to bring new and innovative products to market rapidly is the prime critical competence for any successful consumer-driven company. All industries, especially automotive, are slashing product development lead times in the current hyper-competitive marketplace. This book is the first to thoroughly examine and analyze the truly effective product development methodology that has made Toyota the most forward-thinking company in the automotive industry.
Winner of the 2007 Shingo Prize For Excellence In Manufacturing Research!
In The Toyota Product Development System: Integrating People, Process, and Technology, James Morgan and Jeffrey Liker compare and contrast the world-class product development process of…
I’ve been creating content since I was a day camp counselor (launching a newsletter for the staff!). Since then, I’ve done everything from interview Motley Crue, Metallica and Nirvana to Tom Peters, Susan Cain and beyond. I started my blog, Six Pixels of Separation, back in 2003 and my podcast (of the same name) is the longest running business podcast in the world. I wrote two books, Six Pixels of Separation and CTRL ALT Delete. With that, I even run a private Facebook group for some of the world’s most known business and non-fiction authors. I’m a word nerd. I collect comics (and graphics) novels and spend too much time reading. I’m also a huge collector of books on writing, how to write, interview with writers, and other content creators. So… what’s going to get your ideas into actionable content? I think these books might help ☺
This is not an easy book to find. It’s a small and short hardcover book where famed management legend, Tom Peters, lays out the how to turn your personal brand (and your work) into a project… but not just any project. Tom believes that every aspect of your work should be a Wow! Project. The book is 50 easy-to-grasp sections that have, without a doubt, changed my approach to everything from writing an article to starting a business. This book is a hidden gem… I’m quasi-mad that I’m sharing it publicly, it’s been a great secret advantage. ;)
The common denominator/bottom line for both the professional service firm/PSF and the individual/Brand You is: the project. And for the cool individual in the cool professional service firm there is only one answer: the cool project. A seminar participant said: "Reward excellent failures. Punish mediocre successes." So, how many of you are at work -- right now -- on "mediocre successes"? At work on projects that won't be recalled, let alone recalled with fondness and glee, a year from now?
We don't study professional service firms. (Mistake.) And we don't study WOW Projects. (Worse mistake.) There is, of course, a…
