<< 1 >>
Rating:  Summary: Good Material for Experienced and Beginners Review: Good Material for Experienced and Beginners.
I would say that Cisco Press has continues with a good material! This book talk about Service Level Agreement is just a good guide and an excellent material to start you in the field of Service Level Agreement. Today's IT industry is working around this concepts and you can see the in a lot of flavors ITIL, ITSM and other but what you will find in this book is a very useful material to start delivery and enrich your knowledge.
The book is divided in 4 parts:
Service Level Agreement and Introduction to Service Level Management.
Components of Service Level Management Infrastructure.
Long Term Service Level Management Functions.
Planning and Implementation of Service Level Management.
The authors John McConnell and Eric Siegel and the technical reviewers David M. Fishman, John P. Morency and Richard L. Ptak have done an excellent work.
For the last 5 years I have work in the IT service industry and always struggle with the concepts of Service Level Agreement and how to deliver the best characteristics for my customer and for my company to establish a win-to-win relation and develop a long term relationship and this book has help me to clarify some concepts and get more deep knowledge on other concepts but the most helpful thing was to uncover some of the concepts in which you require to calculate a number and what components influence on it.
The Chapter about the ROI has good information. Some would think it has just basic material about ROI but it helps you understand in a clear way the basic and form you a strong background for some deep knowledge later in this subject. I will read it several times to establish this solid foundation and to correlate with some present work I am doing to put it into practice for my benefits.
I found that the Chapter about Modeling and Capacity Planning has not enough information. From my point of view the authors did not show us how modeling and capacity planning can impact the operations. In today's environment this two subject can help any IT professional justify and plan IT investment and to have a very useful information for the ROI and establish a more productive environment. This part of the book did not satisfy me at all.
If the authors decides to put up a second edition I will suggest them to add some appendix in which some different tools are shown that can be use and some other practical scenarios are shown where the reader can see how to link all the concepts.
I will have it as a reference if I am delivery any kind of it service; it will make my life easier and can standardize some concepts in my daily life. It is a useful guide for a professional with experience or beginners in this kind of IT field.
In the scale from 1 to 5, a 4 it lacks of more practical examples and information about more tools to help you deliver this kind of services and its benefits and drawbacks.
Rating:  Summary: Theory of Service Level Management is well explained Review: The book delivers an explanation for the staff and management of organizations that need to understand what Service Level Management (SLM) is and how to improve SLM in today's networks. There are not very many books out there that have tackled the subject of SLM and the author has done a good job in taking on this subject. The book begins with an introduction to Service Level Agreements (SLA) and SLM. It breaks down SLM into its basic components by introducing facets of a network that must be highly-available and responsive quickly to the inevitable failures that very few organizations can experience without major financial losses. Most network implementers know what needs to be done to design a network, or more specifically a web-based service, to be highly available but few have taken the step to analyze and detail it in the way that the author John McConnell has. The book enlightens the reader into parts of SLM that are performed everyday without thinking about the "what and why". I have worked on networks for over 8 years and have implemented Web-Based Services for half that time. Many of the points the author makes are taken for granted and never really analyzed to try to improve upon them by the majority of network designers and engineers. The book continues with a discussion on problem identification and resolution. The speed of identifying the everyday problems that may develop has become essential just as the amount of data a network administrator must weed through has grown. An example the book illustrates is a Denial of Service attack. This can be crippling to a business that depends on Web-Based Services to perform day to day operations or sales. The author reinforces the reason we need good tools to quickly identify the real issues among the false positives. The book ends with several chapters devoted to the steps in improving the quality of web based services from a theoretical level. You will not find any specific router configurations for example, but you will find out how the case can be made using Return on Investment (ROI) to begin planning on a web-based service. Included is a case study that analyzes this ROI. Lastly the book covers a SLM Implementation Plan moving from the documentation of the existing systems, to creating a baseline, and to fine tuning the service. The book continues with an explanation of creating and managing SLAs and ends with a look into the future of Service Level Management. Overall, I would rate this book a 5 out of 5. As I mentioned earlier, it is not a book that will teach you how to configure a router or switch to perform QoS. But it will teach you to think about the reasons why it needs to be done and the consequences of doing without some planning. The book has diagrams interspersed throughout the chapters illustrating such things as a Web Service Delivery Architecture that enhance the author's description SLM. I would recommend this book to anyone who is serious about knowing the heart of SLAs and SLMs and how they affect business today.
Rating:  Summary: Merges tools & process + sound SLM practices Review: This book addresses service level management at the tools level, but does not lose sight of the service and support delivery aspects of SLM as a discipline. This is a refreshing change from related books that focus on QoS, tools and instrumentation, and other technical details while skimming over the business objectives and process. More importantly, the material goes beyond network management aspects that characterize similar books by addressing SLM at the higher level of delivering web services.The first three chapters clearly explain service level management as a business goal, and as a set of processes which support those goals. The material on metrics is among the best I've read and cover both the technical and business domains. Chapters 4 through 9 systematically address each component and domain in the technical infrastructure, including approaches (such as policy-based management), key process areas augmented by technology (event management and realtime operations), and support delivery areas augmented by technology (application, server and transport infrastructure management). In all areas technology and process are integrated, and important metrics, issues and challenges are discussed. In chapters 10 and 11 the authors cover performance and capacity management with excellent material on load testing (Chapter 10), and modeling and capacity planning (Chapter 11). These topics are critical to an effective and comprehensive service level management posture, yet are often overlooked in many books, or are glossed over. Here the authors go into the same detail that characterizes the preceding chapters. The final three chapters cover implementation from making the business case to providing a viable implementation plan. This book is clearly aimed at technical professionals who design and implement tools supporting SLM; however, there is excellent material for professionals who work at the process level. Both groups will benefit greatly from this book, especially since in many organizations they work independently of one another. Another compelling reason to read this book is the material is consistent with the ITIL, as well as providing sound thinking and best practices in general service level management.
Rating:  Summary: Merges tools & process + sound SLM practices Review: This book addresses service level management at the tools level, but does not lose sight of the service and support delivery aspects of SLM as a discipline. This is a refreshing change from related books that focus on QoS, tools and instrumentation, and other technical details while skimming over the business objectives and process. More importantly, the material goes beyond network management aspects that characterize similar books by addressing SLM at the higher level of delivering web services. The first three chapters clearly explain service level management as a business goal, and as a set of processes which support those goals. The material on metrics is among the best I've read and cover both the technical and business domains. Chapters 4 through 9 systematically address each component and domain in the technical infrastructure, including approaches (such as policy-based management), key process areas augmented by technology (event management and realtime operations), and support delivery areas augmented by technology (application, server and transport infrastructure management). In all areas technology and process are integrated, and important metrics, issues and challenges are discussed. In chapters 10 and 11 the authors cover performance and capacity management with excellent material on load testing (Chapter 10), and modeling and capacity planning (Chapter 11). These topics are critical to an effective and comprehensive service level management posture, yet are often overlooked in many books, or are glossed over. Here the authors go into the same detail that characterizes the preceding chapters. The final three chapters cover implementation from making the business case to providing a viable implementation plan. This book is clearly aimed at technical professionals who design and implement tools supporting SLM; however, there is excellent material for professionals who work at the process level. Both groups will benefit greatly from this book, especially since in many organizations they work independently of one another. Another compelling reason to read this book is the material is consistent with the ITIL, as well as providing sound thinking and best practices in general service level management.
Rating:  Summary: Practical Service Level Management Review: This book really lives up to the title in that is focuses on a difficult subject matter and doesn't deviate into trying to cover a million other subjects. It will not tell you how to configure a router, a monitoring agent or set up a server application in detail; what it does is focus on how to correctly implement Service Level Management (SLM) across the various levels in an IT infrastructure just like the title says! It is a must read for anyone involved with or thinking of setting up an effective SLM organization for their company. I appreciate the authors' approach to traditional Service Level Agreements (SLA) being one of three portions for effective SLM that need covered with the others being Quality of Service and Quality of Experience. The latter is a subject that it seems like many in the field haven't paid nearly enough attention to as it is the most difficult to measure but is the most important to the customer. The portions of the book in regards to setting up correct Service Level Agreements (SLAs) are extremely useful. SLAs have to be carefully worded in order to accomplish their goal. One of their examples of how if you have a hundred sites and a 99% uptime SLA for the month, 99 of a 100 could not have any outage and the other can have 100% downtime for the month! It makes you think of all the SLAs that are sitting out there that really do not do what they are intended. The end to end picture that this book provides is especially helpful for those in management or project management positions. It covers how to make a business case for SLM based on the return on investment, the steps needed to correctly phase in the SLM for the company (a good strategy does not just get turned on overnight), and even how through the right modeling and testing it can continue to remain an effective tool going forward. SLM is not something that is just turned on and then everyone walks away. It is an ongoing project. If you are more focused on digging into the technology that pertains only to your position, hop through the book and read the chapters that are focused on the area you work in. There are dedicated chapters to the transport (network), server, and application areas in regards to SLM so if want to skip the big picture and focus on your area of responsibility it is easy to find the information. I would like to end this by saying that I wish I would have had this book three years ago when I was working for a company providing a managed web service over the Internet. It seems like the book is a perfect description of many of the things learned in real life. The only area that I would have liked to see additional coverage on is the number and types of tools that are available to perform the desired tasks. The book always gave at least one example of technology and at least one vendor (sometimes more) but I would have found it helpful to list a small chart with the vendors so I could easily use that as a reference but that is only my opinion.
<< 1 >>
|