Finance-Software

Whitehead covers alot of the basics of team management. It shouldn't be difficult, and that what Whitehead explains through "questioned" title chapters. It works quite well because you can zero in on the question about leadership in your situation that may be plaguing your mind. The book is short and easy to read, so it can be read in about 3 days on a bus.

The author subscribes to making you aware of the qualities of good managers and how to handle common types of problems, like what to do when you don't have the technical knowledge about a problem, or how to handle difficult/disruptive team members. In summary, Whitehead helps you get into thinking like a ternary leader, that is you are part of a group, all working towards a common goal and you, (the teamleader/manager), should not dictate your "will and whim" to others.

The only criticism is that it is probably too light on the aspect of project management. There are issues about project management of people in terms of requirements, risk, scheduling that are not discussed. This book is about working with your colleagues not clients.... but overall a good read at a good price.

After reading this book, I would say for sure that Richard Whitehead understands the role of the project lead. I would buy this book for a new, or existing lead, if I wanted him to understand the challenges he might face. I really applaud this and would add that many books feel like they were written from the outside looking in (sure, everyone on the outside wants twice the functionality in half the time!). I would love to see an update that included more strategies for success however. A lot of the solutions seemed to be based on a specific set of circumstances and personalities. Perhaps adding some examples from others who faced similar challenges, and overcame them with different methods, would increase the impact of this book.

While the programmer in me has often railed at the managers of software development, generally with very good reason, but admittedly sometimes for reasons that were less than pure, I do readily admit that it is a very difficult job. Humans tend to have distinct sets of skills, some of which seem to have a fundamental incompatibility. Writers of good software seem to be predisposed to having limited social and managerial skills and in general one needs to be able to understand a great deal about software in order to be able to manage its' creation. Programmers are also known as being "somewhat difficult" to organize, so even the best managers can be challenged by what is oftentimes an unruly bunch of developers.
However, difficult does not mean impossible, I have yet to meet a quality programmer who did not have a "weakness", that properly exploited, will cause them to work intensely and log an enormous amount of keyboard time. Teams are built in many ways, and Whitehead quite properly notes that many (most) successful teams are made of people who respect and rely on each other's skills, but may not personally like each other. Some of the most successful sports teams of all times were made up of players who did not speak to each other outside the bounds of play. Arguing and bickering, as long as it is within clearly defined boundaries, should be considered normal and tolerated. Attempts to dictate that people like each other and engage in silly "teambuilding" exercises more often lead to failure rather than success. Other examples in the book show the same good sense, as Whitehead clearly has experience in making projects work.
The book is split into sections, which are

* The new leader.
* Project management.
* Leading people.
* Requirements capture.
* Stress and conflict management.
* Relationship with management.
* Making decisions.
* Analysis and design.
* Testing and project release.

Under these sections, there are a total of 40 different points, with a header and explanation of some of the rights, wrongs and different shades of gray inherent in the points. While forty is not large enough to cover all possible contingencies, I cannot find a reason to criticize those that were chosen.
Writing good software is hard, and managing hard people is difficult. However, from this book you can find some very sound advice that will improve your chances of managing a project to a successful conclusion.

If you are looking to have devotions at home, but do not know where to begin, stop looking. This book and the entire series are excellent. They teach biblical values through hands on expereince. As a pastor of a church, I am recommending this series to all members who have children. You do not need to know theology or know how to teach, just have a desire to set aside time one night per week and enjoy time teaching, learning and growing with your kids in a Christ centered fun way.

This is just a marketing glossy for Microsoft. All it does is keep saying "Microsoft is wonderful! Exchange is wonderful!".

This is a very introductory book with too little detail illustrating various solutions. While the book does mention the Microsoft products that could be used and have been used (which are now out-of-date) for KM, it does not really promote them. The book does not say that Microsoft products are superior to non-Microsoft products, nor does it even mention any features that Microsoft products have that many competitors don't.

This is a great book for outlining IT strategy in the corporate workplace, defining such terms/challenges as "buy in" (trying to get budget for projects to pass through each region), and the most important concept IT will ever have to deal with: the idea that business drives IT, not vice-versa. GREAT BOOK!!!