Here There Be Dragons! Mapping IT Environments
Why Map your IT EnvironmentsMapmaking, or cartography, has been an integral part of the human history for tens of thousands of years. From paintings in caves to ancient maps of Babylon, Greece, Rome and Asia, through the Age of Exploration by the Stars, town planning to avoid contention and onto today with the likes of Google Maps & Geo-Location-ing.People, government & businesses, have created and used maps as a tool to help them define, explain, and navigate their way through towns, cities, counties and the world itself. And Imagine the risk of doing trade without them?
- Scope: Destination unknown
- Cost: Journey expensive due to sub-optimal route
- Risk: You might never get there (Here there be Dragons)
- Time: Late delivery (assuming you get there)
- Quality Risk of spoilt goods
- “Where does “Mapping” sit in the realms of IT & Digital Delivery?”
The Value of IT Environments MappingSo why is Environment Mapping so important, well here are 5 reasons:1 Knowledge via a single pain of glassEstablish a holistic view of your IT landscape that allows you to bring it all together and abridges IT and Business appreciation, team upskilling and cross team collaboration. Understand your Environments Lanes and their sub-structure. Structure consisting of System Instances consisting of Applications, Data & Infrastructure and of course relationships with other Systems, Projects and the Business itself.2 Consolidate and/or Grow DecisioningEasily identify whether you have “footprints” that are over or under sized. Recognise over proliferation & quickly identify opportunities to save costs through proactive housekeeping and decommissioning. Or recognise under Proliferation, that causes contention, disruption & project bottlenecks, and address to streamline your delivery chain.3 Simplified Service ManagementStreamline troubleshooting and impact analysis after System or Component incidents & issues. Instantly recognise what is up and down and identify what that means i.e. how is it impacting your business, processes, other systems and the delivery process itself.4 Project Readiness & StreamliningEnsure Project Environment needs (and any gaps to goal) are immediately understood and accommodated i.e. Shit Left your Design, Architecture and Build practices and ensure your Environments are “Fit for Purpose” and provided in a timely fashion.5 Delivery Chain OptimizationEnvironments Mapping is the foundation for Behaviour Mapping i.e. it is not just about the boxes (as was often the focus in the early CMDB days). By attaching key metadata, for example system versions or data compliance, you can start to identify gaps and opportunities for ongoing improvement, for example the need to introduce tooling and/or automate key tasks.
Tips on successful IT Environment MappingSo, with the above benefits in mind, how does one go about successfully mapping their IT Environments. Well to be honest that’s probably beyond any brief post, however I’d offer the following pointers:
- Map Top Down! IT is the backbone of business, so start from a business perspective. This will allow you to develop “meaningful” associations across Business Units, Finance, Programs & Technology itself.
- Ensure its living! Visio Diagrams & Excel diagrams are static and get out of date very quickly. Implement methods & automation to ensure maps are continually regenerating. Technical debt is the reason 95% of CMDBs fail.
- Don’t think Box! Mapping need not and should not be focused on the physical. Think more broadly about how these maps will allow you to get to your corporate destination. For example, help projects deliver more quickly or cost-effectively by interlacing key meta data that allows effective insight and decision making.
- Don’t leave it to your Infrastructure Team! Or more fairly, don’t let the tail wag the dog. Sure, Infrastructure is important, but mapping bottom up should be a compliment to Top Down opposed to a “practical” alternative.
SummationWhether you prefer to call it Enterprise “Configuration Management” or “Environment Mapping”, it is clear, delivery agility comes from transparency, collaboration, less disruption and good operational decision making, and understanding your systems & relationships is key to that success.Anyhow, let me know what you think.
16September, 2021 by Carlos SchultsLet me start with a question: as a leader in tech, are you satisfied with the budget you have? If I had to guess, I'd say the answer is no. Because of that, calculating the return on investment of the many activities in software...
14AUGUST, 2021 by Ukpai UgochiIt is the goal of every software engineer and software development firm to continuously ship products to end users. This can only be achieved through software deployment. In this post, we'll explore deployment and deployment planning,...
09SEPTEMBER, 2021 by Eric GoebelbeckerLet’s talk about container essentials. Over the past few years, containers have transitioned from the hottest new trend to essential IT architecture. But are they are good fit for you? Are you wondering whether or not you’re using...
05AUGUST, 2021 by Alexander FridmanIn the beginning there was nothing. Then there was the monolith, though we used to simply call monoliths "software." Today we have two rival architectural types: monoliths and microservices. This post will explain what monoliths and...
15JULY, 2021 by Justin ReynoldsCompanies go to great lengths to protect their physical environments, using deterrents like locks, fences, and cameras to ward off intruders. Yet this same logic doesn’t always translate to digital security. Corporate networks — which...
06JULY, 2021 by Justin ReynoldsCompanies today face increasing challenges around reducing the time and cost of software development. Many are thus using DevOps methodologies, which combine software development and IT operations to achieve continuous delivery and...