17 Books Like Practical People Engagement

This book has really cute graphics–what’s not to love about ninjas made out of office supplies? I loved the illustrations but I also feel confident recommending it because it’s not like the other time management or productivity books that I have read.

I’m wary of many time management books because I feel they don’t speak to the reality of being a working parent and having to juggle All The Things, and I could really relate to this book. It felt like the suggestions were reasonable and pragmatic, and I learned something. It helped me change the way I approach my workload, so I’m grateful for that. 

I loved this book because it’s so practical and grounded in reality–so many project management books tell you how to work in an ideal world, but the real world is messy. When people get involved in processes and decision-making, suddenly the textbook formulae for how to get work done no longer apply. 

I liked Brett’s writing style and found the book very relatable. Plus, it’s full-color and really nicely put together–and I love a book that is beautiful to read and pragmatic in its advice!

I work remotely most of the time, and leading virtual project teams (or any teams) is a real challenge. I used to be able to catch people in the office, but the world of work has changed now, and I have to rely on different strategies.

This book is packed with strategies and I enjoyed learning new ways of being able to connect with my teams even though we are no longer in the same office most of the time. The book taught me about having the right mindset for virtual leadership and I loved all the different case studies and stories that helped illustrate good (and not-so-good) ways of working. 

I loved this book because it was one of the most exciting things I’ve read in the project management space for some time. It’s not enough for me to complete a task or project–it has to be fit for purpose and completed in the right way, with the right input from others. And how to actually do that is what I learned from this book. 

It’s a method for making sure what my team creates during a project is actually used and is useful, which means I can show the value we add and how we are making a difference through projects. I thought the practical exercises and tools were fantastic, and the author leaves nothing unexplained–it’s such a thorough guide to managing change adoption. 

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 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… show more.

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.

Another book that predates GitHub but provides a lot of actionable advice today that’s been mostly ignored across much of our industry.

Hard problems like “why isn’t my software project reliable?” are tackled head-on and addressed here. It was an early nudge for me to automate as much as possible in software projects and not ignore difficult problems with project organisation in favour of “fun” technical tasks.

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.

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!