Software Teamwork: Taking Ownership for Success in Software Development
Software Teamwork is a compelling, innovative, intensely practical guide to improving the human dynamics that are crucial to building great software.
Unlike most books about managing software projects, Software Teamwork’s lessons are grounded firmly in data and experience. Drawing on years of work with a wide range of teams, Jim Brosseau shows how to drive powerful improvements through small, focused changes that deliver results. These changes are designed to work for the wholeteam and respect existing organizational culture. Better yet, Brosseau identifies solutions you can start implementing right now, as an individual, without waiting endlessly for executive buy-in.
Whatever your methodology, technology, or organization, Software Teamwork demonstrates how to apply solutions to realistic enterprise development challenges involving complex sets of stakeholders. Along the way, the author shares important new insights into the attitudes, motives, and personal relationships that project management software just can't track.
Review By: Herb Ford Jr.
09/11/2009
This book should be required reading for anyone interested in management or currently in a management position. It is designed for management and non-management staff working in software development. I think everyone should read this book. The author chose to speak to the psychology of a team and breaks down the flaws of a team, not from a technical perspective, but from a human perspective. The author describes problems readers can relate to and recommends solutions from a non-technical perspective. The author also provides immediate insight to current situations you might be going through with your team, as well as questions you might ask in order to find the root cause of any dysfunction on your team. The book is broken down into the categories of a software team, from the individuals to the stakeholders. Throughout the book you will find icons that represent different types of information, e.g., trouble signs, success indicators, questions to ask, and tools for support.
The author's message is easy to understand. The evidence was so crystal clear and relevant that you might believe the author used your office or team as a case study in some examples. The language of the book and layout makes this book suited for anyone and everyone. I would also go as far to say that this book could and should be taught in a college as a curriculum course for those going through information systems, computer science, PMI degrees, etc.
Joining a software team to develop a quality product is not as simple as it sounds. This book lends valuable insight on some of the traps and situations that prevent software teams from reaching their full potential. One of the most interesting aspects of this book is the way the author breaks down a software team, reorganizes it, and then rebuilds it. I recommend this book to everyone. More so, this book should be included in the reference sets you see on development and QA's desks.