Category Archives: Deployment

In Case Of Emergency Press 1

[Note from the author: after some fact checking I discovered that I used the Red Card in a wrong way in this blog post. The red card must be used to raise issue like low volume or high temperature in the room, which can lower the quality of the gathering of information. For normal interruptions the yellow card should be used.

This basically means that I had to rewrite the blog post on certain points. This task was more complex than I had expected. The whole flow of arguments had to be restructured while preserving the spirit of this post. So I only added this note.]

Speaker: Welcome to my writing “In Case Of Emergency Press 1”. My name is Han Toan Lim. I want to share some stories with you.

Facilitator: There is an opportunity to ask questions using K-cards. More information can be found here.

Speaker: In the weeks after the Dutch Juggling Convention in 1992 a new story circulated in the Dutch juggling community. During the Public Show some people had paid an undesirable visit to the camping site. There were no guards.
“Right after the convention I would be camping. The convention [in Delft] looked like a good rehearsal, then someone made some cuts in my tent.”, a juggler told me with a bit of disappointment.
Another juggler was really upset:
“They took my knife from my tent.”
Somehow this unwanted visit was not anticipated. Over the years the story was shared less and less, but it still stung me.

Now it is time for a flash forward. Several projects were weeks from the deployment. I had pressed for a meeting and finally my project manager had agreed. During the preparation of this meeting I had merged 3 Deployment Plans of the three systems on the same day. I had still doubts about the completeness of this resulting plan. All suppliers and other involved parties of the client were present. I was the chairman.

I began with stating the goal of the meeting: everyone should know, what and when they should do in order to deploy 3 systems on the same day. On the screen I showed a gantt chart made in a spreadsheet program. It was an updated version of the team lead of system administration. The time blocks for the deployments of each system was shown. Other time blocks were for preparation and wrap ups. Then it was time to go one level deeper. On the screen the latest version of the Deployment Plan was shown by me in a spreadsheet. The first activities took me some time to let the attendees make themselves familiar with the structure of the plan.

Facilitator: We’ve got a red card.
Attendee 95: What do you mean with “make themselves familiar” with the Deployment Plan?
Speaker: The Deployment Plan was a big table in a spreadsheet. So the size could distract the reader. So I first explained the heading from left to right. Then I went slowly through the first action. So the attendees could listen or read the information with enough time for reflection. Does this answer your question?
Attendee 95: Yes
Facilitator: I see no more red cards. So you can continue.

Speaker: The following pattern arised. I read the action aloud and made sure, that the person, who was assigned the task, fully understood the task. I questioned or let it questioned in different ways:

  • Do you really understand this action?
  • Are other actions needed?
  • Are the actions planned in the right order?

I preferred, that other participants voiced their thoughts. This was beneficial for the group interaction. It was not my one man show after all.

Let me focus on one particular action, restoring the backup. If the deployment would be stopped, then a rollback of the old systems had to take place. So a backup should be restored. But it takes a while to make a good one. To be more precisely one working day. So people had to be instructed, that the systems could only be used for retrieving information and not for storing new information. Some of these actions had not been planned in.

Because no abstract actions had to be discussed, it was relatively easy to describe the specific actions. If there was agreement about the action, then I immediately updated the deployment plan on the screen. If the description of the action was still ambiguous, then people had the opportunity to clarify it.

Then came the part of the failed deployment. Some attendees were reluctant to talk about it. There might be different reasons: the actual steps for a successful deployment were discussed in depth, so they probably would not be needed. Another guess of mine was, that after 2 hours of meeting people were tired.

Afterwards I got the compliment: “You did well.”

This writing I would like to end with a Lesson Used. So time for a flashback.

In 2002 I went to one of the organisers of the Dutch Juggling Convention in Amsterdam. He told me:
“I’ve got some flowers for you.”
Before I could digest the information, he continued with:
“Right after the Public Show we asked the volunteer coordinators on stage. We called Nienke [and gave her flowers].”
Then I said:
“The other volunteer coordinator is Han Toan Lim. He is not here. He’s watching the camping site.”
He waited a moment.
“They gave you the biggest round of applause.”
At that moment I was just relieved, that no bad things had taken place at the convention’s camping site.

I thank for your attention.

Facilitator: You can ask questions using this form. I have already 4 green cards.

[To be continued here.]

Sound check (and other interesting things in other backyards)

Xoun is a strange brand name to pronounce. The question is, whether this sounds right to shopping people. If you turn the picture upside down, you will read a known brand name in the Netherlands. (Which I associate with a mug with welcome warm soup after hours of sailing on the lakes in Friesland.) By taking a different view some things might need more attention than you might expect. In this article I will tell about three situations, in which non IT related information can be helpful for an IT engineer.

Granting a small favour

In the nineties my customer planned in a special activity to introduce internet to his employees. So I ended up talking with a woman from the legal department. She stated, that shipping information should always be mentioned. It would save her department and company a lot of time and money.

A few weeks later it was time for my courtesy call. I called the lady from the legal department. After a short introduction I came to the point: “I just discovered, that your company is selling products on the internet. I could not find the shipping information.” A silence followed, so I had to repeat the message. A muffled “Thank you” followed. A few days later the web shop was off line.

In case of surprise

A special meeting was planned and the project manager was constantly talking about Rbbit. After a while I figured out, that the Rbbit was not a nice white fluffy animal appearing in the magician’s hat, but a Big Bug in the software system. “Two weeks ago we had a Rbbit. Last week we had a Rbbit. What do you expect for next week?” I answered, that another Big Bug would show up. “What are we going to do?”. I spoke up again: “I would set up an emergency procedure.” The project manager was not pleased with the answer: “Do you expect, that I will restore the complete database?”

“If wrong information is sent to the customers, then a new mail must be sent to them, that they should ignore the information in the sent mail. You could also add information, when the right information will be sent. The next step is to investigate and solve the problem.” The project manager finally agreed: he needed phone numbers of people in the operations department and operational measures.

What’s it in for them?

As a software tester it is very tempting to use different plug ins in your browser to analyse web sites. During one of my trials I encountered a tool, which provided me much information. I did not understand, why the tool was given away for free. The web site for the plug in tool was basically stressing the benefits. At that moment I was doubtful, whether I had installed malware.

After more extensive searches on the web I discovered a related business web site, which offered information about websites. This information was gathered by users using the above mentioned plug in. So the business model was as follows: determine, which information is useful for IT people. Provide a free tool for collecting information and sell the gathered information with a nice profit.