In the IT service management (ITSM) world there’s often talk of the need for configuration management and configuration management databases (CMDBs), and also IT asset management (ITAM). It can seem a steep challenge for many organizations, but it doesn’t mean that you can’t start with something far simpler – inventory management.
It’s all well and good talking about configuration and asset management but what if you just want to start with the basics? For instance, inventory management is an activity, or process, that should be easy to implement in theory. But in reality, scope creep, tool set limitations, and plain-old confusion about what inventory actually is, means that getting it right the first time isn’t necessarily a given.
Done well, inventory management can get the day-to-day costs of your IT estate under control and set the stage for more-involved asset and configuration management later on. With this in mind, I give you my seven top tips for effective inventory management.
Aha, the highly-effective series continues. Release management is often a misunderstood process, or capability, with the dividing line between it and change management often blurred. Let’s try to clear the blurriness in this blog.
Release management is the process that deals with major deployments, aka “the complicated stuff,” and its scope extends to hardware, software, networks, code, the cloud – anything that’s big enough and complex enough to need a significant level of coordination and support to deploy it effectively. How good your release management capabilities are – both initially and longer term – depends not only on your release management process but also the effectiveness of the people involved.
DevOps isn’t just about development, the creation of new code and capabilities, there’s also the need to release to the production environment in a way that’s both swift and “safe” – protecting business operations in line with the organization’s appetite for risk.
Much has been said and written about the left-to-right DevOps pipeline, most of it about the starting left-hand side where the developer and version control system trigger a continuous integration process to create a new test environment. But wait, what about the “production side”?
This awkward, right-hand end of the pipeline (the shaded-red area in the diagram below) is often skirted around or skimmed over when good practices are shared in blogs or at events.
Following on from my previous enterprise service management blog, here’s more tips on how to get started.
As a quick recap, part 1 offered advice on how to: (1) self-assess, (2) look for quick improvement opportunities in other lines of business, and (3) plan effectively. I’ll continue with another five “getting started” tips:
Enterprise service management – that’s the use of IT service management (ITSM) thinking, principles, best practice processes, and technology in other lines of business such as human resources (HR) and facilities – continues to be a popular focus for IT departments looking to add even more value to business operations.
Following on from my blog about COBIT and IT4IT, here’s the next in my ITSM 101 series and this time I’m writing about enterprise service management. Enterprise service management is about applying a service-oriented business model to the way your organization works. For instance, we all know that, done well, an IT service desk supported by the right ITSM processes (and people) can transform an IT department – making both the IT and issue resolution run more effectively and with greater efficiency.
So why not apply that same service management capability to the rest of the business?