Finance-Software

This is one of the earliest in a series of books that Cusumano has written on software technology. In this book he cries "Wolf!": the Japanese are so much better at industrial strength software development than Americans, they have a "software factory", etc., etc.

In his subsequent books, especially those on Microsoft and Netscape, Cusumano slowly discovers that the traditional software development process, requirements/specifications/code, etc., e.g. the waterfall model, is *NOT* the model adopted by successful software companies (and, indeed, not the model adopted by many hardware companies). He learns that designs are not something to be churned out by a factory - indeed, if they can be churned out, then they should be reusing exactly the same software.

In some ways the packaged software industry, e.g. Microsoft, supplanted the custom software industry in this timeframe, the time of the PC; Microsoft's process, which Cusumano calls "synchronize and stabilize", may be considered to be JIT (Just In Time) software specification and development. Or, if not Just In Time, As Soon As Possible and No Earlier than Necessary.

While I cannot agree with the conclusions of this book, it is interesting to have on one's bookshelf, to see the evolution of the author's thought over time.

The explanation for what happened to Japanese software factories is in Cusumano's latest book, The Business of Software, which is a more valuable read. The Japanese factories tried to solve the problem of efficiently building custom systems for Japanese customers using mainframes. Cusumano still argues that the factory approach worked well for mainframe software but Japanese programmers didn't have the skills to shift to newer platforms (PCs, workstations). I think the author over-estimated what the Japanese would be able to do. The Japanese are still struggling with old-style development techniques, despite close to zero-bugs, according to recent data from Cusumano. The Indians adopted similar practices (standard dev techniques, reuse, statistical data) but with much better trained people, more adaptable processes, and have been able to handle a wide variety of systems requirements and technologies. I still find Japan's Software Factories a useful look at how Japanese and some U.S. companies made progress in software engineering, particularly their approach to quality control and testing, and reuse. The Indians have gone a step beyond Japan, but they had to start somewhere.

Well written detailed book giving a great overview of what you need for successful project management. Luckily, it prepares you to take the IT Project+ exam very well also. The exam isn't easy, but with this book you can do it.

Well written book. I used it and the SelfTest Software PK0-001 exam Prep SW (002 version not yet available) to study for and pass the PK0-002 exam in less than a month. Be warned though, like everyone says, this is not you normal techie exam. If you don't understand fundamental management concepts you will have a hard time with the exam. I have had a good amount of PM experience over the years but still found this book to be helpful in addressing some of my blind spots. This is a perfect book to prep someone with some PM experience (formal or informal) to PASS the exam.

This is the best book on Project Management (IT or other) I have read and I have read a lot of them. I am a PMP and got this to prep for the IT Project+ certification, very wise choice.

Book is very well-written, informative, and entertaining (yes it is entertaining) to read.

I highly recommend.

This book is written only for the very basic beginner in IT. If you have been around an IT department for any length of time, you will find it difficult to pick up any new management thoughts in this book. For example, the entire topic of ERP systems is covered in 2 pages.

Technology can change all it wants but the fundamentals of being a good IT Manager have changed very little. This book hits all the major areas of focus from staffing and budgeting to infrastructure and disaster recovery.

The section entitled "Certification: How Do I Know Its Worth" applied 10 years ago, and still applies today. Right on the money and a good brief for an IT Manager building a team. Also, small but extremently important policy issues like email and security are included.

I do think that the book included slightly heavy doses of technical information such as a full page table of different memory technologies as well as an entire section entitled "How Do I Configure a Server". These would service a Network Administrator or Engineer just fine but an IT Manager ? Not so much. Don't let this detract you from the overall picture though. Too much information is certainly better than not enough.

I have to be honest, I didn't read this cover to cover. But for someone who has spent time as an IT Manager in the past and one who is looking at doing it again, I was able to re-establish concepts and draw on new tools that, no doubt, provided benefits.

This book is full of practical examples. It is useful to people who have in-depth programming knowledge but no idea how to do a budget or interview job candidates. I found this book specially timely, given that my team is composed of several technical professionals who are now considering a move into management. The information in the book is well layed out and quite accessible.

Very American. Is there a world beyond their borders?

Doesn't mention Data Centers, doesn't talk about market trends such ASPs.

What about market data?

Is the American market really so simple? (Smile, be nice to customers and then sell to a bigger company)

This book has undoubtedly earned a place on the bookshelf of today's ISP owner. Its contents were invaluable information required for the business plan I prepared for an ISP/ASP business.

It s a wonderfull book, about how to run a ISP, and how to identify your market, and develop your bussiness strategy in each segment.

The first three chapters are dedicated to know what is the ISP bussiness, to know your strengths and weakness, and the strategy you must develop to grow.

The next chapters are dedicated to know marketing techniques especially focus in the ISP bussiness, and how to develop the rigth one for your organization.

It s a well organized book, that I can recommend to every small ISP, who wish to grow up.