<?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 Tomasz Tarchała on Medium]]></title>
        <description><![CDATA[Stories by Tomasz Tarchała on Medium]]></description>
        <link>https://medium.com/@ttarchala?source=rss-862bfedc4e73------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4g-ZDW8XcWhWoxlApFDdRQ.png</url>
            <title>Stories by Tomasz Tarchała on Medium</title>
            <link>https://medium.com/@ttarchala?source=rss-862bfedc4e73------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:56:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ttarchala/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[Agile Cards: a Fun and Flexible Way to Industrialise and Standardise, 3/3]]></title>
            <link>https://medium.com/pictet-technologies-blog/agile-cards-a-fun-and-flexible-way-to-industrialise-and-standardise-2-3-42803fbfc89?source=rss-862bfedc4e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/42803fbfc89</guid>
            <dc:creator><![CDATA[Tomasz Tarchała]]></dc:creator>
            <pubDate>Fri, 08 Apr 2022 06:27:22 GMT</pubDate>
            <atom:updated>2022-04-11T08:09:10.810Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is the final part of our three-instalment article.</em></p><h4>The Iterations</h4><p>We picked the practices, described them, and tested the cards in several dry runs, first with selected members of our Scrum Master community, then with everybody all together. At the same time, we prepared different physical prototypes — of various shapes and sizes, text/image layout, elements included. We had to practice what we preached, after all — without this iterative feedback loop, the cards would have no chance of getting buy-in from our own Agilists, not to mention from the wider constituency of our team members and stakeholders.</p><p>The challenge of how to prepare many copies of a physical product and getting it distributed was also quite stimulating, especially as it coincided with the breakout of the global pandemic. Many of our community’s members displayed hidden talents and contributed varied knowledge, ranging from the literal copying &amp; pasting of images on prototype cards to navigating the global (UK, Europe-wide) printing press industry… In the end, the production process itself was a great bonding exercise. Nothing gels a team together like the shared sweat of a job well done!</p><p>A couple of iterations later, spiced up with the quirky illustrations in Benoît’s unmistakable style, we had a full deck. What can a Pictet collaborator find when they hold the deck in their hands? The cards are grouped into colour-coded series, of varying length, each colour representing a basic category of Agile competency, such as Collaboration or Organisation, through groups of behaviours linked intimately to the major events of an Agile team’s life, to technical topics of Software Craftsmanship. A series of cards in the same category has the same colour and can easily be extracted for a topical retrospective, for example. In a future article, we may explore one of the series in depth.</p><h4>What’s in a Card?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/881/1*2qxIAwJL4Q5tr1xtnOE0qA.png" /><figcaption>Front and back sides of a single card</figcaption></figure><p>What catches the eye immediately when looking at the front of a card is, of course, the quirky and inimitable illustration of the practice. Sometimes serious, sometimes tongue-in-cheek, always fun to look at. It’s accompanied by the name of the practice — that’s the bold card title, and by one-sentence which sometimes describes the practice in more detail, and sometimes provides just a supplement or a commentary about it. The top-right contains the card’s color-coded category. And of course, in the bottom-left is the card’s score.</p><p>The back of the card repeats the practice name and lists the behaviours that must be observed on the ground for the team to be able to say, “we are doing it”. Finally, each card is adorned with the logos of organisations involved in the whole exercise — Pictet Technologies Luxembourg and Lean &amp; Agile Coaches from Geneva, as well as the indication that the card can be shared under the Creative Commons licence.</p><h4>How to use the cards?</h4><p>In the most basic of uses, the deck of cards is an attractive, interesting object that all our collaborators receive on their desks. It piques their curiosity and they usually cannot wait to see what’s inside.</p><p>The next obvious application is that the cards are a learning tool. Open the box, flip the cards one-by-one, admire the illustrations, and ingest the Agile knowledge in light, bite-sized chunks.</p><p>It’s the more structured use, facilitated by the teams’ Scrum Masters and Agile Coaches that will be more powerful and useful to the teams. We expect all Scrum Masters to use these cards — typically one topical “colour” at a time — as either an icebreaker, or the main course of a retrospective, under the guise of assessing whether a team follows the practices described. The cards, being of a very graphical nature, lend themselves to being put on an online collaboration tool such as Mural, which leads to a tactile and visually rich retrospective experience, at least by the standards of our pandemic times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Y7MLb3_4vqOdgzgGxLlng.png" /><figcaption>A Mural board where teams can discuss the cards, slide them to the correct column and propose observations and actions related to each card.</figcaption></figure><p>We make it very clear from the beginning that the cards are not a one-way street: teams are free to discuss the practices as described, and decide that in their context it makes sense to follow a given practice only partially — or indeed, to “apply for an exception” from following it at all. This exercise achieves a two-way communication, as the collaborators learn what is expected from an Agile team, in the Pictet Group context, and at the same time the management can learn about the particulars of a given team’s situation, and whether they find it easy to follow the practices as prescribed. For off-hand ideas, each deck contains a card for new practice or suggestion to percolate bottom-up from the teams to the community of Scrum Masters or to the management.</p><p>Another level opens with the use of the points on the card. We gave each card a numeric value in points on a scale of 5 to 30, representing the relative value of the particular practice to the organisation, its importance in our vision of what an Agile Team should do. The sum of points for all the cards in the deck is 1000. This gives an easy-to-use scale of Agility on which the team can place itself after evaluating the whole deck of cards. It can also enable the team to establish what their weak and strong areas are, when the points of only one colour category are added. More importantly, it makes it possible to establish a baseline of where the team was after the first run through the deck, and then to follow the team’s progress — or perhaps even regression — as the cards are evaluated again and again, during subsequent retrospectives. Finally, we can compare the teams — not their velocity of course, but based on what their strong and weak points are, and how advanced they are in their journey to agility. As the community of Scrum Masters, we get to know which teams need more help, and which may serve as example to others. In the end, this maturity-score approach can be scaled to the whole organisation, giving our management an eagle-eye view of the teams’ landscape.</p><p>Does the scoring engender competition between the teams, or put undue pressure on them? In a way, yes, but it’s a healthy competition, because the teams know what they must do to improve, and the fact that it’s mediated by their Scrum Masters ensures that no team will be inclined to take shortcuts or to inflate their score in any way. The only way forward in the teams classification is — by doing the work necessary.</p><h4>The Cards as a Game</h4><p>With skilful facilitation by a Scrum Master, it’s even possible to turn the Agile Cards into a game. One way might be to distribute the cards from a deck between team members and ask them to trade them, to see which ones are valued the most and then imagine a team that follows these practices only. How would such a team work? Pit a mock sub-team organized with only a subset of the cards against another, organized with a different subset of the cards and ask the team to list the strong and weak points of each subset, and which sub-set they would actually prefer.</p><p>Or you could get inspired by card games such as Magic: The Gathering, and just play the cards against each other, individually, after they are distributed amongst the players. One way for a card to trump another would be just the straight score; but that’s not much better than pure randomness. Instead, with two cards placed on the table by two players, the other team members could discuss and decide, arbitrarily and in their team’s context, which card would be better than this one — and which player wins the exchange. The possibilities are endless!</p><h4>The Moral of the Story</h4><p>Today’s Agile coaches and Scrum Masters are overwhelmed with materials from which to draw inspiration: there is a plethora of books, blogs, videos and podcasts. There is also a lively conference scene and plenty of events to learn new tricks, tips and approaches. It’s not a bad reflex to have: when confronted with a new, challenging situation, to reach out in search of people who dealt with similar problems in the past. “We can see further if we stand on the shoulders of giants,” to paraphrase Isaac Newton himself.</p><p>On the other hand, in some organisations, over-reliance on authorities and Agile luminaries might lead to a sort of reverse “Not Invented Here” syndrome, where we trust our insights less than already existing solutions, even if the latter don’t fit our needs perfectly. With the Agile Cards, we flexed our innovation muscles and let us tell you — it’s a damn good feeling! Constructing the Agile Cards was not only stimulating on an intellectual level, but it also gave us a deep sense of satisfaction as we watched our own <em>product</em> grow and mature.</p><p>In the end, this is a call to you, dear reader — after getting to know our Agile Cards, <em>can you do us one better</em>?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42803fbfc89" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pictet-technologies-blog/agile-cards-a-fun-and-flexible-way-to-industrialise-and-standardise-2-3-42803fbfc89">Agile Cards: a Fun and Flexible Way to Industrialise and Standardise, 3/3</a> was originally published in <a href="https://medium.com/pictet-technologies-blog">Pictet Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Cards: a Fun and Flexible Way to Industrialise and Standardise, 2/3]]></title>
            <link>https://medium.com/pictet-technologies-blog/agile-cards-a-fun-and-flexible-way-to-industrialise-and-standardise-2-3-30cd2b3f8b79?source=rss-862bfedc4e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/30cd2b3f8b79</guid>
            <dc:creator><![CDATA[Tomasz Tarchała]]></dc:creator>
            <pubDate>Thu, 31 Mar 2022 11:43:12 GMT</pubDate>
            <atom:updated>2022-04-11T08:03:20.430Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is part two of a three-part article. The next instalment will come on April 14th.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*Z67zOQ8yvx3GysWXppGl5A.png" /></figure><h4>The Inspiration</h4><p>Remember how in <em>Karate Kid</em>, the young Daniel LaRusso was first told by Master Miyagi to wax the car and sand the wood, only to discover that he was in fact learning blocking movements? Shu-Ha-Ri is a way the Japanese think about learning martial arts: first you learn by memorization and rote repetition, without thinking too much about theory: just listen to your teacher (the Shu level). Later you get to know the theory and learn from how other practitioners do it (the Ha level), to widen your horizons. Finally, you analyse your own practice to tailor it to your needs and strengths (the Ri level). In terms of the Shu-Ha-Ri ladder of Agile competences, most of our constituency in the teams struggled to get on the Shu level. The Agile universe offers a wealth of literature, theories, polemics, and high-minded concepts. But what is Agile’s “wax-on, wax-off” instruction with which Master Miyagi built young Daniel’s muscle memory?</p><p>You want to tell rock star bankers and engineers to follow a blind, disciplined practice of the basics, you better make it fun. Looking for inspiration, we shuffled the documents for practices that we came up with before. When somebody printed them up 2x smaller to fit more on paper, then it hit us: each of these could be a card. And when you have many cards, you <em>can</em> make it a game! Even better, a game that you don’t have to play on a screen in a world already suffering from screen overload. What if we put into the hands of every member of our organisation a beautiful object, a deck of cards for a game that could be played with his or her teammates — and while playing, they would soak up the practices and ideas we wanted them to absorb?</p><p>With early cards, we tried out some rather high-level concepts such as “Test-First Development” or “Configuration Management” only to run into the same wall: there were too many possible interpretations. How to determine whether a team is doing “Micro-increments” properly? What does “Courage” even mean? The next critical insight was that we needed to focus on the <em>behaviours</em> rather than principles. Who cares what our principles are, if we don’t exhibit them, day in and day out, in specific actions on the ground? Thus, the basic design of the card was born: the practice or principle’s name stated on the front, whereas on the back we put the specifics, the details, signs, and evidence on how exactly to tell if the practice is working or not. (Incidentally, it’s also reminiscent of the classic 3x5 card design for a user story.)</p><p>It was quite a fun and stimulating exercise for everyone involved to determine these basic behavioural building blocks of our principles. We had to accommodate development and support teams, teams running Kanban, Scrum, and everything in between, teams with wildly differing release calendars, workflows and Definitions of Done; then extract the common elements of Agile mindset and put it down to something that be observed on the ground.</p><h4>One more creative spark</h4><p>How to make it more fun? One lucky strike for us was that we had the inimitable Benoît, a T-shaped developer you might say… for whom one of the T’s arms were drawing skills.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*CQc12RqYXPSlccV91C4lwQ.png" /></figure><p>His quirky illustrations for each practice were not only a perfect complement to the short, to-the-point descriptions of the behaviours we wanted. In fact, the quality of Benoît’s work pushed us to get the rest of the card’s design succinct and fun to match.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*o3IMbPrqggFtvLquL20ElA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*4mm5K6srpUW2mPfuxh74MQ.png" /><figcaption><em>A series of all the cards in a single category: the Daily Scrum</em></figcaption></figure><h4>What is Core?</h4><p>All this design fun couldn’t absolve us from deciding which practices to include and which to skip. Put a dozen Scrum Masters and Agile Coaches in the room and you will easily get literally hundreds of possible practices from all the world of Agility and all its odd relatives. To settle for only a few dozen (the total number of cards is 55) we had to make trade-offs. In the end, as in any self-growth exercise, it was not really about creativity; the creativity was in the form, but not in the contents. It was about productively hurting ourselves to stimulate growth. To pick the appropriate stimulus, we had to look deep into our own beliefs as Scrum Masters and reconcile them with what the management’s goals for the organisation were.</p><p>There was the nagging doubt hounding the project from its inception: are we just translating the Scrum Guide into the form of cards? And not only that, aren’t we setting ourselves up for the charge of “Scrum-But”, the anti-pattern often decried in Agile literature, where a team or organisation cherry-picks only the elements they want to keep and jettisons others?</p><p>In fact, this is not how we thought about it at all. We did not deny the value of any of the Scrum Guide’s elements, instead, we made a conscious choice as to which of them — and maybe others, from other Agile traditions — we needed for the Shu level of mastery. For ambitious team members and Scrum Masters, there will be plenty of time to reach the Ha and Ri levels, to discover the ideas we did not explicitly include in the cards. For the vines to reach for the sun, someone must prop up the vines with stakes first, and this is what we aimed to achieve with our cards.</p><p>Besides, as we admitted amongst ourselves as Scrum Masters with decades of experience between us, there is no such thing as “perfect” Scrum or Scrum implemented by the book. Everybody picks and chooses, and if we are to have a good Scrum-But rather than a perfect Scrum-Bad… so be it.</p><p>Does the stake curb the vine’s freedom to grow? Did we curb our teams’ freedom to learn as they pleased and in the direction they wanted? Yes, but that’s sort of the point: we can’t have a productive vineyard unless the vines orient toward the sun. In the end, it’s a learning process, and the cards propose one way that we decided to go for. Nothing prevents teams from trying other ways, as long as they are aligned with the organisation’s goals.</p><p><em>… to be continued in the final part three, check back on April 7th!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30cd2b3f8b79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pictet-technologies-blog/agile-cards-a-fun-and-flexible-way-to-industrialise-and-standardise-2-3-30cd2b3f8b79">Agile Cards: a Fun and Flexible Way to Industrialise and Standardise, 2/3</a> was originally published in <a href="https://medium.com/pictet-technologies-blog">Pictet Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Cards: a Fun and Flexible Way to Industrialise and Standardise, 1/3]]></title>
            <link>https://medium.com/pictet-technologies-blog/agile-cards-a-fun-and-flexible-way-to-industrialise-and-standardise-1-3-685beca29eb4?source=rss-862bfedc4e73------2</link>
            <guid isPermaLink="false">https://medium.com/p/685beca29eb4</guid>
            <category><![CDATA[card-game]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[scrum-agile]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[gamification-in-business]]></category>
            <dc:creator><![CDATA[Tomasz Tarchała]]></dc:creator>
            <pubDate>Thu, 17 Mar 2022 09:40:46 GMT</pubDate>
            <atom:updated>2022-03-18T14:35:26.315Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is part one of a three-part article. The next instalment will come on March 31.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*nmRSdnTANtua-HrKIu4QLw.jpeg" /></figure><p>Imagine Luxembourg airport at 6 a.m. on a frigid Thursday, in a pre-pandemic January, full of solemn-looking, suited-up guys. As Scrum Masters at Pictet Technologies, we were well used to getting up at this ungodly hour. Working at the scrappy new company whose mission was to turbocharge the Pictet Group’s software development, visiting our mothership in Geneva was part of the deal.</p><p>This time, the meeting ahead did not sound like a lot of fun, though: we were going to meet our sister group of Lean and Agile Coaches to decide which <em>Core Agile Practices</em> to standardise on. As a practicing Agilist, dear reader, you will easily detect the tension, and indeed, the paradox of what we were trying to do: shouldn’t Agile obviate the discussion of concepts such as processes and standardisation? Shouldn’t we <em>respond to change</em> rather than implement a rigid set of practices? And yet, we felt an urgent need to converge on <em>something</em>. Our mission was not just to transform an IT organisation of several hundred to work in an Agile manner. It was to take responsibility for the effects of this transformation, to consolidate and drive performance of each of our teams separately, and of the resulting “one-team” effect for which Pictet is famous. Each of the people we worked with was an accomplished professional in their field. How could we help them get there? How did we even know what ‘<em>there’</em> meant?</p><h4>The Call to a Standard</h4><p>To get our Agile teams off the ground, we had done all the obvious things first. We gave everyone an Agile Core training. We hired the Scrum Masters and Agile Coaches. Each of them brought his or her distinct personality and years of experience, which was a great strength. They started working with their assigned teams, but then something unexpected happened: our customers and collaborators were getting increasingly confused about what exactly they should be doing: they were getting different answers depending on whom they asked. While having a rigid <em>process</em>, enforced by <em>tools</em> and bureaucracy was the last thing on our mind, we started to suspect that there would be benefits in standardising on a core set of practices. If we wanted to know whether whatever we were doing worked, it would be hard to tell by performing a slightly different “n=1” experiment with each person and team.</p><p>Having a shared set of mandatory practices was important: that was a belief shared at the Group level, not just our own Agilist faith. It would enable us to know which parts of the organisation were more advanced in their transformation, and which required more help. Team members would be able to change teams without completely re-learning the way they worked. And as Scrum Masters and Agile Coaches, we wanted to be able to set our own roadmap.</p><p>So many goals! We came to the realisation that only a common set of practices could solve them all. We had to practice what we preached: we had to <em>self-organise</em>, so we got on a plane, and we got together.</p><h4>The False Dawn</h4><p>If you expected drama, shouting and fists banged on the table while we advocated for conflicting positions, you’re in for a disappointment. The meeting finished amicably, and we flew back home with a set of 11 practices we wanted to roll out, organisation-wide, in the coming year. The anti-climax came later: as it turned out, the devil was in the details. In the workshops and discussions that followed, we couldn’t agree ourselves on what it was <em>exactly</em> that each practice meant. Story splitting is a great idea, for example, but should we instruct our Product Owners to split the stories into sub-tasks, or to create small enough stories instead? Is “given-when-then” a valid format for a user story, or is it more suited for a test? If you code in a pair-programming session, do you still need a code review later? While we forged the compromises, the documentation and descriptions of the practices grew, full of nuances and exceptions… until it dawned on us: nobody was going to read this wall of text. It was the dreaded <em>comprehensive documentation</em>.</p><h4>The Drive</h4><p>We needed a way to get the practices across to people in a way that would be both comprehensible and fun.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*JciA349qVTOUbTkLROWS_w.jpeg" /></figure><p>Oh, and did we mention that we had another important goal in mind as the junior spin-off firm of Pictet Technologies? It was to establish our reputation. The Pictet Group is a storied brand, and it’s not easy to leave a mark on a firm established in 1805, a Rolls-Royce among private banks. Advertising ourselves to experts and engineers as experienced Agilists, we couldn’t just settle on an old boring set of Wiki pages saying, “you have to do that” and hope to change anyone’s behaviour. Working with teams full of rock stars, we needed to be what the famed rock producer George Martin was to the Beatles, and not the accountant nagging them about taxes.</p><p>Could we impress rather than oppress? Our company’s mission, our <em>raison d’être</em> was to innovate. Could we innovate our own way out of this?</p><p>We considered the various metro maps of Agile practices, produced by Agile Alliance, Deloitte, and just about anybody else wanting to stake a claim to leadership in the Agile world. Nice to look at, and perhaps interesting at the meta-level; but there were so many versions already that producing another one just for Pictet would just add to the noise. They gave the impression of complexity, too, which is precisely the opposite of what we wanted. If we struggled to understand them ourselves, as experienced Agilists, was that really a good way to guide our teams through the maze? Lastly, let’s not forget the famous remark by Korzybski, “the map is not the territory”. Knowing what to do <em>first</em> is not the same as knowing how to actually <em>do</em> it.</p><p><em>… to be continued in part two, check back on March 31st!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=685beca29eb4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pictet-technologies-blog/agile-cards-a-fun-and-flexible-way-to-industrialise-and-standardise-1-3-685beca29eb4">Agile Cards: a Fun and Flexible Way to Industrialise and Standardise, 1/3</a> was originally published in <a href="https://medium.com/pictet-technologies-blog">Pictet Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>