We have a list of recommended books, here.
In addition, we can recommend the following:
A Sense of Urgency by John Kotter.
Fearless Change: Patterns for Introducing New Ideas by Mary Lynn Manns and Linda Rising.
Toyota Production System: Beyond Large-Scale Production by Taiichi Ohno.
Taiichi Ohno's Workplace Management
The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)by Frederick Brooks. One of his famous quotes: "How does a project get one year late? One day at a time."
Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin Series)by Mugridge and Cunningham.
Continuous Integration: Improving Software Quality and Reducing Risk (Addison-Wesley Signature Series)by Duvall, Matyas, and Glover.
Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen.
Test Driven Development: By Example (Addison-Wesley Signature Series)by Kent Beck.
Working Effectively with Legacy Code (Robert C. Martin Series)by Michael Feathers.
The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovation by Nonaka and Takeuchi.
Good to Great: Why Some Companies Make the Leap... and Others Don'tby Jim Collins.
Software by Numbers: Low-Risk, High-Return Developmentby Mark Denne and Jane Cleland-Huang.
The Five Dysfunctions of a Team: A Leadership Fable by Patrick Lencioni.
Comment: I have given links to Amazon, which has some benefits. There is certainly no obligation to buy from Amazon.
Suggestion: Some of these books are technical (in one area or another) and some are more about people. Mix and match. Consider what you need to learn. Consider what you are most ready to learn. And don't think too much in the sky. Quickly see how much you have really learned by putting your ideas into action.