<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Gerbrand Colombier on Medium]]></title>
        <description><![CDATA[Stories by Gerbrand Colombier on Medium]]></description>
        <link>https://medium.com/@gerbrand.colombier?source=rss-e67a78f8e1ad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Gg-t5TjSvoihlzwCg8U2CQ.png</url>
            <title>Stories by Gerbrand Colombier on Medium</title>
            <link>https://medium.com/@gerbrand.colombier?source=rss-e67a78f8e1ad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:22:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gerbrand.colombier/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[My creative retrospective images]]></title>
            <link>https://medium.com/@gerbrand.colombier/my-creative-retrospective-images-de4ad6bb986?source=rss-e67a78f8e1ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/de4ad6bb986</guid>
            <category><![CDATA[imagination]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[drawing]]></category>
            <dc:creator><![CDATA[Gerbrand Colombier]]></dc:creator>
            <pubDate>Thu, 02 Jan 2020 15:47:41 GMT</pubDate>
            <atom:updated>2020-01-02T15:47:41.749Z</atom:updated>
            <content:encoded><![CDATA[<p>On this day, I’m already working 12 years at the company Adsdaq, a small developing company. We provide publishers a selling tool for their advertising placements on their digital websites and their print papers or magazines.</p><p>During the whole transition of my dev team, I tried to have some good images that would tell how the sprint went the past two weeks. Which isn’t always easy, in the beginning, I decided to find pictures from the web, but it became more and more challenging to find the right image. I mostly used Dilbert cartoons back then.</p><p>Since the end of 2017, I started to draw my images for our retrospectives. Although I found them at the beginning childish, my team didn’t mind it and even found it awesome at some point, eager to see what I came up with this time. Those pictures created a starting point on what had to discuss. Of course, in case nothing exceptional happened during the sprint, I tend to use a nearby holiday theme like Christmas, Saint Nicolas day, Easter, and so on.</p><p>I take my time to make them, of course, I first draw them on paper in pencil, then I go over with a pigment liner, then take a picture of it, to polish it a bit in photoshop and then add them to my retrospective tool as the first slide.</p><p>Now I found it the time to share some of my created images on the web and who knows they are an inspiration or helpful to use at your retrospectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LGgtgfi7mZo-EJ2rjpmTGw.png" /><figcaption>Sprint looks fine at first, but in the end, it wasn’t.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b0E7LAI-7IDbqrmTjzYvyA.png" /><figcaption>A sprint was faster done than expected</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ySuKdlEVpzfc0PEFydIgg.png" /><figcaption>Some factors that made the sprint fail</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FP3RD3rbtQ-AK1KSjd2KNA.png" /><figcaption>A sprint that was though to finish was crushed without any problem</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w_FQ-oL3UpTP9IpkwHNSSQ.png" /><figcaption>Confirmation by an external person on how we are working is top</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hnTMdf_x00VdFKzJdFPqog.png" /><figcaption>I had no inspiration, and it was on the 4th of May. Team members suggested a unicorn.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SRXY5TJgQdRy7JTOmc5IGw.png" /><figcaption>Sint Nicolas day in Belgium.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c_CIQYzksC5PazdYrADipg.png" /><figcaption>We had quite some team members sick, and the reviews pilled up</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u0IikjeLUFJFBFgniomwAg.png" /><figcaption>To announce the deadline of a project is coming close</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mZQga4YO12PIy6LpVViSXQ.png" /><figcaption>A welcome to a new team member (knight) see another story I wrote</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7yNf9yvd_WBiAK8jLigwAw.png" /><figcaption>An issue we had, some member were more focussed on developing more stories but forgot to do some reviews</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zzJ8O9T8CktcbFz3I315mg.png" /><figcaption>We missed some deadline due to distractions and nitpicking during reviews</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q3bMaYKMU4a4rgffDnO1wQ.png" /><figcaption>Christmas 2019</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wb5bGES1SAcWJPSHnZjnfg.png" /><figcaption>Good collaboration between the team members</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-kdXfR52mgR-6ZF5lA0SWg.png" /><figcaption>We tried something new, micro teams, and we did a review on how it went during the retrospective</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rfHU1ZQttiy-QzMZJhy5Kg.png" /><figcaption>When my team in LK won a bowling game</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XRiD_pnguK8NIY71lAKFvQ.png" /><figcaption>When our brand came into the papers</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WA2xS8DpfvoVHezfMr-iHA.png" /><figcaption>When we had communication issues</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qhr9Z0EwLvEsSb2gkYwc0Q.png" /><figcaption>We reached for the first time five sprint in a row</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZCe9GmX1GQUkwfGjMFLviQ.png" /><figcaption>Then five sprints later another record and it kept going</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qqzMtT8UsoYfVW7_IzzN8Q.png" /><figcaption>A sprint where a team member left us, exciting news about our product and attending PHP Benelux as a sponsor + doing a talk</figcaption></figure><p>The pictures are only a part of what I created, and I wanted to share them with the world. Who knows, they can be useful or inspirational for somebody.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de4ad6bb986" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile/teambuilding games]]></title>
            <link>https://medium.com/@gerbrand.colombier/agile-teambuilding-games-41478bac36c3?source=rss-e67a78f8e1ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/41478bac36c3</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[teambuildingactivities]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[agile-game]]></category>
            <dc:creator><![CDATA[Gerbrand Colombier]]></dc:creator>
            <pubDate>Tue, 04 Jun 2019 12:26:17 GMT</pubDate>
            <atom:updated>2019-06-04T12:26:17.385Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the six years as a scrum master/product owner/team leader at Adsdaq, I’ve come across a lot of Agile/teambuilding games. Most of them I tried during our annual Agile Game Day, that I organize at Adsdaq.</p><p>A lot of the games I found on the old <a href="https://www.tastycupcakes.org/">tastycupcakes.org</a> page. Now they have renewed their website, and I don’t see all of the games back. I’ll try to add links to</p><p>Underneath the first overview of some games I used.</p><h4>Rory’s Story Cubes</h4><p>I’m going to start with one of my favorite non-agile game, but it is handy before a story mapping meeting or retrospective meeting. I will open the minds of the participants and trigger their creative parts of the brain. A lot of fun and I also recommend this to play with your kids!</p><p><a href="https://www.storycubes.com/">https://www.storycubes.com/</a></p><h4>Paper plane factory</h4><p>It is a great game to illustrate agile practices. There are a few variations on this game. I have played 2 of them. <br>A straightforward version was, I had two groups of 4 people. Each of the members can do only one action on building the plane. Cut the A4 paper = 1 action, doing a fold = 1 action. Assign one person to test the planes. Only he/she can throw the planes. It is a successful test when the plane flies for 2–3 meters. You decide on the distance.</p><p>There is no need to tell the teams what kind of plane they have to build; they will figure it out themselves.</p><p>The process for four sprints:</p><ul><li>1-minute retro/planning</li><li>3 minutes of building</li></ul><h4>Paper plane factory V2</h4><p>The second variation I did, was the same, only that I printed out the different type of planes and an example of how each sample looks likes once done.</p><p>I also prepared user stories like: “as a customer, I want to have 2 type x planes and 3 type y planes.” Each team had a stack of user stories, and during the 1-minute retro/planning, they decided which stories to take for the sprint. Building time was 5 minutes since the planes folds were more complicated. They had to fly over a certain distance, which is written in the acceptance criteria of the user story. Each user story had a business value assigned</p><h4>Escape the room</h4><p>Is a silent communication game; each participant sits on a chair which is randomly distributed in the room. When you start, let them all lift their feet from the floor and say: The goal of the game is to escape the room. From now on, nobody is allowed to touch the floor or speak to other participants.</p><p>You will see different scenario’s, people hopping with their chair to the door or others will try to make a bridge with the chairs around them to help others and then make a way to the door. And the more people you have, the better :-)</p><h4>Fruit salad</h4><p>Another good ice-breaker to start the day. Make a circle with chairs; it should be equal to the number of participant minus one. Everybody sits on a chair, and one person stands in the middle. Go around the circle and assign each person to a fruit. You can take four possible fruits like strawberry, banana, apple &amp; mango. I found the rules back for this one :</p><p><em>“Whenever the person in the middle calls out a fruit, the participants that fruit was assigned to have to get up and quickly find a new chair to sit on. When they get up, the person in the middle also tries to find a chair.</em></p><p><em>Given that there is one chair less than the number of participants, one person will end up without a chair, and the game starts over. Instead of fruit, the person in the middle can shout ‘fruit salad,’ which means that everybody has to find another chair. It is not allowed to sit on any of your neighbor’s chairs.”</em></p><h4>Racing game</h4><p>A top-rated game here at my office. I think this game has been in every game day I organized. You draw on a big paper (flipchart size) a race track. Just google “race tracks” or let your imagination do the trick.</p><p>Next, you need to create a pen holder that is attached with an x number of cords to it. See the image below. The goal of the game, go as fast as possible around the track without lifting the pen from the paper or go over the track boundaries. Create different types of tracks, sometimes the ones you think are easy are mostly the hardest, also variate in the thickness of the road.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KC3PzX9m0U3G_21rU6IM_A.jpeg" /></figure><h4>The Penny game</h4><p>This game is an excellent game to show what the benefits are of working of small batches instead of large ones. I only played this once with my Sri Lankan team, and it shows that keeping our stories small, makes work go faster.</p><p>All information can be found here: <a href="https://www.tastycupcakes.org/2013/05/the-penny-game/">https://www.tastycupcakes.org/2013/05/the-penny-game/</a></p><h4>Face Identity</h4><p>An excellent game to start the day, but you need to do some preparation beforehand. You need to ask in advanced two personal things of the team member. One thing that generally the other team members know of him/her and one thing that nobody should know or a minimal amount of team members. Create small carts of each personal item and make sure to remember to whom they are linked. I made it in 2 colors, so they knew what the easy carts are and what the harder once are.</p><p>I had two teams of four people each, and I assigned them to draw their face on an A4 paper. It doesn’t have to be a Picasso, but you should recognize them. Once done, hang them on a wall. Now you distribute the carts so that each team has the cards of the other. The assignment now is easy, hang the cards under the right head. Know that each head will have an easy and hard card linked to it.</p><p>Once both teams are done, check which carts are correct and those not. Let the people give some more explanation about their item, or let them tell the funny story linked to it :-)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xE-nmp75u26GhCSDhW-4LA.jpeg" /></figure><h4>Ball point game</h4><p>Get your self a load of tennis balls and see how many balls your team can process in 2 minutes. Do five iterations and see how they improve each time.</p><p>The rules are simple:</p><ul><li>Participants play as a whole team (everyone must touch each ball)</li><li>Balls must have air time between people</li><li>No passing to a direct neighbor</li><li>The start person must be the end person</li></ul><h4>Ball flow game</h4><p>Same rules as the ball point game, you only use 20 balls and see how fast they can process them.</p><p><a href="https://www.tastycupcakes.org/2014/05/ball-flow-game/">Ball Flow Game</a></p><h4>Throw the cat and other stuff</h4><p>This game will create some good discussions regarding estimations. You will see that one team thinks differently than the other team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-5tXMI2sev5WnODV0JTT2g.jpeg" /></figure><p><a href="https://www.tastycupcakes.org/2016/05/throw-the-cat-and-other-objects/">Throw the Cat.. and other objects</a></p><h4>Rock paper scissors but as Bear grandma samurai</h4><p>Classic game, but instead of using only one hand, they use their full body. First, pair up the people (2 and 2) and instruct how to show the figures:</p><p>Bear: Hands in the air and roaring with a deep voice<br>Grandma: Smile sweet and giggles in a calming voice<br>Samurai: Stands tall holding his sword in both hands and saying: ‘Hai!’</p><p>Rules:<br>Bear beats Grandma (eats her)<br>Grandma beats Samurai (He feels so comfortable that he forgets to fight)<br>Samurai beats Bear (slays it with sword)</p><p>Best out of 3.</p><p>Most of the games you can find easily on google if you need more explanation on how to play it. But I’m happy to answer your questions.</p><p>Have fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41478bac36c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Lego scrum board, how we use it!]]></title>
            <link>https://medium.com/@gerbrand.colombier/a-lego-scrum-board-how-we-use-it-e581f86e109a?source=rss-e67a78f8e1ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/e581f86e109a</guid>
            <category><![CDATA[agile-scrum-board]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[scrum-board]]></category>
            <category><![CDATA[scrum-agile]]></category>
            <dc:creator><![CDATA[Gerbrand Colombier]]></dc:creator>
            <pubDate>Fri, 15 Mar 2019 17:39:06 GMT</pubDate>
            <atom:updated>2019-03-16T08:06:50.087Z</atom:updated>
            <content:encoded><![CDATA[<p>Are you looking for a way to visualize your digital scrum board to have easy standups at the office? We at Adsdaq use a Lego board, and this provides a fun and useful overview of our sprint.</p><h4>First, a little bit of history</h4><p>Back in the days, when we started to become a tremendous agile team, we struggled in finding a good way of showing our sprint visually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ff3JpAWOq4OoARbvybk_bQ.jpeg" /><figcaption>We started simple</figcaption></figure><p>In the beginning, we had a single piece of long paper, attached to the window of our office. Only three columns present: Open, In Progress, Done. Within we had the purple post-it that represented our epic and the yellow post-it the stories for it. This board was good and not so good, but we were happy about it, and it worked for us.</p><p>+ Good</p><ul><li>Good overview</li><li>Big space to add the stories</li><li>Could be seen from the whole office</li></ul><p>- Not so good</p><ul><li>Too high for the smaller team members</li><li>Hard to read the post-its</li><li>Took some time to write the post-its</li></ul><p>After some sprints, we had some discussions with the CEO/Product Owner, and he wanted to have also a view on coming features/epics. Since it wasn’t always easy to see it in Jira. So, our physical board went in overdrive:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SgWKQHVt8Iz5j3Ovol3izA.jpeg" /><figcaption>A kanban board with a scrum board combined</figcaption></figure><p>All the different statuses that our features/epics could have on this Kanban board were on the physical board. The part that you see with post-its was the actual scrum board for the developers. The other Kanban columns were for the CEO/Product Owner to keep track.</p><p>In truth, in the beginning, we kept this part of the board updated, but after a while, we just stopped doing it. Only the scrum part, was an active board that moved during the standups.</p><p>As you can imagine, this large board blocked our sun, and the scrum board was the only part that changed daily. The kanban parts weren’t always updated correctly. So in the end, it wasn’t very productive to have this up.</p><p>+ Good</p><ul><li>We had a full overview of what was coming to the development team</li></ul><p>- Not Good</p><ul><li>updating those parts not related to the dev team wasn’t done frequently</li><li>Less space for the scrum board of the dev team</li><li>Still too high for the smaller team members</li><li>Blocked the sun</li></ul><h3>Our Lego board</h3><p>A couple of years back, we moved to new offices, and there we didn’t have a luxurious long wall anymore. So, I came with the idea of putting up a Lego board.</p><p>Before I jumped into hanging big Lego boards on the wall, I tested this out at home with my stash of Lego’s. With the try-outs there, I concluded how to tackle this.</p><p>First things first, getting the big gray base plates of Lego, 12 in total, on the wall. So the lego plates are glued to some wood and then fixed with plugs to the wall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IYrUdi8UkSJLfuGgrx-8Fg.jpeg" /><figcaption>12 plates attached to the wall</figcaption></figure><p>Next up, getting those stories on the board. I solved it, by using a 2x6 block and a 2x4 plate. This way made it a bit thicker and more accessible to take it off an on the board. In Jira, I found a plugin “agile cards,” which enables to print out the stories in the card format as you can see underneath.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RGERQZjtsU5aF_hTIdWJRQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1X3kD5E7ArAhI3Wt8LTOvQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M3_1j8KssM5GpSkYcnunJw.jpeg" /></figure><p>Making two holes, with a hole puncher, on the spots were the top knobs of the Lego block are, allows you to fix the card with a 1x2 green block.</p><h3>Our Lego characters</h3><p>To identify the team members, each of us created there own Lego character and chose a color. Each member has ten blocks, which initially was the idea of availability of that team member, but in practice, we don’t look at it. We have very rare a sprint where a member doesn’t have any blocks anymore because they are all used on tickets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SS_U2ZN5dJ95etvJikj2xQ.png" /></figure><p>Since we have team members in Sri Lanka, we identify the scrum master with the green arrow next to his character.</p><h3>Scrum columns &amp; rows</h3><p>Our board is split into four main columns: Open, Progress, Review and Done.</p><p>The progress column has a small additional column that indicates a ticket will be done today with coding and will be moved to review the same day or beginning of the next day.</p><p>There are also two rows on our board, one big one, which indicates the main goal stories of the sprint and the row underneath, indicates the subgoal stories of the sprint. With this separation, we know that the ticket stated as the “main” goal is necessary to be closed this sprint. Subgoal tickets aren’t necessary to be closed this sprint and can still be in “open” at the end of the sprint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P0sOxBRmIuGCrLZJJxhKzg.png" /></figure><p>At the beginning of a sprint, I’m attaching the stories to the board, in the way it is shown in Jira with the swimlanes. At the top of the board, we have our Bug tickets and then starting with the epic stories. Those epics are mostly in order of importance. But this isn’t always the case when all epics are evenly important.</p><p>Underneath our characters on the left side of the board, we have our sprint indicator. This indicator is determined during the standups each morning. Once a story is indicated with a yellow or red 1x2 brick, the risk is immediately shown.</p><h3>The tickets</h3><p>The printed tickets, with the agile cards tool, can be designed with the information that best fits for your team. In our case I have the following information present on a ticket:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/252/1*wbcsHm60Cm7puLX0lBSnIw.png" /><figcaption>typical story</figcaption></figure><ul><li><em>Issue type Icon: </em>Story, task, analysis, story defect or bug</li><li><em>Priority Icon:</em> Blocker, critical, major, minor, trivial</li><li><em>Issue id:</em> In our case ADQ-XXX</li><li><em>Summary:</em> Ticket title</li><li><em>Epic:</em> Title of the epic the issue is linked to</li><li><em>QR-code:</em> Can be scanned during the standup to look up some details with the mobile app of Jira.</li><li><em>Customer:</em> This is mostly our company name, but if a customer specifically asked something, that name is set.</li><li><em>Sprint Goal:</em> Indicates if the ticket is a main or subgoal focus.</li><li><em>Story point:</em> Effort of the ticket, measured in story points.</li></ul><p>Each issue type has also a color right side border to indicate what kind of issue type it is. This can be set in the agile cards add-on.</p><h3>Standup Routine</h3><p>Each morning at 10 o’clock, we have a standup meeting. We have a softball that we pass to the member that talks about what he did the day before. Which issues he has and what he was able to finish. Then he talks about what he will be doing today. Team members move their tickets in the right column and add the correct reviewers to it when it is moved into “review.”</p><p>After every member did their overview, I provide a summary of what our Sri Lanka team members did (I have each morning 30min before our standup a call with the Scrum Master in Sri Lanka). Then we check if some stories are at risk or not. Once that is cleared, we check if there are questions/remarks towards other team members regarding a story.</p><p>All this takes about 10–15min with six team members each morning.</p><h3>Conclusion</h3><p>With this board, we have a very clear overview while doing our standups. I may take a bit more time to set up the board each new sprint (30min max in my case), but it provides all the information during our standup.</p><p>We can clearly see who is on which ticket and can ask the right questions on the spot.</p><p>This is how we use our scrum board in Lego and it is a tool we can’t miss at this moment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e581f86e109a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our agile Transition at Adsdaq]]></title>
            <link>https://medium.com/@gerbrand.colombier/our-agile-transition-at-adsdaq-f823b2a7f55a?source=rss-e67a78f8e1ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/f823b2a7f55a</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[transitions]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum-agile]]></category>
            <category><![CDATA[knowledge-sharing]]></category>
            <dc:creator><![CDATA[Gerbrand Colombier]]></dc:creator>
            <pubDate>Mon, 24 Dec 2018 14:00:40 GMT</pubDate>
            <atom:updated>2019-03-19T13:54:07.899Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*26zshzzrRY2dIN_Wm0LgNQ.png" /></figure><p>Our journey to be an agile company explained in storytelling.</p><h3>Preliminary</h3><p>To understand the story and references I’m making, you can find underneath a list of comparison items I’ve used.<br>Kings: founders<br>Knights: developers<br>Captain: team leader<br>Queens: clients<br>Castle: our software solution<br>Dark wizard, Dwarfs, Trolls, Dragons: issues, bugs, complex code, …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HCoEboin1x9HNU1hMcS2Sw.png" /></figure><h3>The year is 2007</h3><p>Once upon a time in the year 2007, September 2007 to be exact, two kings decided to build a new and impressive castle. A never seen before type of castle on the market and that would attract a lot of new queens worldwide.</p><p>They started by hiring some Knights that could build and defend the new castle. They had already 1, and they found and convinced two other Knights to join the adventure. The two kings had an excellent idea of how they saw their new castle and had a good knowledge of what was out there on the market. So they started to share their ideas with the Knights, and each knight then began on building pieces of the castle. After a few months of long building days and nights, we finished some parts of the castle. From that moment, the kings start to showing it during their sales pitches with potential queens.</p><p>Months go by, and the fast building kept on going. The kings managed even to attract some queens to joins us in our castle and use the castle for their daily business of selling advertisement placements. That was a lot faster than the old way of going door by door. With the first usages of the castle and the fast building, we didn’t start to notice little black clouds gathering on the horizon. What we didn’t realize was that these black clouds would bring a dark force of dwarfs, trolls, and dragons. Each knight was working on different parts of the castle, that we didn’t realize the oncoming trait. Little by little the queens started to report the first dwarfs entering our castle and annoyed the queens in their daily routine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*LFe2pXxHJ3oOSrdL1w88QQ.png" /></figure><p>The kings, who received the first word of this, started to inform the knights and they began to search the castle to destroy those dwarfs. <br>While those actions were happening, the kings and queens continued talking to each other about new opportunities for the castle. The queens demanded the new features and the kings agreed on everything.<br>So now the Knights didn’t only have to fight the dwarfs, they had to build a new part to the castle or adapt them to please the queens. Since each queen had their separate desires for the castle, it was difficult to acquire the correct setups for all of them.</p><p>Lists were made by the kings about the new desires of the queens or parts were they saw dwarfs wondering around and then delegated/explained to the Knights. Each knight did their best to fight the dwarfs and build new parts of the castle. And to achieve it as fast as possible, Knights started to take more and more shortcuts to have it done more quickly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*v1vFr8EReaLCFo4Cwckjog.png" /></figure><p>So the castle was growing fast, but the dwarfs and even trolls were able to get in more quickly also due to the lack of proper testing and verifications after the build was done. We also had a communication problem between the kings and queens, sometimes the king came back with a new idea of a queen, but he understood it differently than how the queen wanted it.<br>This same problem was also happening between the kings and the Knights since sometimes the notes that were taken weren’t correctly done or verified, which gave the situation of some that were built in the castle that the queens didn’t want like that.</p><p>At one point, we were so overwhelmed by the dwarfs and trolls that were present in the castle. We had almost no time in building new parts for the castle, only time to fight and fix broken pieces of the castle.</p><p>This situation went on for a few years. We hired new Knights to help to build and to defend the castle against the dwarfs and trolls. But most of the Knights stayed on their part of the castle they knew the best. Sometimes another knight came rushing in to help a fellow knight fighting a dwarf, but it wasn’t a common thing. Each knight tried to fight and build it alone.<br>As time passed, the build of the castle became bigger and complicated to navigate through, which made it hard for the Knights to find the dwarfs and trolls quickly. Even some of the seasoned queens got lost in all the functions of the castle, and it required the kings also more effort in explaining and guiding the queens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*ppbtLkWOLTlO3zdni0sUHw.png" /></figure><p>In the meantime, dragons have found their way silently into the castle and had settled themselves in a dark part of the castle. Only a few of our Knights were brave enough to go those parts and try to fight the dragon.</p><h3>A breeze of change</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*QRomVCPNCn30ucSEhW2gjA.png" /></figure><p>A few years passed by with this working method and by the end of 2010 beginning of 2011, the kings had enough of the situation and wanted some changes. Both on the productivity of the Knights and also on the organization internally. Themselves went on a quest to find a solution for our chaos inside but even outside. In that same period, we hired our first Sri Lankan Knights, in the hope they could help us in our quest of building this fantastic castle.</p><p>After a while, the kings came back with a book about Kanban. They did some further research in the local libraries. In their search, they came across an abbey of white wizards that were kind enough to send us one of their white wizards: Nick Boucart. He came and looked at our processes and told us we were walking a path of disaster. With the whole team of Knights and the kings, he explained to us the concepts of Kanban and Scrum and recommended to start with Scrum. We all agreed, and he guided us on how things should go for the planning, the daily stand-ups, … He did some follow-ups for some sprints, and then it was up to us to continue the journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*D9iOFn-2EyCnCuYlJkLwmw.png" /></figure><p>One of the kings took it over from Nick, and we started to get organized. We followed the Scrum method for several months. We had sprints of 1 week, daily stand-ups with all the Knights and all tasks were written down in the way of “as a … I want to … so that … “. Then we tried to put a story point on the task. At the end of our sprint, we had a retrospective on the past sprint.</p><p>The kings also found a new tool, Jira, to use to get us better organized for all the requests and tasks that were coming but also where all the dwarfs, trolls and dragons were situated. In this tool, we even had our queens involved in so they could give us an indication of where the dwarfs or trolls were hiding. Which was very helpful in some cases but sometimes the queens thought they saw a dwarf, but in reality, it wasn’t a dwarf, but a decoration they asked for.</p><p>But we failed miserably with our quest to use Scrum. Why? Because we didn’t stick to the rules, sometimes we made a sprint of 2 weeks, or we skipped the daily standup, or the planning wasn’t ready for the next sprint. All that because the king didn’t have the time to keep track of it, because he was already full in discussing things with the queens and following the progress of the build of the new parts for the castle.<br>Even the Knights didn’t continue the daily scrum tasks, due to the tight schedules of building the new parts together with fighting against the dwarfs and trolls. But also because some of the Knights didn’t like to work like that. I blame the black wizard that cursed their minds.<br>So all of that made it very difficult to adapt to this, but the most missing part was somebody dedicated it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*RA-xswnE5IyvWd1Q1BUTzA.png" /></figure><p>A year passed again in a snap, but this time the winds changed in the right direction …</p><h3>The winds of change</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yu_YcHWzHuIkuDMFPR9Pxg.png" /></figure><p>There was a knight, me, that was present from the beginning. I’m honest, I had it with the fighting against the dwarfs, trolls, and dragon + building/adapting at the same time parts of the castle. I admit, I wasn’t the expert in building and I never would become one in the current environment. But I was intrigued by the scrum / agile methods and being the captain of the Knights. So together with the kings, we agreed I would take that responsibility step by step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*Zqs-UKnbjw3Zpj3olunezg.png" /></figure><p>The first step was to put back the scrum process in the team. We started to simplify our Jira tool because that one also became too complicated to have a good overview of things that needed to be done. <br>As a team, we decided to have sprints of 2 weeks, nothing more nothing less. Our daily stand-ups were set at 10 o’clock each morning. We just stood up in a circle, all with or without a piece of paper, with what the knight did the day before and was planning on doing that day. <br>Planning was done together with a king, and during the retrospective, we discussed our velocity and what we did right, wrong or not to do anymore. Everything was noted and tracked in our book of wisdom called Confluence, and I guarded this with my life and made sure the team followed it.</p><p>Another thing we changed was our building process. We introduced that each knight should review the other Knights building before we told the kings and queens that a new part of the castle was finished. The same for the annoying dwarfs, if a knight came back saying he defeated them, a knight double checked that no dwarf stayed behind. This change made a big difference … and as time passed, we noticed lesser dwarfs and trolls hanging in and around our castle, which pleased our queens of course.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*hsdch5AJcuo0LVFZComi-A.png" /></figure><p>The process between the queens and kings have improved also. The first thing was to say NO to the queens when something wasn’t doable or not relevant to building it in our castle. This required some understanding of our queens, but after a while, they have accepted it. There was also a common understanding of writing the new request for the castle down in a document that was a reference for once the build was done.</p><p>By now the Knights with the cursed minds left the castle, and new Knights found their way to us, which created a steady team that was willing to go further and takes the challenges together. To increase this bound between the Knights, I organized our team gathering, with a day of fun and not to think about the work in our castle. Our team became closer and working more and more together. I became the captain of the Knights and guided them as good as possible in the right direction.</p><p>As of 2014, I started to go to big gatherings of other Knights and wizards that talked about agile processes. My first gathering experience was the Agile tour Brussels 2014 and returning from that gathering I had a bag with a lot of new ideas and books to be read. Since then I never missed a gathering and each year I had new ideas to try. With that gathering, I also found a new one, XP Days of which I had my first one in 2015 the mini XP Days and since then the same, I never missed one either.</p><p>On one of those gatherings, I got to know another great wizard: Jef Cumps. He helped us in refining our processes in 2015 and acknowledge that we had a good process going on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*QsVuKKrjERNGpu9ZGMZzeg.png" /></figure><p>So inspired by those yearly gatherings, I organized our own Yearly Adlogix Agile games with the purpose of showing the agile processes through games. Our Knights learned each time again something about the process while having fun. If I wanted to have something new in our process, I made a game about it or used existing games. It is a day that the team looks forward to each year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*CEPR8fAX-dHPEeWL3RBAvQ.png" /></figure><p>Our Jira tool is great, and we can’t live without it at this point, but for our stand-ups not really. We wanted something visual that we could see immediately. And so we started a period of different physical scrum boards on the barracks walls.</p><p>Our first scrum board 1.0:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ff3JpAWOq4OoARbvybk_bQ.jpeg" /><figcaption>First scrum board 2014</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-KrEgHfs9z9jgfkVbYbog.jpeg" /><figcaption>First scrum board 2014</figcaption></figure><p>Our scrum board 2.0: Here we include the cycle of the request of our queens. In that way, we had a visual on what the next things are to come in the building cycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZycMrWilhyOG4Q9p00F_Jw.jpeg" /><figcaption>Scrum board 2.0 2015</figcaption></figure><p>Our current scrum board since 2016 3.0: A Lego scrum board, the best one we have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DFwmnHatEhVACBf5ZUgzow.jpeg" /><figcaption>Scrum board 2016</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1j-zwiPKbpt40eCdFBP4SA.png" /><figcaption>Scrum board 2018</figcaption></figure><p>Our retrospectives experienced the same kind of transformations during the years. First I build it with a power point and later that involved in using a Jira board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*UWbnhIecq60vW5cMR4VkEA.png" /><figcaption>Each retro a different type of image</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HQR_LZLQaJfQhDFyq62uLA.jpeg" /><figcaption>PowerPoint version with the columns</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*tf4eQBL4iScJblvbFnMA9w.png" /><figcaption>Jira retro board since 2017</figcaption></figure><p>Since last year, I’m making a drawing each sprint that relates to the sprint and describes it in one sentence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7yNf9yvd_WBiAK8jLigwAw.png" /><figcaption>The one where we need some focus</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wb5bGES1SAcWJPSHnZjnfg.png" /></figure><p>The one where we collaborated together</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gnxmvmuRAGp0KgGpfn9rOg.png" /><figcaption>one with the Halloween review!</figcaption></figure><p>To show you that retrospectives are helpful, I have the following case. We had issues of reviews taking long, not in the sense that the build was terrible, but in an understanding of the knight that had to review it, didn’t find the time to do it. That made us lose time. So we decided that once a building is in a review, you need an approval of 2 Knights: a functional one and a technical one. You assign 2 Knights, and in case they don’t have the time, they should mention it. In that way, another knight that has the time can have a look at it.</p><p>A year and a half back, we had a period where the Knights weren’t motivated entirely, and I knew that we could do better than the current velocity. But we couldn’t find a reason why this was happening. Since I like playing games a lot, I found information on how to gamify your process. Reading a lot about it and figuring out a system in our environment, I introduced this in 2017 and today we are still using this system. First, we build it in excel and afterward I made it digital that retrieves the information from Jira and calculates the points automatically. Those points are used for a personal incentive but also a team incentive. Those are used to organize the team gathering and game day. More points mean more money for those days. But we agreed that the team building is always done even if we have minimal points. It just says we are maybe doing arrow shooting instead of cruising with a ship.</p><p>Something else that we recently started to do is to share our love amongst the Knights. I implemented the Adsdaq love wall… a wall where you can add your appreciation to a fellow Knight. If during the sprint, a knight did something extraordinary or helped you unblock a build, you can write a love card to that knight. During the retrospective does cards are being read for all the Knights</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*c5tuP_baLevl5FwTFYNPkg.png" /></figure><h3>Present day</h3><p>For two years now we are building a new and simplified castle, with an agile process on point. We see from time to time tiny dwarfs popping up, but until today we never had to face a troll or big dragon. We can see that also in our discussions regarding processes, and they are more about details than about big things. But we never stop trying to improve our processes.</p><p>Like the way, we introduced this year, micro knight teams. We have micro teams of 3 Knights working on an epic. They can review each other work, and you always know who to pick as a reviewer. Each micro team has his micro leader, and he follows ups the epic progress. When issues arise, he will be the person to report it back to the captain.</p><p>Today we have 13 Knights to build and to defend our castle, and I’m doing my best to lead them. Of the 13, we have 8 in Sri Lanka, and they are a big part of our team, and they are a great value. It took us some time to get their mindset from just executing tasks to a mind of thinking about how a request can be built and letting them also do some investigations and then implementing it. <br>The Belgian and Sri Lankan team is one big family, and as in every family we have some struggles, but we communicate and talk about it so that everybody on the team feels good and is happy to come to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*xFKc_tJkq2kl4PG4yGYv9w.png" /></figure><p>So, looking back on the track of 11 years, from where we came to what we are today, is such a huge difference. When I ask if we should go back to our old way of working, I will get a no immediately as an answer.</p><p>Today, I can say that we have a team of Knights with a good team spirit and mentality to achieve our goals. Each of us has their pros and cons, we aren’t perfect, but we accept that, and we do what we can to achieve success.</p><p>And that concludes this story of our transition at Adlogix/Adsdaq.</p><p>Underneath I have added the list of books, I’ve read during those years. The tops ones are the most recommended ones in my opinion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*vfEQHMG1XO0mRHq8hTttxw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f823b2a7f55a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>