Category Archives: Juggling

Q&A Deployment Plan Meeting

[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.]

Facilitator:  Thank you reading “In Case Of Emergeny Press 1“.  I’ve got green cards from numbers 95, 27, 38, and 23. Number 95, you can ask your question.

Attendee number 95: Did you consider Inspection according to Gilb and Graham?

Speaker: I am familiar with the Inspection according to Gilb and Graham. Frankly I did not consider this method. The question should be rephrased as
“Would you choose Inspection according to Gilb and Graham?”.
Looking backwards it is too far fetched. The people should receive proper training and there was just a block of few hours. Another disturbing element is mentioning the most biggest issues first. This can lead to a lot browsing forward and backward through the deployment plan. This can be quite disturbing.

Facilitator: Number 27, you can ask your question.

Attendee number 27: What was your role in the project?

Speaker: My role was a test coordinator.

Facilitator: I’ve got a yellow card from number 68. Number 68.

Attendee number 68: Why did you call for this meeting? It is not your task.

Speaker: I thought, that it was important. The next step is to make things happen: I planned in the meeting and I became the chairman.

Facilitator: There are no more yellow cards for this question on the stack. So we move on the next green card. Number 38.

Attendee number 38: Did the suppliers provide any deployment plans?

Speaker: All the suppliers provided deployment plans.

Attendee no 38: This looks like a time consuming operation. Was there any reluctance?

Speaker: One supplier did not see the benefits at first. Then he made a Deployment Plan after some talking.

Facilitator: At the moment I’ve got one green card from number 23. Number 23.

Attendee no 23: why did you need a deployment plan?

Speaker: I asked my test team the same question. One of the testers told me, that experience taught, that these plans were necessary. A few months before I personally witnessed a rollback.

Facilitator: we have a red card. Number 3.

Attendee no 3: What is a rollback?

Speaker: A rollback is, when the backup is restored. In this particular case also the old system was reinstalled.

Facilitator: we have a yellow card. Is it about the rollback? Okay. Number 17 go ahead.

Attendee no 17: Do you need to test it? The system, which was rolled back.

Speaker: Of course

Facilitator: There are no more yellow cards on the stack. I’ve got green cards from 54, 65, and 78. So number 54, you can ask your question.

Attendee no 54: Which format did you use for the Deployment Plan?

Speaker: I asked and got permission from one of the suppliers to use their Deployment Plan as a starting point. The advantage was, that it was familiar to the employees of this supplier.

Facilitator: I’ve got green cards from 65 and 78. So number 65.

Attendee no 65: Why do you call it an emergency? Nobody got hurt.

Speaker: How do you call a situation with a person cutting someone’s tent? And what would happen, if this person is caught in the act?
How do you call a situation with a system, which cannot be used right after the deployment?

Attendee no 65: [nods]

Facilitator: I’ve got green cards from numbers 78, 95 and 24. Number 78, you can ask your question.

Attendee no 78: Looking at your technical background it seems easy to be a chairman. Do you know everything?

Speaker: I do not know everything. I cannot know everything.

Attendee no 78: Did you not feel vulnerable?

Speaker: At certain points of the meeting I was vulnerable. Quite vulnerable. But I was also confident, that we could make a deployment plan as a group. Sometimes I had to ask for support and I got it.

Facilitator: No yellow cards. Number 95.

Attendee no 95: So technical knowledge and experience are not necessary?

Speaker: The important thing is to have a safe environment. A place, where people can voice their thoughts.
In order to discuss all actions I chose a business way of meeting. Please stick to facts. And we’re all here to accomplish something like a group.
I watched for body language. If I was not sure, then I stated the action, looked to the person and became silent.

Facilitator: I’ve got green cards from numbers 24, 38, and 23. Number 24, you can ask your question.

Attendee no 24: You added a new blog category: A leader ships. Did you ship? A Deployment Plan is just an artifact.

Speaker: I once read something along the line like System must solve the problem. If the deployment is bad, even the best system cannot solve a problem.

Facilitator: I’ve got green cards from numbers 38 and 23. Number 38, you can ask your question.

Attendee no 38: What have juggling and testing in common? You are talking about a hobby and job. These are two separate things for me.

Speaker: I have question in return: would you please summarise both stories in 4 words?

Attendee no 38: What about: good planning withstands emergency.

Speaker: So you plan the emergency?

Attendee no 38: I need some What If Scenarios, if things go wrong.

Speaker: So you want to make a scenario for every possible situation like overloaded network, a comet paying a visit, etcetera. There are a lot of scenarios to ponder upon. I suggest: Plan to anticipate emergency. In this case: complete rollback.

[To be continued here.]

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.]

A look behind the scenes – In Runö

When I mentioned at Let’s Test Conference in  2015, that I came from the Netherlands, the following question was likely to be asked:
“Do you know Huib Schoots?”
My standard answer was:
“Yes. And he knows me.”

At Schiphol Airport in Amsterdam I was waiting to check in my suitcase. Behind my back I heard: “Hey ugly man” I turned around. Ready to confront this man. Huib was looking at me with his characteristic wide grin.

When I arrived at the belt to pick up my suitcase at Arlanda Airport, Huib was talking with Bill Matthews:
“Do you know him?”
“The juggler.”
Huub confirmed that with an
“A huh”.

Shifting gears

On Sunday May 24 I arrived for the Let’s Test conference in Runö. In the conference centre one of the first testers I talked to, was Henrik Andersson.
“You asked me to do an extra juggling workshop. When would you like me to give this workshop?”
“This evening would be great.”
I agreed. On Twitter I had already seen a suitcase of Paul Holland packed with games.

That evening I packed 6 devilsticks with 12 hand sticks. When I arrived at the hall, Henrik saw me. He smiled and gave a thumbs up. I chose the bar room, because there was a lot of traffic. The chance, that people would join me juggling, was great. Henrik joined in. Even a man with a ponytail started juggling. The following moment I noticed, that Michael Bolton was juggling with one of my devilsticks. I did not believe my eyes. I thought about one of my advices in my conference workshop:
Don’t fear your peer.

I was so focused on my workshop, that I forgot to exercise answering the standard questions like

  • What is the name of your company?
  • What kind of products or services does your firm offer?

I was completely in the presentation mode: I had not practiced my small talk English. The proper translation of the Dutch word patiënt is patient?!

Flirting with disaster

On Monday morning I could not sleep any more. It was the early sun rise. So I opened my laptop to add another bug for my exercise. For some reason testers like to find bugs. The modification went well. Within 30 minutes I had finished it and tested the program. The last thing, that I had to do, was uploading the file to a server. I opened a connection. I got confirmation, that the upload was successful followed by a cryptic message about a data connection. I looked on the server: the old file was removed and it was not replaced by the new one.

At that very moment I realised, that I had made a major error. I assumed, that the connection was safe. So I did not take any precautionary measures like renaming the file, which had to be removed. So I gave it another few tries to no avail. In plain English I had just ruined an exercise.

Then I looked on the internet. The plausible cause was the firewall of the hotel computer network, which did not support uploading files. So I used my smartphone (with a mobile provider) instead to upload the file and everything was all right at the end.

Speaker‘s Corner

After the Monday morning sessions I was tired. So I went to my hotel room and had a long nap. Then I returned to the main building. I saw Ruud Cox, who was listening to Huib Schoots. The latter was talking about the building blocks of his workshop the next day and the time estimates of these blocks.

During his workshop on Tuesday Huib said:
“I always ask feedback.” And
“Tell every day to a colleague, what you have done that day. ”
“If you cannot find someone, place a rubber duck on your desk and start talking.” 

So I went to an empty table. Then I noticed, that more speakers were gathered in the same room: Jean-Paul Varwijk, Joep Schuurkens, Michael Bolton, Laurent Bossavit (?). Probably improving their talks. I went through my slides of “What I learned from juggling as a tester” on my smart phone and juggled a little bit.

Sharing the fun

My facilitator was Duncan Nisbet. The familiar question popped up: “How shall I introduce you?”I mentioned 3 things, which should be included. Then I referred to this blog for additional information. Then Duncan introduced me as a “good storyteller”.

I had never told him a story before. I was just sharing some on this blog. Anyways … 

Then I started with a story about a boy missing a foot and most of his fingers, who wanted to learn juggling from me.

On my ride to Runö I was sharing a cab with Bill Matthews, Chris Grant, and Dan Billing. The latter said something about the inner tester. The following morning I knew I had the perfect example for a story. Just before the keynote of Ben Simo I asked Dan permission to use this single sentence in my workshop. He agreed. On the last evening of the conference I told him, how I used it. This lead to a wonderful conversation about “needs, values and relationships”.

There’s a mismatch

On one of my sheets I am wearing a dark and a white sock. Nobody mentioned it.  Maybe you do notice now.

On the other hand two unexpected bugs surfaced during my exercise: there was a huge error in a sentence. The second one was, that my exercise was not usable on an iPhone. I forgot the portability test.

Oops sorry

During my workshop Henrik Andersson had entered the room. I was so concentrated on my presentation, that it looked to me he appeared out of nothing. I started talking about discovering a juggling trick. On the sheet the following text was shown:
“Create a framework to correct errors”.

“I did not discover this trick [helicopter], because my framework was too strict.”
Then I apologised to Henrik:
“Yesterday evening I gave a workshop. Henrik Andersson was present.
[Turning my attention to Henrik] If you cannot learn the helicopter, it is, because I gave you a too rigid framework. So I apologise for this.”

A question, which back fired

I showed a sheet with frequently asked questions about juggling to the audience. One of the questions was: “Do you juggle with fire?” I repeated this question aloud, followed by:
“This question was asked right before this workshop.”
One of the delegates got a red face and laughed hard.

Thanks for the workshop

While I waited for my cab, Kristjan Uba came personally to me to thank me for the workshop. I recognised him, because the evening before he was intensely observing Tobias Fors (?) and me solving the dice game. This was hosted by Michael Bolton. Kristjan wanted to learn the finer details of coaching this game.

Trying to look friendly I searched my memory for this man. Luckily Kristjan helped me by telling about juggling the devilstick himself. Then I noticed the ponytail. It was the juggling workshop on Sunday evening. So I juggled with 2 famous testers and a speaker.