Customer Reviews

Information Systems: Policies and Procedures Manual: 2000 Supplement (Information Systems Policies & Procedures Manual Supplement, 2000)

5 star:		(0)
4 star:		(3)
3 star:		(0)
2 star:		(2)
1 star:		(7)

 

 

Dr. Jenkins may have 23 years as a IS practitioner and published numerous articles but on this book he clearly missed the mark. The book does provide some very general and generic information an IS manager might use but all-in-all it is a dougnut that is all hole.

What this book lacks are specific examples of policies, procedures and, "real world" examples of their benefits and ROI's. Considering that the book contains the FY2000 supplements on CD it is very disappointing that Dr. Jenkins did not take the time to include examples of policies and proceedures in MS Word or PDF format that IS managers could easily load and modify to meet their own corporate needs.

There is also a lack of information on "why" things are important to include or to leave out. The result is that this book focuses on a hodge-podge of random theories creating a sort of theory stew, instead of providing a meat and potatoes platter relating the theories to "real world" facts, situations, and examples. I realize that no book can contain all the policies and procedures suited to my own corporation, none-the-less I am disappointed that this book did not provide a better basis for me to work from.

End thought: "I could have saved the money on this book and gotten the same information from common web sites."

Provides page after page of procedures to be followed for various tasks. These tasks are general enough to apply to a number of computer-related fields, but specific examples of their application are lacking.

The reasoning behind the procedures is not discussed, leaving the procedures open to question. This book could have been greatly strengthened by adding some discussion and examples.

For example, Chapter 6.2.2 "Data Library Operating Procedures" section A "Receiving new disks and tapes": "Upon receiving new disks or tapes, the data librarian: 1) Compares quantity received with original order... 2) Inspects disks or tapes... 3) Logs in new tapes or disks... 4) Notifies the computer operator..." (condensed for brevity)

The author does not explain why checking the order should be handled by the tape librarian rather than by shipping/receiving. Other tasks mentioned, such as "the date received and vendor are also posted to the! consecutive number log" are of questionable necessity, and these questions are left unanswered. Isn't the above information available as part of the original tape order? Why include it in the log intended primarily to ensure that the proper tapes are used at the proper time? He may well have very valid reasons, but these are never explained.

Similarly, his classifications seem arbitrary at times and such important data center concepts as service-level agreements with clients were never discussed.

Prentice Hall may have found a title that many IT professionals are interested in, but, unfortunately, the content of the original book is far from practical and shows little REAL WORLD experience. Why Prentice Hall created a supplement is beyond me?

I was hoping to use this book as a guide for composing SOPs for a small IS group. However, I found the information to be too general, so as not to help with this endeavor.

The table of contents provides a good template for creating your own policies and procedures outline, however the content is much to general. This purchase was a mistake.

The book is an outline of information that assists you in improving your department/office without tying you down in one specific method. This allows one (along with that of their peers and subordinates) to relate their previous work experience(s) to an information systems environment. Items such as IS procedures, policies, and organization; shipping/receiving, inventory control; technical publications library procedures, and training, to name a few, are discussed in this not overly specific method so commonly desired by others. With this outline one can quickly put together a specific plan tailored for their own environment.

Very broad book as another user wrote. No practical policies that can be used by your organization.

Prentice Hall may have found a title that many IT professionals are interested in, but, unfortunately, the content of the book is far from practical and shows little REAL WORLD experience. One can only conclude that this is a collection of various isolated and/or theoretical policies and procedures from numerous sources that have been cobbled together without seeing how they interact or would actually work in the real world.

Prentice Hall may have found a title that many IT professionals are interested in, but, unfortunately, the content of the book is far from practical and shows little REAL WORLD experience. One can only conclude that this is a collection of various isolated and/or theoretical policies and procedures from numerous sources that have been cobbled together without seeing how they interact or would actually work in the real world.

Nice.

This is my bible, a book every slimmie should have on their desk (but not their feet). There aren't enough ohs in smoooooooth to tell you how choice this rhode island red book is for the IT professional. Sit back, grab a slab of coffee and read this peepskin cover to cover. I guarantee that this is a book that describes the thing and the thing better than the rest. You won't be a KTR if you own this book.

Give me a blast if you have any questions. Take care and as always thanks for your time.