The task: explain what you do at work to a group of 6 years old kids.

Level: high (my own daughter was among the kids).


Many people shared their ideas of such “lectures” – you can find some really interesting examples on Stack Overflow (e.g. here). Many of them are based on the idea of presenting how computers are stupid and that you need to tell them very precisely what and how to do things to succeed. Fun guaranteed, but I seriously doubt if afterward kids understand anything about programming.

My ideas for a successful presentation were:

  • Keep them engaged by asking questions and drawing. The original drawings were pretty big (flipchart) and I draw them while talking – which BTW is a nice way to keep a young audience engaged (they had so much fun laughing at programmer straw man or pointing out that Peppa Pig doesn’t look like this, etc).  I do not have the original drawings (forgot to take pictures) but I draw them once again so you get the idea.
  • Build upon what they already know (YouTube, laptops, tablets, DVDs). Nowadays every kid watches cartoons on YouTube, plays games on tablets and observes mom or dad working on their laptops. They also know the movies are kept on CDs/DVDs and that the smartphones and tablets are pretty similar (when it comes to games and movies).

I started with the basic question “who knows what a programmer does?” I knew they had some discussion about this yesterday so I wasn’t surprised they had some idea. I gave them my own definition: “Programmer is someone who writes computer programs, who knows the languages used to tell the computer what it should do. A programmer knows a lot about computers.”

Then I draw a programmer at work.


The next step was to discuss computers. All kids started talking about laptops of their parents (it is really lovely how they mention the same thing over and over again). I interrupted after some time pointing to them that there are many computers in different places – like smartphones or watches, but also in cars and lifts. I draw each of the mentioned items and discussed in few words what a computer is used for in each case. I also asked them how they think the weather forecast works (one smart kid answer “the satellite knows what will be the weather next day”) and told them about computer calculating the prognosis based on data coming from thousand of measurement devices.


I wanted to move to computer programs next so I mentioned that computers do what they do thanks to the programs which instruct them to do certain things.

I moved to YouTube cause I knew they will know a lot about it. I started by drawing UI that they are all familiar with.

I asked how many movies there are on YouTube. Some of them were confused but few shouted “millions” or “infinity”. So I asked if it is possible that all the movies fit on one discs. Then I draw many discs and asked “how it happens that after you tell YouTube to watch certain episode of Peppa Pig it finds the right disc?”. They responded with silence so I draw a database and quickly described its role.


I wanted to give them some idea that what they see is only a tip of an iceberg and that the programmers are responsible for much more. I explained how we must take care of various stuff like:

  • protecting the movies against bad people (“what would happen if someone changed the database so that instead of Peppa Pig you would see some football match?” – answered with horror silence)
  • making backups (“what would happen one disc broke? then you would never be able to watch this Peppa Pig episode in which Daddy Pig tried to hang a picture?” – horror silence again)
  • so that YouTube works on different devices (smartphone, tablet, laptop)
  • presenting ads
  • counting the number of people watching each movie
  • showing thumbnails of similar movies, etc.

This was a good time to remind them that the programming is a teamwork. The programs are big and demand knowledge of different areas so that many people are involved in their creation. At this point, I updated the first drawing adding another programmer so that two were sitting close to each other.

The next topic was how computers work – very roughly of course. All I told them was that:

  • mouse and keyboard are for people to give commands to a computer
  • a computer screen is for computers to respond
  • inside every computer there is a processor (you can think of it as of a brain of the computer)
  • there is also some disk which allows computers to store information


I concentrated on processor telling them that it uses a funny language which consists only of zeros and ones. Then we had a bit of a fun when I pretended to talk in a language using only As and Bs. Then I explained that the programming languages used by programmers were created so that it is easier to talk with processors.

I followed with the simplest possible examples of programming languages statements (using some pseudocode). I wanted to show them some more but I felt they were losing their focus so I haven’t even presented the for loop.


To finish my lecture I draw once again symbols of what we talked about. I draw them one by one and asked questions like “what is this?”, “what do you remember about it?” and so on. It went pretty well.


Additional comments, do’s and don’ts, tips & tricks:

  • It was more fun than I expected! I treated this seriously and I was well prepared, and it paid off. The kids were interested and I think they might even remember something. :)
  • Drawing pictures is the right way to go. It grabs their attention and lets me remind them about things we have discussed few minutes ago by pointing to a certain drawing.
  • Be prepared for them repeating things over and over again. When I asked about languages they know then one guy raised his hand and said: “I know a little bit of English”. And then his colleague did the same. And then one more. And another. And then rest of the group joined one by one (or few at once). All saying exactly the same about English. It gets even more chaotic when you touch the subject they love like cartoons.
  • Some kids will get bored no matter what you do. Their attention span is simply too short.
  • Write carefully – e.g. they will protest when you write 1 so it looks like 7.
  • During the presentation I understood that there is no point in correcting them – for example, I think they understood that YouTube keeps cartoons on DVDs and when you ask for one then computer selects the right disc and plays it. I think this is perfectly fine. I wanted them to understand the concept (how the search looks like and what does a database do) and not the technical details. I feel this is the right way to go.
  • The presentation took me ~25 minutes. No sense to make it longer.

My findings from the 7th ACE! conference (Krakow, Poland).

They say that “When the student is ready, the teacher will appear.” So maybe I was ready, and ACE! appeared in the right moment to teach me a gazillion of things. Frankly, I can’t remember any other event that I finished with so many new pointers, new ideas, new things on my TODO list or inspiring quotes. I can’t possibly list them all here, but at least I will share some of them with you.

The order is pretty random. The quotes are not really quotes but close to it. :) Some things were never mentioned directly, but I read them (imagined them?) somewhere “between the lines”.

  • Naomi Ceder – Antipatterns for Diversity
    • Impossible to see a problem when you belong to the privileged group.
    • If you are privileged you find ways to justify that you belong there
    • Compliments are often nicely wrapped up stereotypes.
  • Shu Ha Ri – mentioned all over the place
  • Experiments – yes, you should
    • be really crazy about it: Popcorn Flow by Claudio Perrone 
    • you experiment more, you learn more, you learn faster, you outsmart your competition etc.
    • reminds me of Mngmt 3.0 Celebration Grid (silly name, BTW)
    • You should know what you expect, how you decide whether it was a victory or a failure.
    • If you are not ashamed with your first release, it means you waited too long. Claudio Perrone
  • You and your team are parts of the system. Complaining about the system is stupid, you are part of it, you can affect it, so work towards changing it.
  • Causal Loop Diagram,  Current Reality Tree, Cynefin
  • You can copy solution, but not the context (AKA, “we are not Spotify!”). Yeah, read what others do, be inspired, but find your own solutions. Your context is different.
  • Mary Poppendieck is awesome. Can’t get enough of her lectures. :)
    • on a downside, her workshop wasn’t a workshop but the continuation of keynote lecture
  • The process often stands in the way of a passionate team. Forget the process. Let them work independently. They will do great.
  • The art of scrum mastering / agile coach is to disappear.
  • A team should have a mission. Easy to say when you work for NASA Moon program. But what about a team that works for normal business? How to create an exiting motto for such a team? Maybe start small, with something different. Try to find (together) some working principles, identify team values, list things the team won’t tolerate.
  • Sketchnoting is not for me. Yes, I learned that I can draw a happy guy and a tired lady, and even a grandpa with mustache, but how on earth could I use it to make notes? You gotta be kidding me! (But I will show my new skills to my kids, and I bet they will appreciate!)
  • Thing is really done when:
  • Real options – delay the commitment
  • Do not start working on a story until you know how to measure its impact.
  • Creators should be immediately connected with what they create.
  • Put your money where your mouth is. E.g. do you promote kanban boards? Fine, so where is yours?
    • …ouch! where is mine?
  • Teams should solve problems, not deliver features.
  • PO – build a hypothesis, team – build and experiment ASAP.
  • Deploy (technical) and release (marketing) are different things. Feature toggles help.
  • Constraints can be pretty helpful, they help you to do only important work. (That is why I limited the time to write this blog post.)
  • Peer coaching (peer-feedback, peer-to-peer review) should be separated from promotions, salaries etc.
  • Do’s and don’ts when you attend a conference
    • Coaching sessions are a must.
      • BTW. There were coaching sessions with some great coaches and not all were taken. I don’t understand it. You prefer to see a presentation when you can have a 1on1 conversation about your issues/problems/situation with some Guru?!
    • Open Space discussions are great. Especially when the owner is prepared.
    • Don’t take a laptop with you. Don’t bother with tweets. Be there, listen, talk. Pen & paper will be enough.
    • The food at ACE! is delicious. Prepare a box next time, take some cookies home. 😉
    • Talk with people. Talk with the speakers. Talk. They won’t bite you.
    • Write a blog post right after the event is finished. Otherwise you will never do it. (Yeah, I did it!)

Recently I had an opportunity to meet some people working in big corporations. One of the things we discussed was role of leader/manager. They used the term “shit umbrella” to describe the role of such person. If you are unfamiliar with the term, here is the definition from urban dictionary:

It’s the unofficial title for the person/role above you at work, who takes the heat from management/owners.

This individual takes the shit, while the people below him/her are shielded from management’s crap, trouble, finger pointing, etc..

My view is different. While I agree with the idea of “protecting your people” I think that standing there with an umbrella is not good enough. There is more to be done. IMHO your task as a leader is to go up there and clean the mess so no more management’s crap happens again.

When I think about this, I think there are two major differences between me and my corpo colleagues. First of all, they perceive their organisation as something evil. Their teams, their departments are kind of surrounded by the armies of darkness (upper management) so it is only natural they want to defend their people. This is not my case – my organisation is not evil and there are no monsters outside my team’s room. I do not need to protect anyone.
Second, they do not believe they can change the way their organisation works. This thing is way too big, too rigid, too hierarchical (and has been like this for decades) to change anything. All they can do is to stand their ground and protect. And they do. They survive onslaught of stupid requests day after day. They are valiant and stubborn. On the contrary, my organisation is very small and it is still growing, evolving and changing every day. And we – me and all teammates – can influence the direction we grow. If we see bad things happen we can act and change them. This is how small size, trust and flat hierarchy (or almost no hierarchy at all) works.

So while I appreciate what my fellow corpo-leaders do for their teams, I wish they could do more for them.

All in all, lucky me. :)

The Internet is full of “10 Rules For Effective Meetings” blog posts so why not create my own? Sure, why not?

These are the guidelines I try to follow when organizing meetings. They work fine for me in the context of the company I work for (flat structure, ~80 people, no managers, no corpo-bullshit). I have no idea what happens if you apply them to your workplace (but I bet, it would be something positive).


Meetings People Love

Meetings People Love

A Meeting? Seriously?

Sometimes it is enough to visit your colleague in the next room, sometimes all you need is a short discussion on group chat with few people, sometimes simply wait till certain people are having coffee break and join them for a five minutes discussion.

Meeting is a heavy, time-consuming, corpo-smelling, commonly disliked thing – look for a lighter solution.

Save People’s Time

As an organizer make sure you do everything possible to save people’s time. This means you make sure that:

  • all important people will show up,
  • the room is ready (see below),
  • all participants  know what they should prepare for the meeting (if anything), and that they really did,
  • lead the meeting so that it is worth being there

One minute of your preparations can result in few minutes saved for each participant. Do the math.

Organize the Room

Always be there at least 5 minutes before the meeting. This gives you time to reorganize tables and chairs, tweak the air conditioning, bring missing markers, clean the whiteboard, check the projector works etc. Make sure the flip chart, markers, magnets, pencils, cards, or whatever else you gonna use is there.

They way the tables and chairs are organized is important. Make sure you know what type of meeting you want (a lecture? an open discussion?) and put the chairs so that people have no choice but sit according to your plan. If it doesn’t work just like that, ask people to rearrange so they sit the way you intended. Really, do it. If not, you will end up with weak discussion only because people sit side by side and can’t really talk to each other. Or you will have two hostile tribes on two other sides of the table. And it will be your fault.

Action Points

A meeting without Action Points (AP) is a waste of time. Make sure everyone knows what was decided (remind them right before the end of the meeting). Every AP should have an owner. For every AP it should be clear what the next step is, and when this next step should be finished.

Meeting Notes

Keep them short – usually the APs is all that matters. Add pictures of whiteboards notes, sketches, diagrams etc. – a good reminder of what happened during the meeting.

Send the notes ASAP (to all interested parties) after the meeting is finished.

Make Fun of It

If possible make some fun around the meeting. Yes, do it. The invitation can be funny or you can put some funny accents into the meeting notes. I’m trying to do it for (some) meetings I run at Codewise and I think it works. From discussions with my colleagues I suspect some of them take look at the notes because they want to find out what kind of stupid stuff I put there among serious notes. Good! – at least they will scan through the notes looking for hidden gems and will inhale some of the essence (if they want it or not).

I will give you one example of what I’m talking about. This is an email invitation to developers to take part in our weekly “devs meeting” – which is a gathering of interested individuals from each development team to share business and technology news. So usually the invitation email is “standard”, but from time to time, I try to tweak it a little bit. For example, like this:


Facts First

For problem-solving meetings always start with the facts. Even if you think people know the full picture. They usually don’t. It is your task to learn about it before the meeting, and then present it in a concise way. Or – even better – ask the participants to list them. If not, you risk all kind of misunderstandings (like people discussing different issues, while thinking they all talk about the same).

OK, here comes a story. So once upon a time we had this meeting. And I explicitly asked participants beforehand to prepare a list of facts so we start discussion with them. Once the meeting started one person gave like one fact and immediately followed with a general solution, which, in his opinion, solved all problems related to the discussed topic! I stopped him in the middle of a sentence and refused to discuss the solution until we learn about the whole picture. We continued with the facts and listed 12 of them on a whiteboard. After 30 minutes of a discussion we agreed on some action points. The solutions we discovered were completely different from what the first guy suggested. I would also say they were much better. Can you guess why?

Do Not Distract People

Do not turn on the projector too early, and make sure you switch it off when it is not needed anymore. For some reason, people will stare at the screen even if nothing happens there (instead taking part in the discussion).

Switch off all communicators/calendar reminders when presenting. First, it distracts people. Second, it can be pretty embarrassing. :)


For problem-solving meetings always leave the door open. Invite crucial people and let other know that such and such meeting will be held. And don’t worry – only few (if any!) will come. But those who decide to join you will probably have something interesting to say. Good for you, right?

Similarly, publish the notes so that all employees can read them. You have nothing to hide, do you?

As Attendee

  • Come prepared. If asked to read something, read it. If asked to think about some idea beforehand, think about the idea. Simple, isn’t it?
  • Don’t attend a meeting if you do not feel like going there. Your absent-presence won’t help anyone.
  • Think about other people who could help and discuss inviting them with the meeting host.
  • Always inform the organizers if you attend or not. A simple click in the calendar is all they need – and it really helps them to prepare a meeting.

Tips & Tricks

  • If we chit-chat instead of discussing it means the meeting is over. Finish it.
  • For recurring meetings, change the meeting host once in a while. It helps to fight the boredom.
  • Throw away empty markers immediately. Have no mercy!

Ending Quote

For all programmers out there, who love all kind of meetings :)


During the Unexpected Meetup: 1st Open Space I had an opportunity to discuss the topic of changes with fellow Scrum Masters / Team Leads / Agile Coaches. Here are some notes (subjective and incomplete):

  • Books to read:
    • Our Iceberg Is Melting
    • More Fearless Change
  • You shouldn’t expect that your team will come with new change proposal every day. It will be rather your task to help them to discover that some changes are required and decide that they are worth the effort.
  • External experts can really make a difference. Somehow people from the same company are less credible (“No prophet is accepted in his own country’)
    • New hires – especially if they are seniors – are treated similarly to external experts. At least for some time.
  • Imposed changes are much less effective than grassroot changes.
  • No sense to order changes (e.g. “you will do the pair programming 100% of time starting today!”). Much better is to show the idea and let people use it at their own will.
    • Onboarding (especially with fresh devs) is a great time to inject some desirable behaviours.
  • A nice way to introduce a change is to run an experiment (e.g. “Let us do the pair programming 1 hour per day for 2 weeks. Then we decide whether we like it or not”.) Be prepared that people might not like the change. But this is fine.


I was addicted to email checking. Or maybe I should say that I still am the same way an alcoholic doesn’t stop being alcoholic, he merely doesn’t drink anymore. So let me say I’m still emailoholic who checks email in controlled manner. Or at least, one who tries to achieve the inbox zero.

Checking email often was exhausting, pointless and stupid. I didn’t like it, so I decided to put an end to this bad habit. In fact, there were two goals I wanted to achieve:

  1. stop checking my email account too often,
  2. don’t let the unanswered emails pile up in my Inbox.

Interestingly these 2 things come together – at least for me. The thing is, that I used to check my email when I had no time to handle it. This had two very negative effects. The first, and an obvious one is, that I was thinking about answering my emails right after I checked my mail account. This disrupted my work, family life or whatever else I was doing at the moment. The second, less obvious effect is, that sometimes I hadn’t answered to emails at all (or I did this after very long time). This one is harder to explain, but my theory (uh-oh, big word!) is the following. There seems to be a certain good time for some things. A book should be read right after you buy it. If you don’t start reading it immediately, you probably won’t read it at all. Similarly, an email should be answered right after you see it.

So, in order to improve the situation I took one resolution: I will check my email only if I have time to process it right away. This means saying no to:

  • email checking while my code compiles,
  • grabbing tablet on my way from dining room to the kitchen only to check my email and put down the tablet on the table,
  • no quick checks in between other activities.

I started with the cleaning of my inbox. This wasn’t very hard, I had like ~40 emails there. Then I removed pinned tabs from my browsers. And hid the email icon from the front page of my tablet and phone.

Since 2 weeks I check email rarely (compared to what I used to do) – sometimes only once a day, sometimes few times a day, but the important thing is, that every time I do this, I make sure my inbox is empty before I switch to other tasks.


There are some issues, though. First of all, my email is also my personal database of various things. Sometimes I need to look there searching for something. To do it, I need to break my promise and take a look at email, even if I do not have time to clean it. Secondly, sometimes I have time to process email, but for some reasons I can’t – e.g. I need to consult something with my wife before answering, or I need to check something at home before I answer. Fortunately, neither of these happen often. Another issue, is that sometimes I wait for an email answer which I need ASAP – e.g. will I meet with X today or not? Then it is hard not to check my email every 30 minutes or so.

But all in all, it works pretty good for me. I’m not so obsessed with my email anymore. People who contact me by email should be also happier as they receive answers much faster than previously. I enjoy email-free evenings, and email-free-thoughts. My inbox is often at zero, and I hope to keep it this way.

Some time later

After 2 weeks – To get rid of unwanted emails I spent some time signing off from all kind of customer survey etc. This takes time (usually you need to log in to change your notification preferences) but I believe it is worth the trouble when thinking in the long term.

After 2 months – It is much easier (at least for me) to keep inbox at zero than to restrain myself from constant email checking!

After 2,5 months – I have never checked my email using phone or tablet. Yes!

After 3,5 months – Block site helps to fight the urge to check my email often. Not ideal, but helps.

I performed a Journey Lines team building activity (as described by Lyssa Adkins) with various teams. In general, I was really happy how it went (and so were my colleagues).

The idea of Journey Lines is that each of the participants draws a line showing ups and downs of previous jobs. Each chart contains also some additional information like technologies used, skills acquired, names of companies they worked for, or any other comments that people find important. This activity:

fosters self-organization and cross-functional behavior because it reveals a person’s skills, experiences, background, etc. This way, the rest of the team knows what this person “brings to the party.”

Some observations:

  • Some people need to check LinkedIn to help them remember all the places they used to work (especially freelancers with short-term contracts really need such reminders),
  • The time required to tell the story differs – some people needed 6 minutes, for others even 15 seemed to be not enough (next time I will probably put some time constraints). The whole exercise took an hour (for 4 people team) and more than 2 hours for 8 people (including 15 minutes pizza break).
  • Even though this activity is intended to be used when forming a team, we played it a long time after the team was created and it was also fun & informative. Team members learned a lot about each other, even though they worked together for a long time already.
  • Personal things (marriages, kids) showed up rarely.
  • It was very interested to see how many different ways lead us to this particular company that we work for now. Also, it was funny to notice that in the past we all went through similar stages (e.g. freelancing during high school, hacking games etc.).
  • Some people draw really beautiful charts with nice fonts and additional drawings.
  • There was a lot of new things about each team member that no one knew before.

Probably the most interesting for me was to learn about the “down” moments (where the line of journey went down, down, down – often very abruptly and usually resulted in job change). There were few reasons for this:

  • people issues – stupid team lead / manager / boss can ruin even the best place,
  • stagnation – nothing new? maintenance and bug fixes for too long? people will look for a different place to work,
  • people leave their jobs when put in a position they did not want (e.g. someone was appointed a PM, another dev ended doing some office-management tasks).
  • a lack of vision (“why are we doing this?”) or lack of business impact (“we did it, but then they started to argue if they really need it, and it never went to production”) is a serious motivation killer

One more thing. I like this activity because it creates a symmetrical situation – “I show you mine, you show me yours”. Also, each participant can decide how much he wants to reveal. The only potentially intimidating thing is that at some point you need to stand in front of your colleagues and tell your story. But somehow, it hasn’t been an issue for any of devs I worked with.

P.S. Ask participants to write neatly on their charts so that later all can read it! :)

It is almost the end of January, but I believe it is still a good time to make some New Year’s resolutions. Today I want to describe one of mine, which I believe could be a good fit for many of us.

As you know, it is very simple to make resolutions but much harder to fulfill them. So before I reveal it, let me tell you why I believe I will keep it:

  • it is not hard to do,
  • no special equipment/weather/mood required,
  • doesn’t take much time
  • requires only a little bit of preparation
  • I have heard many people saying it is a very valuable habit
and last but not least:
  • I have first started doing it and I already like it (and only later decided to make it my resolution – usually first you take a resolution and then you start).

And the resolution itself is very, very simple: I decided to perform a short (5-10 minutes) retrospective of my work achievements each week. Have I done what I promised (to myself or to others)? Have I worked on really important stuff or maybe I spent my time doing 2nd rate stuff? Have I started new tasks without closing the older ones? And so on.

In order to be able to do that, I take notes every day before leaving the office: few bullet points with major things I have been busy with. Then, on Fridays (I set up a reminder so I don’t forget it) I go through the notes from the last wee and ask myself questions. And then I write down some TODOs – like “do X – don’t wait any longer” – but also I praise myself – e.g. “good job with Y!”.

After three weeks I already have few observations and ideas:
  • Maybe Monday would be better, so my TODO list was kind of fresh and I would be able to jump into the action without waiting for the weekend to pass.
  • Why only work achievements? Why not introduce the same idea to my family life?
  • A week is kind of long, at least in some cases. Wouldn’t it be better to have it twice a week or daily to shorten the feedback loop? I’m not sure.
  • I do not have a good way of reminding me about the TODOs I created during the review. A sticker on the monitor doesn’t work for me – somehow after an hour it is like I don’t notice it anymore. Maybe I should set up a reminder for this as well so e.g. every day I got reminded about things I decided to do?
  • I have already been able to achieve some small victories (e.g. doing some stuff I have been putting off for weeks…) so I can say it works for me. So I plan to continue.
There is still time to change this year into something more valuable. Why don’t you give a try to this self-retro idea? I hope it helps you.


Few months ago I published a list of books that I really, really wanted to read in 2015. 2015 is finished so I can now tell you how it went.

…and there isn’t much I can be proud of. Out of the 14 books I read.. well… around 3. Not exactly 3 because in fact I read 2 books and also halves of another 2 books. At first I was really disappointed when I realized this. But after some thinking, it doesn’t look so bad any more.

  • The list was published end of May 2015, which gave me only 7 month and not the whole year. Still the 3/14 ratio sucks big time.
  • I have read few books outside the list. Apparently, new topics (e.g. user stories) got my attention in 2015 and I decided to devote more time to them .
  • I have read numerous blog posts and watched many online presentations. It seems much easier to read/watch them than read a book. You can read a blog post during a short break but you can’t (or at least I can’t) read a book like this.
  • The books on my list were mostly about “background” stuff – things which aren’t urgent but crucial in the long term (think Eisenhower method important and not-urgent tasks). It is OK I haven’t read them all as long as I go back and pick one from time to time.

Now, what has it thought me?

  • Long list of books “to read in the nearest future” doesn’t work. I still have a list of “books I want to read one day” (and it is always growing and rarely shrinking) but I do not fool myself into thinking that I will eventually read all of them.
  • Sometimes reading a book is a waste of time – it is enough to read what others have learned from it (at this point it is hard not to mention Pierre Bayard’s “How to Talk About Books You Haven’t Read”)
  • I have very limited time for reading books. I should pick them wisely so I do not waste it.

I will end my today’s mumblings with the quote of Stanisław Lem:

“No one reads;

if someone does read, he doesn’t understand;

if he understands, he immediately forgets.”

Enjoy reading, folks! :)

One year ago I blogged about a game we played during retrospecitve. A year has passed and it was time to open this “time-capsule”. No one guessed the right answer to all 13 questions, but some people were pretty close on many of them. Some questions got kind of outdated – e.g. we asked about the number of traffic-handling servers but in the meantime this functionality was split in two.

We liked the idea so this year we played it once again. The questions were similar to the previous ones but we tweaked them a little bit. Also, we invited our account managers to join the fun so the number of players grew to 14 (last year it was devs-only event, and there was only 9 of us).

P.S. Some people decided it would be fun to play it at company level so we prepared 5 questions and played the “New Year Predictions game” together. Will see what 2016 brings!