In writing CMDB Systems: Making Change Work in the Age of Cloud and Agile, we gained a lot by talking to deployments. In the spirit of our own recommendations for how to manage and optimize a CMDB-related initiative, our goal was to learn from reality more than just preach a series of best practices. What I’ve chosen to write about here are just a few highlights, following four key areas of interest:
■ Dialog, Communication and Stakeholder Planning
Dialog, Communication and Stakeholder Planning
Taking the time to engage stakeholders effectively is one of the bigger challenges in any strategic IT initiative, and one of the biggest single catalysts for CMDB success. One of the problems, of course, is time and energy to engage in something new, no matter how valuable, when most IT professionals are already overworked and trapped within their own treadmills.
The Hamster Scenario
“Cultural challenges were a big factor — in getting the silos to think about new ways of working together. Something like what I call the “Hamster Scenario” running around its wheel. You’ve got some processes in place and you’re used to those processes. When do you step back and change those processes? In other words when does the hamster get off its wheel and think it might move in other directions?” (a transportation/travel company from Chapter Eight)
Next is a comment in both the challenge and resolution category about dealing with a very different concern — too much enthusiasm, and with it, too many expectations:
Challenge/resolution: Trying to please everyone
“When we discussed the CMDB with different groups in our organization, each team got very excited about what they wanted to get out of our CMDB. But very quickly we could see that many of their priorities were at least a couple of years away from implementation. So everybody’s understanding of the scope was different. For instance, we had desktop people saying 'can I inventory my mouse? Can I inventory my keyboard and my monitor?' They all wanted to see those as CIs.
“But managing this wasn’t too difficult. I asked everyone two questions; first, ‘What is this equipment that you’re prepared to manage from day one through its entire lifecycle as a CI?’ And second, ‘Do you have the resources to manage these items as CIs once they get into our CMDB?’ If there were no costs associated with CI inclusion, then everyone would want everything included in the CMDB right at the start. But as soon as they begin to understand the costs, including update and data access costs, they viewed it differently.” (a manufacturer from Chapter Four)
We spend a lot of time in the book looking at architectural challenges, including a very progressive technology landscape as it’s evolving to support more dynamic and complex service interdependencies. Below are just two perspectives, the first on service modeling, and the second on assimilating multiple data sets.
Service models vs. data models
“Our Service Model is based on ITIL’s definition, and it’s all about the processes, functions, services and technologies that we deliver to our customers. So therefore it’s a separate idea that can be applied to the data model. Our Global Finance team defines our business strategies company-wide. And these are of course not about a data model or technology. But that’s where we started, so we can trace everything we do back to those business services.” (manufacturer from Chapter Four)
Assimilating and reconciling many multiple sources
“Each discovery tool has its own idiosyncracies in terms of what it captures and how it works. This impacts both our ability to manage it and our ability to optimize our hardware and software asset investments in terms of utilization and licensing. With our integrated data analytics, we’re leveraging 35 different discovery tools in order to get a more cohesive 'golden record' for the CMS ... This includes desktop security, network management and administration, application dependency mapping, systems management and administration, asset management solutions, and BSM performance management, just to mention a few categories.” (a financial services company Chapter Nine)
Cloud and Agile
Since our book does its best to focus on the very current landscape of cloud and agile, I thought it fitting to end with two excerpts — one on each point. I think both are a bit surprising as well as insightful, but I’ll let you decide which might raise more eyebrows.
“... the general idea is to leverage ADDM visibility for consistency across the cloud and hybrid cloud environments — so that you can identify servers that are not registered in your configuration management tools. Another example of the value of this type of visibility is keeping track of the Amazon Machine Images (AMIs), which can potentially lead to malware and other problems. There are over 30,000 community AMIs and not all of them are patched correctly, so if a developer decides to use one that’s not authorized it may cause problems. When that happens, ADDM can help to identify and remediate the problem.” (a software manufacturer from Chapter Fifteen)
“Before investing in the CMDB we were very fragmented in how we saved information. Some of it was in Visio, for instance. Some were in OneNote or in Excel. We also had a lot of Word documents — so it was difficult-to-impossible to get insight into impacts when we were about to make a change …
“At that time, development was a little bit ahead of operations in terms of maturity. Our operations organization was fairly siloed and hadn’t yet invested in best practices. We often had no clear idea what would happen if, for instance, we unplugged a server. Most of our change records there resided inside someone’s head … If somebody was sick at the wrong time, it could be very disruptive …
“But we did have some [scrum] best practices that had evolved in development for source control. So when we saw what a CMDB could do, we felt we had a chance to transform our way of working when it came to managing change.” (a mid-tier financial planning company from Chapter Fifteen)
All right, I’ll be candid. Probably the biggest single “revelation from the trenches” for me was this last — a development team purchasing a CMDB to support an agile environment using scrum and pushing it into operations.
The point being in these and other insights is that each deployment shares common challenges with other deployments, on the one hand; but is also distinctive on the other hand. The goal is, invariably, to find the best path for you — while learning from the many other voices of wisdom and experience available. And this was, perhaps, the single most pervasive "guiding light" in seeking out optimal content for our book.
In today's competitive landscape, businesses must have the ability and process in place to face new challenges and find ways to successfully tackle them in a proactive manner. For years, this has been placed on the shoulders of DevOps teams within IT departments. But, as automation takes over manual intervention to increase speed and efficiency, these teams are facing what we know as IT digitization. How has this changed the way companies function over the years, and what do we have to look forward to in the coming years? ...
Although the vast majority of IT organizations have implemented a broad variety of systems and tools to modernize, simplify and streamline data center operations, many are still burdened by inefficiencies, security risks and performance gaps in their IT infrastructure as well as the excessive time it takes to manage legacy infrastructure, according to the State of IT Transformation, a report from Datrium ...
When it comes to network visibility, there are a lot of discussions about packet broker technology and the various features these solutions provide to network architects and IT managers. Packet brokers allow organizations to aggregate the data required for a variety of monitoring solutions including network performance monitoring and diagnostic (NPMD) platforms and unified threat management (UTM) appliances. But, when it comes to ensuring these solutions provide the insights required by NetOps and security teams, IT can spend an exorbitant amount of time dealing with issues around adds, moves and changes. This can have a dramatic impact on budgets and tool availability. Why does this happen? ...
Data may be pouring into enterprises but IT professionals still find most of it stuck in siloed departments and weeks away from being able to drive any valued action. Coupled with the ongoing concerns over security responsiveness, IT teams have to push aside other important performance-oriented data in order to ensure security data, at least, gets prominent attention. A new survey by Ivanti shows the disconnect between enterprise departments struggling to improve operations like automation while being challenged with a siloed structure and a data onslaught ...
A subtle, deliberate shift has occurred within the software industry which, at present, only the most innovative organizations have seized upon for competitive advantage. Although primarily driven by Artificial Intelligence (AI), this transformation strikes at the core of the most pervasive IT resources including cloud computing and predictive analytics ...
When asked who is mandated with developing and delivering their organization's digital competencies, 51% of respondents say their IT departments have a leadership role. The critical question is whether IT departments are prepared to take on a leadership role in which collaborating with other functions and disseminating knowledge and digital performance data are requirements ...
The Economist Intelligence Unit just released a new study commissioned by Riverbed that explores nine digital competencies that help organizations improve their digital performance and, ultimately, achieve their objectives. Here's a brief summary of 7 key research findings you'll find covered in detail in the report ...
Today, the overall customer scenario has digitally transformed and practically there is no limitation to the ways in which the target customers can be reached. These opportunities are throwing multiple challenges for brands and enterprises, and one of the prominent ones is to ensure Omni Channel experience for customers ...
Most businesses (92 percent of respondents) see the potential value of data and 36 percent are already monetizing their data, according to the Global Data Protection Index from Dell EMC. While this acknowledgement is positive, however, most respondents are struggling to properly protect their data ...
IT practitioners are still in experimentation mode with artificial intelligence in many cases, and still have concerns about how credible the technology can be. A recent study from OpsRamp targeted these IT managers who have implemented AIOps, and among other data, reports on the primary concerns of this new approach to operations management ...