FooBar - a modern dromedy in three acts
Michael Klein 9 August 2018 12:14:10
ACT I2016.08
Company: "We need to decommission system Foo soon. We have system Bar now delivering the same services. What do we have to do."
Me: "No prob, here's the list of systems using Foo. Have your networking team check the routing and open all necessary ports to system Bar and then configure your systems to connect to/use Bar."
C: "Thanks, will do."
2016.09
M: "Regarding that Foo topic - please let me know if you want me to coordinate the tasks with the involved parties."
C: "No, all good. We know what to do."
2016.12
C: "How long till licenses for Foo expire."
M: "Let me see - this will be JUL 15, 2017."
2017.01
M: "Regarding that Foo topic - please let me know if you want me to coordinate the tasks with the involved parties."
C: "No, all good. We know what to do."
ACT II
2017.04
M: "Regarding that Foo topic - please let me know if you want me to coordinate the tasks with the involved parties."
C: "Ah, the Foo topic. Yes we need to decommission that system soon. What do we have to do?"
M: "I've sent a list of systems using Foo a few months ago. Just point them to Bar and have your networking team open all necessary ports to Bar so your systems can connect to Bar."
C: "Thanks, will do."
M: "Please let me know if you want me to coordinate the tasks with the involved parties."
C: "No, all good. We know what to do."
2017.05
C: "How long till licenses for Foo expire."
M: "This will be JUL 15, 2017."
C: "OK. We'll set a deadline for JUN 30. Until this date, all systems will be changed to Bar and we'll do a proper shutdown of Foo. I'll create the necessary change."
ACT III
2017.06
M: "Regarding that Foo topic - please let me know if you want me to coordinate the tasks with the involved parties."
C: "No, all good. We know what to do."
2017.06.25
C: "Ah, we cannot do that change JUN 30 as not everything is ready from network side. We'll just use the rest of the time to do the work and don't do a proper/planned shutdown but let the licenses expire."
M: "Ahm. Not recommended but up to you."
2017.07.16
C: "We have a problem with our production system Vortex. It cannot connect to Foo. The admin of Vortex is on vacation in Singapore and he says that business is stalling. Everybody else from operation and network teams seems to be on vacation. Can you help?"
M: "Ahm. Licenses have expired but we could enable Foo's function Void so that at least business can continue."
C: "No that's no good, Foo should not be re-enabled. Wait, just got word that some guy is still here and that they somehow implemented a workaround for the systems to connect to Bar."
M: "Good work!"
Lessons Learned:
- act early
- plan your actions properly (create specifications / checklists)
- consider risks
- do a POC (review and update specifications / checklists)
- do proper tests (review and update specifications / checklists)
- do a pilot (if at his point you have to alter specifications / checklists, you might want to take a step back)
- act actions according to checklists
- hold on to the schedule
- if you don't know what to do > get help
- if you don't have time to do it > get help
- don't panic
Disclaimer:
This dromedy is protected under copyright law. Country of first publication: Switzerland. Any unauthorized exhibition, distribution, or copying of this dromedy or any part thereof may result in civil liability and criminal prosecution. The story, all names, characters, and incidents portrayed in this production are fictitious. No identification with actual persons (living or deceased), places, buildings, and products is intended or should be inferred.
No animals were harmed in the making of this dromedy.
Comments Disabled