Sprint 1 Teamwork Bookclub
- Good to Great — Jim Collins
Based on research into companies that made a sustained leap from average to excellent performance. Key ideas include Level 5 Leadership (humble but fiercely determined leaders), getting the right people on the bus before deciding direction, the Hedgehog Concept (the intersection of what you're passionate about, what you can be best at, and what drives your economics), and the Flywheel effect — that greatness comes from consistent sustained effort rather than a single breakthrough moment. - The Five Dysfunctions of a Team — Patrick Lencioni
Written as a business fable, which makes it very readable. Argues that teams fail because of five cascading problems: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results. Each dysfunction feeds the next, so trust is the foundation everything else rests on. Practically very applicable to software teams. What does trust mean to you? What is possible in a high trust environment versus a low trust environment? - The Advantage — Patrick Lencioni
Less a fable, more a direct leadership manual. Argues that organizational health — clarity, communication, and cohesion among leadership — is more important than strategy or innovation and is the most underutilized competitive advantage. Covers how to build a cohesive leadership team, create clarity around mission and values, and reinforce that clarity through communication and systems. How to build trust: share personal background and values, admist mistakes and weaknesses, keep your word, assume positive intent, communicate often and exessively! - The Mythical Man Month — Frederick P. Brooks Jr.
The most directly software-relevant book on your list and a classic. Brooks' central argument is that adding people to a late software project makes it later — because communication overhead grows faster than productivity. Also introduces the concept of conceptual integrity in software design, the idea that great systems need a single unifying vision rather than design by committee. Many of its observations from 1975 remain painfully relevant today. - Crucial Conversations — Joseph Grenny
A practical guide to handling high-stakes conversations where opinions differ and emotions run strong. The core insight is that most organizational and relationship problems can be traced back to conversations people are unwilling or unable to have effectively. Covers how to create psychological safety, stay focused on shared goals, and separate facts from stories we tell ourselves. Very applicable to code reviews, team conflict, and client communication. Remember: opinions vary, stakes are high, and emotions run strong. Stay respectful, focus on facts, listen more than you speak, make it safe. Respectful debate is ok!
