|
Your search returned 1 matching documents
Software Teamwork: Taking Ownership for Success
by
Jim Brosseau
|
Addison-Wesley Professional
1 edition
November 2007
432 pages
|
Reviewed by Jeanne Boyarsky, December 2007
         (9 of 10)
"Software Teamwork: Taking Ownership for Success" isn't just about teams. The book provides tips on the individual, group, team and stakeholder levels. (A group is defined as interacting with others without being a team.)
I particularly liked the inside cover references. Each of four tables (individual/group/team/stakeholder) that cross reference the chapter number and four areas (trouble signs, success indicators, questions to ask and tools for support.) These combine to form 16 icons. The icons are used within the chapters to highlight key concepts or find them later. While this sounds complicated trying to describe it, it's a case where a picture is worth a thousand words and the concept works very well in reading/navigating/referencing the book.
I also particularly liked the "how is this relevant?" section that ends each chapter. After the chapter summary, the author picks key concepts and asks questions to get you thinking about how it applies in your workplace.
I'm always a bit sceptical of books that claim to address everyone involved in the software development process including managers, developers and stakeholders. This book manages the task impressively.
And finally, the book resonates with problems and phrases used in industry. My favorites are the problem with "and then a miracle happens" and the repeated emphasis on what "done" means throughout the book. There are good analogies, stories and examples throughout the book. It was a great read and very informative. I highly recommend this book.
Discuss book in the Saloon —
More info at Amazon.com
|
|
