So, everybody is complaining about online meetings, I've posted my presentations and board templates already, but one thing that people neglect is icebreakers.
People think that because these are internal meetings, that icebreakers are not required, after all, well know all know each other.
However, the point of icebreakers is not necessarily to get to know each other, but get everyone loosed up and talking.
My favourite icebreaker of all time is Agile Faces, one that I picked up with @RedHatLabs, however this one is hard to do for remote meetings, and takes a bit of time.
I needed something that I could start almost every meeting with, and that anyone could facilitate.
So I settled on, the candy game, here is an description from FunRetrospectives:
The game is simple, you have a list of questions, each with a colour, and ajar of candies. Participants take a random candy, and then answer the question with the same colour
We use @discord as our remote office, so I created a `!candy` macro with the DiceParser bot, so that participants can chose a virtual candy and get the colour.
Every week I add a card with new questions, here is this weeks:
So, what makes a good question?
The point is not really the answers or facts presented, the point is to get the person talking.
So making the question should not be approached as "what do I want to know about my colleagues" but rather "how can I get my colleagues talking"
So, I made a poll (using modernballots.com) where my team could rate the questions we have used so far to understand what people enjoyed most.
The number one rated questions was:
This has the elements of a great question, there is no good or bad answer, no correct answer, it's open ended and encourages role play, and the rest of the team can easily join in.
Similar questions where also highly rated.
Food related questions tended to do well too:
The lowest rated questions was this one.
Why is this a bad question? Because it asks the person to remember and recount a fact, rather than just improvise and role play. If nothing comes to mind, they are kind of on the spot.
Starting your meetings with the candy game is a great way to build a creative and fun mood, make sure every talks, and takes only a few minutes to do. It works great for remote meetings.
Here are some more highly rated questions:
Are you doing anything to get your meetings started in an effective and engaging way? I would love to hear about it!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
We did our next loglines session at @TerminusDB, since we're almost done with Episode 4, we did the next iteration of planning, refining the requirements for Episode 5 and breaking them down as Spoiler Titles for our backlogs.
Our board looks quite messy, but this is actually a sign of maturity, since we "know the drill" thus our @MURAL kind of looks like our walls would if this was an in-person workshops. Not as perfectly curated as recent online sessions that require more perscriptive facilitation
I come across the advice to have a "camera on" rule for online meetings all the time. I really dislike this rule.
Cameras have their place, but the idea that you can effectively measure engagement via the camera isn't true. Measure engagement by *participation* not surveillance
There are many reasons to not use a camera, but to me the most import is that you should be using real-time tools like @MURAL or @milanoteapp to collaborate, and I would rather have the participant's eyes on these these tools, rather than on the video gallery.
Physiologically video exacerbates "Zoom Fatigue" as your brain works overtime to identify non-verbal communication in the tiny video frames. It doesn't work, and it's exhausting.
who wants to start an online tech conference in an old-skool text MOO?
At @TerminusDB we just did on online conference, there was a lot that was cool about, like virtual booths, etc, but the tech was cumbersome, weird web 3d stuff, the awful go to meeting and crappy slack channels. Made me remember building cool stuff back on ChibaMOO
With emoji's and links, a MOO based conference could be dope. This seems to be the most update LambdaMOO decedent: github.com/lisdude/toasts…
Using loglines as a format works very well for design because it encourages a user-centric view with a protagonist, a goal and an obstacle, and of course fits nicely with our "spoiler titles" style of backlog item writing.
We can chose which of these we want to move forward with.
This technique really works, here is how to run your own.
1. Create a list of "how might we" questions for your brainstorming.
2. Create a shared digital board of some sort, @MURAL , @MiroHQ, or whatever, create headings with your questions so people can put stickies under them
Managing Databases in a CI/CD pipeline is a nightmare. Migration scripts are better than making changes on running servers, but become hard to manage in complex modern pipelines.
Truly solving the problems requires revision control for databases so that you can clone, branch and merge your database.
Devs have it pretty good these days.
With Git, CI/CD, Infrastructure as Code, and the Public Cloud, you can have an idea in the shower, write some code after breakfast, commit to git and start collaborating with colleagues after lunch.