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.
Dennis Drogseth is VP at Enterprise Management Associates (EMA).
In the spirit of Earth Day, which is Saturday, April 22, we recently asked IT professionals for the tips and tricks they're using to help keep their data centers as green as possible. Here are a few ideas inspired by the responses we got ...
A majority of senior IT leaders and decision-making managers of large companies surveyed around the world indicate their organizations have yet to fully embrace the aspects of IT Transformation needed to remain competitive, according to a new study conducted by Enterprise Strategy Group (ESG) ...
The move to cloud-based solutions like Office 365, Google Apps and others is one of the biggest fundamental changes IT professionals will undertake in the history of computing. The cost savings and productivity enhancements available to organizations are huge. But these savings and benefits can't be reaped without careful planning, network assessment, change management and continuous monitoring. Read on for things that you shouldn't do with your network in preparation for a move to one of these cloud providers ...
One of the most ubiquitous words in the development and DevOps vocabularies is "Agile." It is that shining, valued, and sometimes elusive goal that all enterprises strive for. But how do you get there? How does your organization become truly Agile? With these questions in mind, DEVOPSdigest asked experts across the industry — including analysts, consultants and vendors — for their opinions on the best way for a development or DevOps team to become more Agile ...
Is composable infrastructure the right choice for your IT environment? The following are 5 key questions that can help you begin to explore the capabilities of composable infrastructure and its applicability within your own IT environment ...
What is composable infrastructure, and is it the right choice for your IT environment? That's the question on many CIOs' minds today as they work to position their organizations as "digitally driven," delivering better, deeper, faster user experiences and a more agile response to change in whatever vertical market you do business in today ...
As companies adopt new hardware and applications, their networks grow larger and become harder to manage. For network engineers and administrators, the continued emergence of integrated technology has forced them to reconfigure and manage networks in a more dynamic way ...
The complexity of data in motion is growing and risks undermining the success of the modern data-driven enterprise. A recent survey of data engineers and architects, conducted by StreamSets, sought to bring some perspective to the new reality in the enterprise, leading to some interesting insights about the enterprise data landscape ...
The biggest factor driving happiness is the quality of relationships IT professionals have with their coworkers, including users, peers, and managers, according to the 2017 IT Job Satisfaction report from Spiceworks ...