Finance-Software

This book covers all of the key points and provides some excellent topics to include in a corporate e-policy. The goal of this book is to aid you in developing a policy that will provide clear, enforceable guidelines to your employees in the acceptable use of the Internet and electronic mail, and to protect your company's image.

It starts out with a well developed approach to assessing your current situation with respect to Internet and software usage, and provides a handy list of questions to aid in this task. The key objective is to discover your company's exposures and what abuse of systems or services [if any] need to be immediately addressed by the policy.

In order to fully understand the results of your assessment and how they relate to risks and exposures, the author provides fundamentals of "cyberlaw" and general security concerns that will indicate, roughly, the degree of risk your company faces. These are important considerations for tailoring an e-policy to which your employees can relate. I liked the chapter on cyber insurance products and how they can be used to transfer some of the inherent risks to an underwriter. I didn't even know such policies existed. The author also addresses software piracy, which can be a big issue because the world wide web has many sources for pirated software (commonly called "Warez"). It goes without saying that pirated software can expose your company to legal headaches and expenses, not to mention technical headaches and lost productivity that will occur if that stolen software also comes with a virus attached.

The book then shows you how to develop an e-policy that is based on your assessment results, and the issues previously discussed in the book. What is valuable here is that the author provides a list of all elements that need to be included in the policy. Moreover the next chapters provide additional material that will prove to be invaluable in preparing your company for the policy. For example, there is a "Netiquette" primer for employees, on-line writing guidelines, and advice on training your employees. The training aspect of implementing an e-policy is especially important because many employees have home computers and are experienced Internet users. They might consider themselves to be experts and may resent being "constrained" by a policy that dictates how they use the Internet at work. Educating them and getting their "buy-in" is essential, and the author provides some effective ways to get that "buy-in".

I found the sample policies in the appendices to be particularly valuable to use as guidelines for drafting a clearly-worded policy that covers all key elements. The applicable laws cited in the appendices were also valuable because they indicate the many sources of legal risks (and protection) that touch an e-policy.

This book provides an excellent starting point for developing an effective e-policy that can be closely tailored to your company and "sold" to your employees. Its clear writing, completeness and sensible advice earn it 5 stars. I will offer one caveat: any e-policy developed based on this book or any other should not be issued until it has been carefully reviewed by legal counsel. I am not an attorney (I am a computer consultant by profession), however, I do know that such a policy touches so many aspects of privacy and employment law that you may put your company at greater risk by implementing a policy that has not been reviewed by qualified legal counsel than by having no policy at all.

This key to designing and implementing email and software policies in a company structure provides business owners and managers with important information on how to produce clear policies which regulate computer use. From workplace piracy to e-theft insurance, Nancy Flynn's The ePolicy Handbook covers a wide range of topics and concerns.

This book tells you exactly what it says on the cover "How to effectively manage e-business implementations". The chapters are short and sharp, the assumption is made you have experience in project management already. This is NOT a book about project management. I found the structure excellant for "active readers", easy to scan through and revise back on. If like me you manage several project you'll end up going back to it again and again.

If you want to learn what e-commerce is and get a lot of jargon involving the words ¡°chain¡±, ¡°global¡±, ¡°supplier¡±, ¡°customer¡±, and ¡°e-¡°, do not look here. This is a book on how to do e-commerce. I am a manager at a software firm that implements e-commerce solutions. In doing many e-commerce projects over the past 4 years we have found that implementing e-commerce is quite different and more complex than standard IT projects. However, most books either do not address putting e-commerce in or they treat e-commerce as an IT application. E-commerce is not a standard IT project. Today about 40% of our staff do business analysis and support tasks for e-commerce rather than IT work. This is the first book to deal realistically with the problems that people in the real world face when they do e-commerce. We are now buying this book for our customers as well as our staff. The book handles the roles of business staff, consultants, and systems staff. More importantly the book discusses in depth how to detect, handle, and resolve specific things that you are likely to meet up with. This book is both valuable and realistic.

The authors have used their experience in e-business implementation to provide specific guidelines and tips in implementing e-business projects. The book deals with many technical, management, user, and vendor issues that you are likely to encountered and that we have dealt with in our e-business efforts. There is more time pressure and higher management expectations for e-business than standard IT or business projects. There are good suggestions for dealing with the time pressure. E-business is a program since one project leads to another. E-business projects overlap. This book addresses that in four chapters that handle expansion and on-going e-business. Using this book we have encountered fewer problems in our latest e-business project than in previous efforts. Some other areas of the book that are good are dealing with competing demands for resources between regular work and e-business projects as well as the method for tracking, analyzing, and reporting on e-business issues. Chapter 15 has some good charts and analysis for e-business issues. Another useful idea is to have multiple project leaders for the e-business implementation. There are examples in banking, manufacturing, retailing, and natural resources that are followed through the book. While written for e-business there are useful ideas here for IT projects overall.