Decommission Analysis Guide - book finally released!

Finally is there! My first paper book has been printed out. The "Decommission Analysis Guide" is ready to be picked up from the Amazon bookshelf and read.

If you have been asked to analyze tens (or more) systems in your organization,  and you're whole in tears now,  this book is for you. That's a practical guide, that will help you to rationalize the task, and embrace a massive number of existing systems you don't know and have no chance to understand.

[Amazon store]

What is system decommission analysis?

A life cycle of all IT systems ends up with plugging out of the power supply.  Before it happens, we need to make sure we understand what is the real scope of the system, and what actually happes once the last led-light goes out.

It's not usually a big deal if we have a single system to analyze and an existing support/developer team  already that is up to speed, with an insight into the product.  The problem becomes more interesting once you realize you have to analyze tens (or even 100+) of the systems that have been build for the last 20 years.   In that case, most of the developers who have built those systems are no longer a part of the organization. Too much faith in existing and reliable documentation may bring you into trouble. 

Where can I find a list of the systems?

That's the tricky part - even if it sounds like the easiest.  The CMDB repository is always a very good place to start looking. Unfortunately, It may be a huge challenge to find anyone capable to confirm that list, especially if you ask about the systems' boundaries (list of its components). 

A very good example might be a database that is shared across two systems - which system owns the database?  

Practical guide

The systems' boundary and data flow discovery - that this book is about!  This guide will lead you through the whole end-to-end process, starting from the initial workshop,  plans and estimates, MVP,  the blanket/dedicated analysis, and data aggregation.  

During the next couple of weeks, I will try to put more light on the described process, especially in the context of migration (i.e.  Cloud Adoption Framework).


Sold for profit - Absoluty NO!

There's no profit for selling this book. The price covers the cost of printing and Amazon's fee only. All of those is to make sure you can get the paper book version without any extra costs.



Special thanks!

This book has been created based on my personal experience working for our clients in GFT, but not only. Given that, I would like thank to  GFT Poland, for the support and help.  

Comments

Post a Comment

Popular posts from this blog

Podman using Ubuntu WSL2

Image
The Docker Desktop for Windows is no longer free for commercial usage, or at least in many cases. If your local development environment is Windows, and you're looking for an alternative, this article is for you. "Docker Desktop remains free for small businesses (fewer than 250 employees AND less than $10 million in annual revenue), personal use, education, and non-commercial open-source projects.". Unfortunately, containerization is a foundation of most enterprise-level projects these days, which size causes the licence issue.  The commercial doesn't cost an arm and leg, even though it builds unnecessary concern and limitations. Even if you use the WSL2 Linux image, you need to use the docker engine, which is a part of the Docker Desktop for Windows. Podman as Docker And here is the beautiful moment when Podman comes into the play. It's a root-less and demon-less solution, fully compatible with docker. If you have been ever concerned about the demon working in the...
Read more

Automatization of test cases in SCRUM

Image
Test case automation may bring many benefits for the application/system QA process, but it's not always obvious how to introduce an implementation of the test cases into SCRUM flow.  The SCRUM methodology defines the number of PBIs (product increments) for prioritization and planning, as a part of the SCRUM process. Those could be user stories or enablers , sometimes bugs . Each of the PBIs needs to be estimated and confirmed by a scrum team before it's added into a sprint scope (sprint backlog). The question would be: How to plan the effort for the implementation of automation tests, as those are not the PBIs per se? Test Case is not a PBI In the strategy proven in one of my projects, a test case is an output (product) of the delivery, just like an ordinary artifact. Typically, it's a part of a testing suite. It needs to be created, maintained, and placed into a repository (see: Azure DevOps ). Once prepared, we can start working on the automation of the test case. Bo...
Read more

Azure Synapse - first contact

Image
Despite the fact I've spent the last two years working with Microsoft Azure cloud tech stack, I didn't have a chance working with Azure Synapse yet. Finally I've met this guy. The first impression is very good. Azure Synapse Workspace To create the first Azure Synapse you need to create an  Azure Synapse Workspace . If you are already familiar with Azure you may already know Azure Log Analitycs Workspace to examine logs and operation of your applications and resources. Here is the same. Workspace is created within the Azure resource group, building a landing page for its settings, analytic pools, security, and monitoring aspects. Azure Synapse Workspace will require a storage account to be created/selected under-the-hood. A storage account will be used to build Azure Data Lake Storage Gen2 for the files you will manage by yourself (sample data for processing) or by the Azure Synapse itself (ex. PySpark trained models will be saved here as well).  The better place to deal...
Read more