maker faire and heat plan

Is there something with every other year and Maker Faire weather. In 2013, we exercised our rain plan and had a giant goldfish bowl of rain! In 2015, we used our rain plan again. Last year, it rained overnight, but not during the event. This year in 2017, I was excited about the weather. It was going to be shorts weather with not a cloud in the sky.

Turns out there’s a downside to that. It was too hot for the robots. On Saturday, the robots started overheating and we were caught by surprise. The RoboTigers made a sunhat for their robot:

On Sunday, we let the teams know what to expect. In particular to make sure the robots took breaks in the shade and not just the humans. The problem was there wasn’t much shade. So I made some with tablecloths. Elegant looking robots:

The Brooklyn Blacksmiths needed to cover a part of the robot so the motor didn’t overheat when running. They had a work glove around so added that. Then the robot became a high five robot!

We also brought a water cooler that we kept refilling so water was handy. Finally, when people around us left early, we expanded into their space. Good for us to have more space. And good for Maker Faire to not have that gap.

And we won a ribbon. In shorts and all!

Using Agile Games to improve meetings – the virtual/remote edition

This evening, I went to the NY Scrum User Group where the topic was “Using Agile Games to improve meetings”.

As the presenters went through the games, I thought about how they could be adapted for a virtual/remote team. I spoke about Virtual Scrum last year at a Birds of a Feather session. I’m doing a presentation/breakout session at Spring One on the same topic this year and looking forward to adding an agile game or two that applies to remote teams!

In thinking of remote equivalents, I wanted to preserve the sense of fun along with the message/goal of the game. Here’s how that went.

Story Cube

The Story Cube game involves rolling dice and talking about feelings based on the dice. For more, see this Story Cubes description. The only part of this that is physical is the dice.

As a remote alternative, I thought about having pictures with each of the images and using a randomizer to display some on screen. Then the talking would proceed the same as if the images are on the table.

Dana Pylayeva (one of the presenters) noted there is a phone app if you want to spend $2. (That’s a lot cheaper than the physical dice by the way.) We searched for it during the meeting and found Rory’s Story Cube app. Looks cute. With the app, you’d need one per site.

Feelings Game

The Feelings Game involves physical EMO cards with feelings listed on them. Each feeling has a number next to it. In response to a prompt, each person writes the number of a feeling on a post it. The post its are randomized then the group discusses. For more, see this Feelings Game description.

This time there are two parts to make remote. The feeling cards part is easy. You make a web page/powerpoint slide having a table with numbers and feelings listed. Or you have each site print a copy. Or you buy a set of cards for each site.

Then you need a way to anonymously share the number everyone chose. There are a number of online shared whiteboarding services. I like web whiteboard because you don’t even need to login to use it. What’s more anonymous than a site you can use anonymously! (you likely don’t want to use google docs or one note because either the author is tracked or the perception is that it is)

Fist of Five

Fist of five is a survey technique where everyone holds one to five fingers up at the same time. For more, see this Fist of Five description.

This is really easy to make remote. My team does “finger voting” frequently. Especially at sprint planning. We do thumbs up/side/down voting. We do story point estimate voting. (When we were a collocated team, we used planning poker estimating cards. When we became a distributed team, we used pointing poker for a while. Then we had a retrospective suggestion to use our fingers instead and it took.) We do voting from a multiple choice list to see what people think of design tradeoffs.

Anyway, finger voting is easy over video conference/Google hangout/etc as you see each other. if you can’t see each other, pointing poker is good for voting. You can set it up to use any options you want. So you can choose the numbers 1 through 5 instead of estimates and you have fist of five.

Ehab El-Badry shared with me this anonymous fist of five tool. Nice!

My Right and Mrs Right

In this game, the facilitator reads a story and the team passes legos left and right when they hear “right” or “left” in the story. Those words come up a lot. I couldn’t find the exact story used at the meetup, but a similar story is here. Then she asked questions about the story. And we hardly listened because so fixated on the legos. (It was also more complicated because she had everyone holding two legos and changing hands in addition to passing them. I think this was to make the task harder.)

Clearly we aren’t passing legos around remotely. But I think any sufficiently complicated task would work and have the same effect. It loses a tiny bit of the team bonding but that wasn’t the main point of this learning game; it’s about the shared knowledge/reference for why multi tasking doesn’t work. Ideas of remote friendly tasks to replace the passing of legos in a circle:

  • Put a paper clip in the left or right pile when you hear those words
  • Count the number of times left or right comes up (this might be too easy)
  • Count how many words are mentioned that contain three letters

Beautiful meadow

There’s lots of physical objects in this drawing game. There is a large paper, multiple colors of markers and a page of requirements. For the details/text of the game, see this beautiful meadow description.

We clearly need a shared document tool for this. We could use web whiteboard. For this game, there is no need to be anonymous so Google docs, OneNote or your favorite collaborative editing tool works. After splitting up the different groups into different shared document URLs, the moderator would drop the instructions into each board and keep time. Participants would have to be instructed to only communicate through the shared doc – no IM! But other than that, it’s equivalent.

Clapping/Raising hands

This was an unofficial game. “If you hear me, clap once” or raising hands to get everyone quiet. These work through phone or video chat respectively.

WIP Game

I can’t find an online reference for this game, but it is easy to explain. Half the group tries to write “I must limit work in progress” five times as sentences. The other half does the same but by writing “I” five times then “must” five times then, well you get the idea. About halfway through the time it would take to do this, the group is interrupted becuase the project ran out of budget and figures out who can deliver full sentences.

The only thing to change for remotes is to determine who uses which approach. Physical colored cards don’t work. But counting off or a random number or anything else to split up the two halves works.


An object forms the center of the room. Then questions are asked and people move closer or further away. For more, see this Constellations description.

I’d make this remote by using a collaborative editing tool like web whiteboard, Google docs or OneNote. I’d either put an image on the center of the whiteboard or draw a giant dartboard. Then I’d give people a color to use to represent them or type their initials in the spot where they would “stand”


I can’t find an online reference for this game, so I’ll describe it. We stood in pairs in front of colored pairs. We spent a minute talking about what we learned and then moved X spaces.

I think this is the most challenging to make remote friendly, but it is still possible.  At the beginning, have everyone pick a number. Randomly or by choice. Then have #1 and #2 chat, #3 and #4 chat, etc. After a minute, have the numbers shift.


Being on a remote/virtual team often requires a little imagination. But it’s fun. And easier than you might expect to adapt to.

setup for HOL-1695 – Starting Out with JUnit 5 at JavaOne

I’ll be leading a hands on lab “Starting Out with JUnit 5” at JavaOne. This is a BYOL (bring your own laptop) lab.

In order to follow the lab, you’ll need either a recent Eclipse or IntelliJ. Or you can use the command line and your favorite editor if you usually code that way. If you aren’t very familiar with IntelliJ, I recommend using Eclipse. Both lab instructors use Eclipse primarily so we will be able to help you more that with IntelliJ.

If you run into any trouble setting up for the lab, you can post a comment on this blog post or start a thread in the Testing or IDEs forum at CodeRanch.

(NetBeans does not yet support JUnit 5 which is why it isn’t an option)

Option 1: Eclipse

  1. Download and install Eclipse Oxygen
  2. From Eclipse marketplace, install the JUnit 5 beta support.

Option 2: IntelliJ

  1. Download and install IntelliJ  2017.2.1 or later. (2016.2 or later will probably work, but I haven’t tested). JUnit 5 is included.

Option 3: Maven and your choice of Java editor

  1. Install Maven if you don’t already have it.
  2. Make sure you are using Java 8. (This lab was not tested with Java 9).
  3. Your favorite Java editor is presumably already installed :).

Optional – Git

  • One of the steps will be to pull code from git. If you have a git command line (or git bash), this is a one line operation. If not, you’ll be able to download a zip file from github so this isn’t a hard requirement.