File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Book Reviews and the fly likes Leadership, Teamwork, and Trust: Building a Competitive Software Capability Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Books » Book Reviews
Bookmark "Leadership, Teamwork, and Trust: Building a Competitive Software Capability" Watch "Leadership, Teamwork, and Trust: Building a Competitive Software Capability" New topic
Author

Leadership, Teamwork, and Trust: Building a Competitive Software Capability

Book Review Team
Bartender

Joined: Feb 15, 2002
Posts: 926
Title           :Leadership, Teamwork, and Trust: Building a Competitive Software Capability (SEI Series in Software Engineering)
Author/s    : Watts S. Humphrey, James W. Over
Publisher   : Addison-Wesley Professional
Category   : Project Management, Process and Best Practices
Review by : Jeanne Boyarsky
Rating        : 6 horseshoes

"Leadership, Teamwork and Trust" is the original Watts Humphrey's last book. While I knew both the authors were heavily involved in TSP, I wasn't expecting a book on TSP. You'd think something like that would be mentioned on the cover.

The book has two parts. Nine chapters (160 pages) of examples, points and content. And 5 chapters (144 pages) of appendices about TSP. That's almost half the book! The appendices weren't bad; they just caught me by surprise.

Back to the part of the book that wasn't about TSP. I liked the mix of stories and points. Some stories were like mini-case studies. Some parts really drew me in such as in chapter 4 on how we differ from unskilled laborers and why management really needs to as well. It included the relationship between money/motivation and trust/blame. I also particularly liked chapter 7 on not using metrics against people so as to not taint the data you get back.

Did I mention that part wasn't about TSP. Well, kind of. Many of the examples were from TSP. The implication being that you need TSP to collect data. These points could have been shown as being more broad.

I did like the first part of the book. I'm taking off a lot of points for the strong TSP bias and the fact that it isn't mentioned on the cover or book description.

---
Disclosure: I received a copy of this book from the publisher in exchange for writing this review on behalf of CodeRanch.

More info at Amazon.com
Joachim Rohde
Ranch Hand

Joined: Nov 27, 2006
Posts: 423

For those among us, who also didn't know what TSP stands for: it's an abbreviation for "Team Software Process".
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 29257
    
140

Thanks Joachim. I'll add that in parenthesis when I submit this review to Amazon and Goodreads.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Joachim Rohde
Ranch Hand

Joined: Nov 27, 2006
Posts: 423

You are welcome. Before you post the review you should also change "And 5 pages (144 pages)" to "And 5 chapters (144 pages)" ;-)
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 29257
    
140

Joachim Rohde wrote:You are welcome. Before you post the review you should also change "And 5 pages (144 pages)" to "And 5 chapters (144 pages)" ;-)

Fixed. And thanks.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Leadership, Teamwork, and Trust: Building a Competitive Software Capability
 
Similar Threads
Managing Software Debt: Building for Inevitable Change (Agile Software Development Series)
Spring Persistence with Hibernate (Beginning)
Making it Big in Software: Get the Job. Work the Org. Become Great.
Arduino Robotics
Sun Certified Enterprise Architect for Java EE Study Guide (2nd Edition)