Skip to main content

Posts

Showing posts with the label ITSM Planning

Simplifying Service Management

One of the things that troubles me at times is how often people try to make the world more complex than it needs to be. The world is really a rather simple place if you take the time to step back and avoid complexity. I recently read a statement that made think upon this problem again. The opposite of “simple” is “elaborate”, not “complex”— Dan Roam, The Back of the Napkin What people call complex, may in reality be elaborate. They confuse the two ideas. This can lead to issues in the delivery of Business and IT Services to customers. If someone believes a service is too complex they can often be less willing to make the effort to provide the service, or support it or improve it. Most likely the service is just elaborate (having lots of underpinning elements and components), not really complex (being of a nature that is difficult to understand). So how do we move away from complexity and towards seeing Service Management in terms of simplicity and elaboration? Here are several tech

Where to start with SACM? Service Asset and Configuration Management

I often get asked the questions, "Where do I start with SACM? How do I implement this process?" In my experience, this is one of the most difficult processes to implement correctly. Let’s discuss the first activity of the SACM process of Planning . In this activity, decisions will be made about the scope of what needs to be controlled in your organization. What level of configuration management is required? How will that desired level is achieved? Do you gather information about a service or about specific components? Do you need to control assets which are causing your customers the most pain points? When do you establish a controlled configuration, how do you change a controlled configuration, and what amount of resources are you going to expend to manage configurations? All of these decisions must be documented and formalized within the configuration management plan. Configuration Management Plan: · Context and Purpose · Scope · Requirements · Applicable policies and stand