The future of talent management is now. I’m a teacher, consultant, and board member who is deeply interested in the social and economic impact of the freelance revolution. Millions of people around the world are now working for themselves as independent professionals or “solopreneurs”. Millions more are taking on freelance assignments to augment their income or increase their expertise and experience. Technology makes it possible for professionals in many fields to work remotely and free themselves from the limitations of their local economy. These benefits organizations by offering greater access to talent and gives professionals greater access to opportunity.
In a recent survey of HR leaders, 80% mentioned that they were continuing to organize their HR department based on the “Ulrich” model. Is there a more impressive recommendation for the impact of this book, and Dave’s research and writing? In HR Champions, Ulrich points out the importance of three types of HR work: business partners, specialists, and shared services. In a recent HR Management article, that model was expanded to include a fourth category: project management. Technology is obviously a much bigger factor in HR work since 1996 when the book was first published. But, this oldie but goodie has aged extraordinarily well and continues to be relevant and insightful. If you are in HR or interested in talent management at scale, this book has to be on your list.
The author argues that the roles of human resource professionals must be redefined to meet the competitive challenges organizations face today and into the future. He provides a framework that identifies four distinct roles of human resource professionals: strategic player, administrative expert, employee champion, and change agent. He includes many examples to demonstrate that human resource professionals must operate in all four areas simultaneously in order to contribute fully. He urges a shift of these professionals' mentality from "what I do" to "what I deliver" and makes specific recommendations for how individuals in human resources can partner with line managers…
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 have worked for some really toxic leaders in my lifetime. Over the decades, I’ve figured out that even well-intentioned people can be toxic leaders without knowing it. As a team and leadership performance coach for the past 15 years, my job has been to help leaders show up as people others want to follow; to help employees feel cared for, and as a result, be intrinsically motivated to care about their company’s mission. These books represent the figurative fuel in my tank for this work, and I hope you find them useful.
One of the core concepts of how we live our lives–including how we lead–is our mindset. This book, better than any other I’ve read, captures what a mindset actually is: values, beliefs, and principles, and how the three combine to make us feel right about our behaviors–even when we’re wrong.
We all have mindsets for driving, parenting, leading, being a partner, and many other areas of life. I find that in my work, the more that I can help someone examine their values, beliefs, and principles, the more success they will have in changing their behaviors. While the book is about more than mindsets, I continually use Broza’s explanation of the concept in my work.
Does your Agile team experience the following common problems?
Members use established Agile practices and tools, but with little motivation or buy-in.
Even though the team is cross-functional, members don’t collaborate effectively or leverage everyone’s abilities.
Rather than act empowered, they wait for permission and approval.
Improvement has stalled — the team performs okay, but it can do so much better.You can’t solve these problems with more practices, rules, and tools. These are people problems.
If you’re a manager, Scrum Master, project manager, or delivery lead — or you aspire to be — you can make all the difference to…
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?
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.
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.
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.
"Ship It!" is a collection of tips that show the tools and techniques a successful project team has to use, and how to use them well. You'll get quick, easy-to-follow advice on modern practices: which to use, and when they should be applied. This book avoids current fashion trends and marketing hype; instead, readers find page after page of solid advice, all tried and tested in the real world. Aimed at beginning to intermediate programmers, "Ship It!" will show you: which tools help, and which don't, how to keep a project moving, approaches to scheduling that work, how to build…
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…
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,…
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…
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.
I have been waiting for this book, published in 2023, since Eli Goldratt published Critical Chain. It describes very clearly in the form of a novel not only how an extraordinarily effective multi-project organization works, but also how a traditionally managed organization can transform itself very quickly and sustainably into a highly productive enterprise. In each chapter, I recognized myself in the challenges that I face again and again. Thank you, Efrat, for this profound yet easy-to-read book!
Marc Wilson is not giving up. He is determined to turn around the struggling family company and keep it, despite his father’s decision to sell. The problem is that they are late on more and more projects and their customers won’t tolerate it anymore. Marc is looking everywhere for a solution, when in one of his MBA classes he comes across a unique approach that views operations in terms of flow.
The concept of flow is straightforward. It’s easy to visualize the stream of projects going through the system and understand that if something clogs the flow, the projects pile…
