Korean Baseball is awesome (+ tv appearance)

watching the game

Baseball is insanely popular in Korea. We were fortunate enough to score some tickets for a particular exciting game in the season (the local Hanwha Eagles #6 vs. the Samsung Lions #1). For a Dutchy this was all new for me and I have to say that I really liked the game vibe, atmosphere and food*.

Suddenly we were approached for an interview right at the break of the fifth inning. I got a bit nervous when she mentioned it would be a live (but scripted) interview during break time. 

So there we were, taken backstage and up to the reporter areas. The 30 second interview was about our family and asked why we came to Korea (obviously for this particular game), and what dutch people think about Korean baseball. Ofcourse we also did a little cheer for the local team. So I’m a proud father of a eight month old daughter who made an appearance on Korean tv!

After a bad start of the match Hanwa (#6 in competition) actually beat the #1 in the competition; The stadium exploded with cheer. We got a signed baseball too!

All and all: We had a great day!

cmb2 hanwha daejeon suna dorresteijn
*Koreans shout ‘FIGHTING!’ to cheer someone or a team on. In terms of food, Chimek is great at sports events; CHIcken and MEKchu (beer); Basically KFC style crispy chicken with hot sauce and a cold beverage, what a combo!

No more traffic jams

van

When we moved to the Netherlands, I lived in my hometown (center of the country) close to my family and work.

However, my job happened to move to the headquarters in the ‘big’ city. Fine, I thought, I’ll drive. However, I then spent the better part of my week (12%) driving to my office and back. Listening to podcasts and audiobooks did cure the pain a bit, but it was a time waster.

I’m happy that my wife agreed to move closer to our office and last weekend we made the move! Now I’m enjoying short travel times and no more stress about traffic jams, life is good!

Creating psychedelic art with deep dream

A few days ago, Google released a Python Notebook to let you play with their very recent work on visualization with neural networks, turning buildings into acid trips and landscapes into Magic Eye pictures. They published their code publicly for everyone to play with.

After I found a docker image I was able to play with the notebook. Holy cow! I put a picture of me with my daughter that transformed us to someones nightmare in a few minutes; eyes popped up everywhere and I started seeing people behind us. So I moved on to objects and buildings; here is a picture of my office. (clickable)

inception

 

On the left you see the regular picture, next to that you can see the image which had a 7 time inception with the neural network which creates a lot of artifacts, just look what is haning on the roof; On the right an artists approach can be seen where a zoom is applied on the regular image.

After that I played with pictures of clouds and natural items; I found that the engine really goes wild with trees. Checkout this picture I took in Korea:

korea_deepdream_bl

Ok that’s enough trippy pictures for one evening; If you are interested how it works, read at this google blogpost.

 

 

 

Quad racing and Hummer driving with Sanoma

quadhummer

Whilst planning the Sanoma tech* outing, I pitched canoeing as a nice outdoor activity. My idea was refuted as soon as we found actionplanet; Offering quad racing and landrover and hummer driving, followed with a nice barbeque! Needless to say, it was an amazing event and I think the entire crew had fun. Hope we can make this an annual event!

* all the developers of websites like nu.nl, startpagina.nl, kieskeurig.nl, autotrader and yours truly with the Disney and tina titles!

In the DonaldDuck

joop

Working at the Kids and Teens department is always interesting; The editors and the drawers of DonaldDuck get their jokes and inspiration from all sorts of places, even around the office. They ‘used’ me to make a character in an actual duck story; I’m a geeky guy who drives around a celebrity – how cool is that! If you want to read it, get a copy of the latest TrosKompas!

Mont Ventoux, je ne suis pas fou

mont_ventoux_johan_joop_dorresteijn

If you wanted to watch the Tour de France in the 70s, you had it rough, it was a daily 20 min B&W summary filmed from a single angle. However, my dad did become an avid fan and took up cycling himself. Together with his friends they climbed the famous mountains like Alpe d’Huez, Col de la Madeleine and the steep Mont Ventoux themselves. Their sport bonded the group and they are cycling together to this day.

Moving on to may 2015, my dad was picking a cottage for our yearly family get-together, unsurprisingly he picked one at the foot of that very Mont Ventoux. Our whole family took the opportunity and enjoyed surprisingly good weather, French baguettes and French wine. Then my dad asked me if I wanted to join him up the mountain; I had to consider, I cycled up Col de Madelaine in 2004 but I am totally untrained at the moment. I agreed to a small ascend to halfway point as a first training.

We started off and I felt pretty great, the mood was good, lot’s of “bonjours”, waves and there was an American girl cheering us on and offering cold beverages, that was fantastic! With the 7~10% climb I was cranking energy fast but all was good… until a man dressed like Lance Armstrong rode by and called me to my place “hey, c’est la folie, you are crazy” and carried on*.  I yelled something back – too little too late – but actually found a renewed strength; “I’ll show him!” After a good hour we left the forest and we could see the moon-like summit. Breathtaking.

At halfway point I told my dad I wanted to keep on going, as the weather was exceptionally cold that day. But actually, being there with my dad really kept my nose to the grindstone and I didn’t want to let him down. Then I hit my limit. Closer to the top, I got into trouble but I made it! Thanks to my dad staying by my side and motivating me. A lovely Dutch woman with a SLR camera snapped my last meters, seen in the shot above.

At the top, we cheered, took some photos and had a cold drink. Then we turned around and breezing off the mountain, I was carrying such a big smile that I felt embarrassed for the people still climbing but I couldn’t stop. It was an absolutely perfect day.

*note: I did carry a helmet but only wore it during the descent; it was a remark regarding my endurance or my bike. Also; Generally French people are nice!

Real life Nintendo duckhunt

My uncles treated us on Skeet shooting in the far south of the Netherlands today. At the Eric Swinkels track. Having never shot anything in my life, this was a new experience. A loud bang and some feedback from the shotgun. Not sure if I will do it again but it was an interesting experience!
kleduivenschieten

At Sanoma Kids & Teens; a Scrum update

Scrum_training

I made a move within Sanoma from Comparison to the ‘Kids & Teens‘ cluster at the start of the year, and am surrounded with Disney characters ever since! This cluster has a solid foundation, based on traditional publishing since 1951. (the year the first donalduck magazine was published), and is expanding through digital business models currently.

Finishing a title called ‘duckworld.com’ (more on this in a month or so), a touch typing course at ducktypen.nl (Polish version coming soon!) and maintain various content and e-commerce sites like fashionista.nl, donaldduck.nl and duckstadshop.nl.

We setup a development team working scrum at the start of the year. Three months in, to raise awareness throughout the cluster, we’ve organized a day-long scrum training with Zilverline yesterday. We started with a basic explanation about Agile and Scrum and zilverline introduced a number of fun activities to get the message across. According to at least a few participants, the day was a success. I can recommend Zilverline highly!

Not only did we explain scrum in practice, we found new energy to improve our working processes further. I heard that the New York Times is already create their newspapers with Scrum, I’m curious what we can do for the cluster in the coming time!

2014 will go into the books as…

Whoa, the year passed already?! Check 1 min video below for our year together, long riverside summer days, walks and traveling Shanghai and Korea.  All of this, while preparing for Mia arrival in December. At work, a lot of energy went into rewriting the largest comparison website of the Netherlands. Here on the blog, the most popular post was the dramatic sounding “end of my Chinese fashion startup.”

I’ll go and cuddle Mia to sleep. Have a great 2015 y’all! (briefest annual wrap-up yet! 2013, 2012)

Screen Shot 2014-12-30 at 22.00.08https://www.youtube.com/watch?v=IyxtzaIqi3A

 

Planning and scaling with scrum

Jeff_Sutherland_joop_dorresteijn_scrum_zilverline

After working with Scrum for some time, I’ve finally became a certified ScrumMaster (SM) at the zilverline course with Marco Mulder en Bas van der Hoek. Addtionally I met one of the inventors of the Scrum software development process. Jeff Sutherland at our company yesterday!

Scrum is like a homing missile

The old school and dreadful IT project style: The customer wants a new website and makes sure to write an extensive project plan beforehand. Better be extra detailed to make sure we’ll get this project right! The customer assumes the project is clear and believes that developers should be able to give a detailed and trustworthy scoping. Planning commences and the project starts. Within no time, unforeseen occurrences happen and the made promises are broken. Both parties eventually become more hostile towards each other and IT has to work overtime to finish and the customer isn’t happy with the final result. Sounds familiar?

The waterfall method described above is like a cannonball. The customer sets a target in the distance and the developers have one shot at hitting it with their cannonball. The shot is taken and is in vain as in fact, the target was moving and there was unforeseen wind, the outcome became clear when it was too late.

An alternative to this is the scrum approach. The empirical approach in which the customer is closely aligned to the developers, releasing software often makes that demands are discovered along the way. Customer happy, developers happy.

Whilst finding roots in software development it’s also applied at banks, healthcare and government around the world, in the Netherlands there’s even a high school applying scrum at a class, where students show increased collaboration!

Epics and roadmaps

I’ve experienced firsthand that trying to scrum a traditional waterfall/Gantt planning can create a lot of friction in an organization. It starts with acknowledgement that Scrum is nice and all but targets are made for an entire year, the ‘business side’ (as apposed to the IT side) should be able to get some commitments over the year.

This doesn’t mean that one should make a roadmap, we’ve learned that roadmaps are too messy of a prediction. A roadmap feels a bit like a large project. The chances of making it are small.

Source: Standish group

Source: Standish group

But… when will the project be ready?

You’ve haven’t even started with the project yet but usually the costs need to be made clear in advance, and marketing activities planned. Expectations have to be given. “When will you finish?” is a pesky question without a roadmap. This is where one needs to be clear. Scrum allows you to produce a realistic planning after some time of development. By reducing size of projects and always focusing on the single most important thing, you will deliver something quickly, and more can be said about the time left for the rest. Tasks are put on a backlog, with most important things in top an detailed. Abstract things for the future at the bottom.

Cone of Uncertainty

Cone of Uncertainty

Finishing sprint after sprint, you will be able to estimate with more confidence. As you know how many storypoints you burn per sprint. Apposed to a long term development like waterfall, scrum will give quicker insight towards completion with a so called ‘release burndown’, showing how many storypoints are left. Additional tasks are added underneath the chart.

3045759561_b273c9ec39_z

Going wide, not deep

Instead of a ‘island’ culture where one team passes work to the other, scrum teams are multidisciplinary and have full access, responsibility and knowledge of the architecture. Only then they are able to understand the why, how and what of the most important item.

Besides that, there can be only one thing important at the same time. People are terrible at multitasking, for a long time people assumed that if you started more, you’ll finish more. It’s the other way around, the more you finish, the more you’ll finish!

During the training, we made a storymap together. It’s an overview of tasks and time. Our task was to prioritize features. In the Image below, we were building the “bare necessity” row.

05fig14_alt
At first, we added all basic functions .The coach then challenged us and soon we realized that the bare minimum could be stripped a lot more. This was an eyeopener, as I’ve felt into this trap often in the past, thinking “I’ve started working on this anyway, might as well extend a little bit on this part as well.” NO! Work wide, not deep. Only then you can deliver fast. What is the actual minimal working skeleton? We also sheepishly added cards at every column, another team skipped even skipped columns for their first release. Why not?

Scaling scrum

Steady teams and performance

I joined the ScrumMaster training with some experience under my belt and a lot of questions regarding scaling and performance. Personally, I had to deal with proving increased output of the team this year and I was seduced to start micromanaging expanding time logging of the team. (Micro) managing isn’t going to get the best out of a team. Jeff Sutherland stressed that simply making work of a team transparent to outsiders is enough to get the team motivated and self steering. When all seems lost, decrease the tickets in one sprint and focus on applying the practices correctly. To increase performance is to keep addressing the next biggest improvement in the team. Dysfunction team members, dependencies on other teams etc. What scrum does is making the process quantifiable so you can break dreadful processes instead of trying to satisfy them more rigorously. Also don’t let the team get disturbed too often, “The door from the business to the IT team is closed, whilst the door to the business from IT is always open”.

A common mistake is of management to assume that adding member to the team will speed up the sprint. It’s usually the other way around. Scaling should always be done slowly. While growing, together with the ScrumMaster (SM), a decision can be made to divide the scrum team in two. Do not simply duplicate the disciplines with new hires in an all- new team. Instead, split the existing team. Make sure the independent teams are still able to complete tickets autonomously. At first, it’s still ok to do backlog refinements together. Later, you can allocate an own backlog and own PO when necessary.

Scrum of scrums

With different scrum teams in place, a scrum of scrum meeting may be implemented, addressing coordination across teams in a simular fashion as the conventional standup. Due to the content nature, it’s not uncommon to send the PO instead of the SM. Alternatively to the group just standing in one room, walk past all the teams and their scrum boards.

Portfolio9

With a split team, the chief product owner can keep a scrum-team-per-lane overview with a so called “Epic board”, to helps to see inefficiencies and to plan future sprints together. When there are multiple teams, it’s advisable to plan demo’s after each other and together. Before the training, I read that Spotify implemented so called component teams, in which teams are allocated to various GUI components; one for the music player, another for the login window and so on. To facilitate this, technology needs to change the architecture. Component thinking could lead to double work between the teams but this is ok and a sertain isolated approach on similar things should be encouraged towards the team.

From the Q&A session:

Tips for increasing efficiency?

Let the team do a retrospective round on paper so everybody can give their opinion.
During planning poker, a discussion might occur. Sometimes it might help to end an argument with another round of planning poker instead of a guess from a few people.
‘Fist of five’ for commitment. Count down and raise a range from 1 to 5 fingers when you support the commitment.

Is a ‘research’ ticket a valid approach?

No. A research ticket is not part of work and should not be part of the sprint. A ticket should be completable within one running sprint.

What if you have dependence of a non scrum team?

When you know this in advance, the backlog item simply wasn’t ready and should be marked accordingly and as impediment. This has to be made clear to PO as quickly as possible. It shouldn’t belong at the top of the backlog, as it doesn’t have priority from the business. In that way, the SM is responsible for solving this situation.

Do you count the points of an unfinished ticket?

When a ticket isn’t finished in a certain sprint, do not count points for that ticket in that sprint.

Does the UX’er work in a ‘sprint zero’?

Sprint 0 does not exist. Sprint zero gives the idea that there is a phase where one doesn’t work. This is not the case. The PO and the UX’er have a secret side to the conventional scrum flow. Whilst the team is following the sprint, they already workout the tickets for the coming sprints. In that way they have a ‘secret’ sprint. A UX’er needs to find balance to work within the team, but also work ahead in making the UX foundations for templates before the sprint starts. If the UX’er does everything ahead of the sprint, the team cannot work together for optimal collaboration.

Should I create a second sprint to prioritize non-business things like IT?

get business priority for IT project. Remember to sell the problem, not the solution. Make sure that the BLI isn’t called ‘Varnish v4 upgrade’ but “Get our website to load within 200ms and increase conversion.” be clear about the results.

Tickets & backlog:

A nice way to avoid assumptions on the backlog is to create (abstract) user stories. Avoid assumptions by always asking why. It shouldn’t be possible that multiple items on the backlog are evenly important.

Scrum organization

I found that some organizations are completely scrum. At ING bank, they do standups at every level of the organization starting bottom up. When there is an impediment at bottom, it should be answerable within 2 hours when top management has a standup._