<?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 Peter Zylka-Greger on Medium]]></title>
        <description><![CDATA[Stories by Peter Zylka-Greger on Medium]]></description>
        <link>https://medium.com/@peter_89654?source=rss-b5d367332ea9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*d_oDyarVtA92EySqULl2Cw.jpeg</url>
            <title>Stories by Peter Zylka-Greger on Medium</title>
            <link>https://medium.com/@peter_89654?source=rss-b5d367332ea9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:48:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@peter_89654/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[The Challenge of Saying No as a Self-Employed Professional — My Story Of Finding My Own Path]]></title>
            <link>https://medium.com/@peter_89654/the-challenge-of-saying-no-as-a-self-employed-professional-my-story-of-finding-my-own-path-4637b48e6322?source=rss-b5d367332ea9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4637b48e6322</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[self-employment]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Peter Zylka-Greger]]></dc:creator>
            <pubDate>Wed, 07 Aug 2024 11:22:50 GMT</pubDate>
            <atom:updated>2024-08-07T11:22:50.617Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Challenge of Saying No as a Self-Employed Professional — My Story Of Finding My Own Path</h3><p>This is the most personal article I have written and published so far and it feels like the right thing to share this with a wider audience.</p><p>So here I am, taking you on a journey through time with me. I’ll let you in on stories I have been telling myself about the situation at hand. And I’ll give you a hint on the patterns that I suspected. All this while making some jumps in time — are you ready?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*p1G6NE0EOo6donfs.gif" /><figcaption>I promise, I limit myself to only 2 Taylor Swift graphics</figcaption></figure><h4>Where do I start? 2022 — let’s start there…</h4><p><em>What happened?</em></p><p>I decided to quit my corporate job and become self-employed again because I felt an intense pull to do more for the world. Exclusively working for just one company didn’t feel right anymore. Even though I absolutely loved what I was doing in my corporate job, I still felt very much limited in what else I wanted to do and I lacked the flexiblity of trying out new things.</p><p>In <strong><em>July 2022</em></strong>, I was fortunate that my former employer re-hired me for my first project right from the get-go. I was privileged enough that my networking efforts paid off, leading other companies and projects to reach out as well.</p><p>By <strong><em>September 2022</em></strong>, I was juggling 3–4 projects in parallel, working way more than 100%. And if that wasn’t enough, I also engaged in non-billable activities: hosting meetups, speaking at two conferences, and never turning down a 1:1 chat to help someone. I was also continually involved in some kind of training to up skill myself as I needed to stay interesting and fit for the market.</p><p><strong>The story I told myself</strong>: It’s fine. You love what you do, so it’s different for you. You can handle more than 100% — that limit is only for those who don’t enjoy their work. Stay focused and things will work out.</p><p><strong>The pattern I suspected</strong>: The typical fear of a self-employed person. Take all the work you can get while the opportunity exists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AuTquHvZcqY_Zxx8" /></figure><p>Fast forward to <strong><em>January 2023</em></strong>: By November, I realized that I do have a limit of what I’m capable of doing.</p><p>How did I notice?</p><p>I was no longer present, missing meetings, and had days when I traveled to three different customer sites within four hours, spending more time travelling than working. I also did notice a change within myself: I became very impatient, frequently complained about everyone but myself, and was often set off by situations that occured at my customer. With the nature of my own inner self, I was also less capable of helping others around me as internally I was absorbed with making sure that I stay “ok” and given that I wasn’t ok, it became harder for me to support others.</p><p><strong>The story I told myself</strong>: It seems you are human after all. You can’t do it all. Maybe it’s a good time to practice what you preach to organisations and teams and limit the time you spend working with customers.</p><p><strong>The pattern I suspected</strong>: I tend to run when things go wrong and blame others.</p><blockquote>If they would only provide a good working environment, everything would be easier. — a sentence I loved to say to myself a lot of times</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/0*Dx-sPr3QijKgeUW7" /><figcaption>It’s the easy way out</figcaption></figure><p><strong>The rest of 2023</strong>: I decided to limit my projects to a maximum of two, a very healthy decision but not an easy one for me to take.</p><p>Was my WIP problem solved?</p><p>Heck no!</p><p>Instead of projects, I now said “Yes” to all other requests: coaching engagements, workshop engagements, and of course, I continued working on my networking, spending a lot of time after work at meetups and meeting people.</p><p><strong>The story I told myself</strong>: That’s just how being self-employed works. Maybe a permanent position is better than you thought. And remember, it wasn’t all bad while being permanent. The security you have, the paid leave, not worrying about your next gig — and a little bit of “status quo” can’t be that bad, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*AVwwxfUMdfsoDtNT.jpg" /><figcaption>The most fitting picture for this….</figcaption></figure><p><strong>The pattern I suspected</strong>: I like the excitement of new things, so that’s probably where the root cause of all this lies. So, I most likely just repeated the mistake many of my teams focus on: never addressing the root cause, only the symptoms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*0R06EFi9ytqDqm0k.jpeg" /><figcaption>Yoda and root cause — find a better combo</figcaption></figure><p><strong>Fast forward to April 2024</strong>: That root cause thing didn’t really work out for me.</p><p>The same patterns repeat. I am busy and unwilling to say “No” to requests. I still have only two “official” WIP projects, but tons of other WIP on the side.</p><p><strong>The story I told myself</strong>: The same old story I’ve told myself over the years. Becoming grumpy, bitter and frustrated with myself and those around me.</p><p><strong>The pattern I suspected</strong>: A highlight reel of all the patterns I’ve identified over the years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9-2-xARW4eVT1vha" /><figcaption>Only bad if these habits exist for decades…</figcaption></figure><p>Now, let me take you to today and especially to April.</p><p><strong><em>What happened in April?</em></strong></p><p>And let me now use my second and last Taylor Swift quote:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J2pgXTWoqD7QpowR" /></figure><p>Thanks to Taylor for providing the perfect lyric to describe what I went through. As some of you already know, I spent almost two weeks at the <a href="https://evolve2b.com/academy-evolutionary-leadership/">Academy of Evolutionary Leadership of Evolve2B</a> in the US with Audree and Michael Sahota who are very close to me and whom I consider as the biggest influences in my life.</p><p>What I discovered about myself there was very profound to my self-employment journey:</p><p>The stories I told myself were not actually me telling stories, but rather the egoistic part of me that felt quite comfortable in the situation and enjoyed running into the same issues repeatedly. (Side note: These issues did not start when I became self-employed)</p><p><strong>This time, I will not share a pattern, but rather the profound root cause I have discovered for my WIP problem (and not only my WIP limit)</strong>:</p><p>I did not feel any self-worth or that I was good enough. Hence, whatever opportunity came my way, there was this pull towards it as I thought it was a very unique opportunity that I should enjoy before people discovered that I’m not good enough. I was falling into a trap that I was too blind to see and didn’t have the knowledge and/or didn’t know how to action the small points of awareness I had. My obsession with upskilling comes from the same place — I needed to constantly upskill myself to feel worthy, only to start the next training immediately after finishing the previous one.</p><p>This discovery was the most relieving I’ve had in my life. In the months since returning from the Academy, I have noticed for the first time in a very long time how I said “No” to requests and felt good about it.</p><p>Similarly, the urge to start something new is not strong anymore, and I felt like my last weeks were the most balanced I have had in years. I feel like I’m in control for the very first time over my WIP and have not the WIP control me. Sleeping over things and not making a decision on the spot became my new super power.</p><p>Even writing this article was on my to-do column for a longer time but I just waited until it felt like the right time to write it and it came in a moment where I felt the need to do something creative.</p><p><strong>The future…</strong></p><p>Unfortunately, I can’t take you into the future. I haven’t discovered that magic power within me yet, but what I can say is that I’m confident about it and at the same time realistic that I will still fall into a trap from time to time which will be treated as a great learning point as I’m pretty sure that there is still more out there for me to learn about myself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4637b48e6322" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working with Obeya — an experience report]]></title>
            <link>https://medium.com/@peter_89654/working-with-obeya-an-experience-report-22ae02f205e6?source=rss-b5d367332ea9------2</link>
            <guid isPermaLink="false">https://medium.com/p/22ae02f205e6</guid>
            <category><![CDATA[visual-management]]></category>
            <category><![CDATA[transparency]]></category>
            <category><![CDATA[visual-management-systems]]></category>
            <category><![CDATA[obeya]]></category>
            <dc:creator><![CDATA[Peter Zylka-Greger]]></dc:creator>
            <pubDate>Wed, 12 Jun 2024 15:42:28 GMT</pubDate>
            <atom:updated>2024-06-12T15:42:28.804Z</atom:updated>
            <content:encoded><![CDATA[<h3>Working with Obeya — an experience report</h3><p>In this blog, I’d like to share my experience with using Obeya at a customer. This will include a brief introduction to what Obeya is, how I came across it many years ago, how I have experienced it without realizing it, how I re-discovered it, started to love it, had success with it, and how it eventually became Flowbeya.</p><p>If this sounds appealing to you, read on!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*YRQ0gcjd207GuvYA.jpg" /></figure><h3>Obeya — a Definition</h3><blockquote>A physical and/or digital space where strategy meets execution. The Obeya approach builds alignment and ownership across diverse groups of stakeholders to solve complex problems, drive cultural change, and get work done. — Obeya Association</blockquote><p>Speaking of complex problems: The Obeya approach was pioneered during the development of the Prius in the 1990s. Toyota’s Chief Engineer, Takeshi Uchiyamada, recognized the need for a more collaborative and transparent environment to manage the complexities and challenges of the Prius project. The word “Obeya” means “big room” in Japanese, and it reflects the physical and metaphorical space where cross-functional teams gather to synchronize their efforts and drive project success.</p><p>Toyota’s implementation of Obeya involved creating a dedicated room where team members from different departments could come together, share information, make decisions, and solve problems in real-time.</p><p>In my own words, I usually explain Obeya as a visual management system that makes information accessible to the people that need it. In addition, I usually get super excited talking about it.</p><h3>My First Contact with Obeya</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*ytq1HX5FKdFd4nqp" /><figcaption>Good old times….</figcaption></figure><p>Do you know when you connect with a topic and then out of nowhere have this feeling of “Wait a second — I have heard this before”? This is how it went for me with Obeya when I came into contact with it this year. And while it took me some time to realize where I had heard of it before, now I know that it was in 2018 during the Global Scrum Gathering in London where Leonoor Koomen, in her talk about ING’s cultural transformation, mentioned how they introduced an Obeya room, with a change wall, a run wall, a performance wall, and an improvement wall. And how the Obeya room was their one place to build high alignment.</p><p>While I remember the talk being one of my favorites during the conference, other topics seemed more important to me at that time.</p><p>While going through memory lane, I made another stop. This time a year later and I thought to myself: Wait a second! You have experienced an Obeya before, you just didn’t realize it.</p><h3>My First Experience with Obeya</h3><p>It was during my time in Australia in 2019 — we were working in a pretty amazing team and as all of this was pre-covid, we were in the office five days a week. And because we were an amazing team, no one actually had to force us to do this. In addition, we also had a pretty cool office space where the entire team (approx. 25 people) could sit together and even have their own private meeting room. This meeting room was special, though, and was quite different from the rooms I knew back then.</p><p>It had:</p><ul><li>A single big dry-erase table</li><li>Standing stools</li><li>Walls consisting of only whiteboards</li><li>Lots of space to move around</li></ul><p>This allowed us to use it whenever a working session was necessary. Usually, people very quickly started visualizing their thoughts on the table, exchanging ideas, discussing better ways to solve a problem, and so on.</p><p>All this was supported by the information on the walls. The walls were divided like this:</p><p>Wall 1:</p><ul><li>Product Strategy</li><li>Customer Journey</li><li>Current hypotheses we experiment with</li></ul><p>Wall 2:</p><ul><li>Current problems we address from a tech standpoint</li><li>Problems we will need to address</li><li>Any other ideas that were related to tech (drawings, etc. visible)</li></ul><p>Wall 3:</p><ul><li>Operational downtime</li><li>Any other metric that was important to us</li></ul><p>Wall 4:</p><ul><li>Everything that was related to improving the way we work</li><li>Action items from the Retrospective</li><li>Ideas on what to improve next</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hqK2A2zpLJjLN-zXGogpEw.jpeg" /><figcaption>This is how the room looked like from one side…and you see our pretty cool screens on the outside and some colleagues who probably just had discussions about something they saw on the other walls.</figcaption></figure><p>I think it is fair to say that we were quite a visual team and used a lot of visual triggers to collaborate together. Only years later did I actually realize that we had been using an Obeya. I just can’t recall us ever using the term and knowing what we did. But in hindsight, I saw how it helped shape the team and turn us into a high-performing one. The room also served us as a “training camp” for every new joiner — they usually spent two days in the room at the start of their journey with us, understanding the concept of the team, the product, operations, and tech. And usually spent plenty of time in the room afterward having conversations with other people pointing at the walls.</p><p>Interestingly enough, the walls didn’t just serve the team, but also became regularly visited by other people in the company: Sales, C-Level, Marketing, or generally people who were interested in what we did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2umsrhEJA9hLud9Puzh0TQ.png" /><figcaption>We also had pretty cool digital screens in the office</figcaption></figure><h3>My Re-discovery of Obeya</h3><p>This is a rather easy one. I re-discovered Obeya while reading Jim Benson’s <em>Collaboration Equation</em>.</p><p><a href="https://www.goodreads.com/book/show/62796385-the-collaboration-equation">The Collaboration Equation: Strong Professionals Strong...</a></p><p>Obeya is mentioned a lot of times while Jim shares his amazing insights and gives examples of how it has helped groups to work together and use the Obeya as a Visual Management System.</p><p>If you haven’t read the book yet, this is a heartfelt recommendation to put it on your summer reading list. See also my other blog post on this topic:</p><p><a href="https://medium.com/@peter_89654/getting-a-team-out-of-learned-helplessness-using-flow-metrics-a-case-study-e2ef886838c4">Getting a team out of learned helplessness using Flow Metrics — a Case Study</a></p><p>The book inspired me to look more into it. What helped was that in most of my projects I was seeing a repeating pattern: Information was not being made available to the people who needed them. Or if information was available, it took people a lot of time to find it, with information being buried somewhere in a Wiki.</p><p>“There is no information on this.”</p><p>“Sure there is.”</p><p>“Where?”</p><p>“In our Wiki.”</p><p><em>*searches for 10 minutes…</em></p><p>“Here it is — you just have to enter xyz (add any search term that has little to do with what you are actually looking for), skip the outdated version of it, click another five links and you have the information you require.”</p><p>I have been part of many conversations like these.</p><p>Fact is, I’m only exaggerating slightly. In most companies nowadays, information is indeed available, but it is not being made available in an easy way and therefore, a lot of times, doesn’t reach the right audience. This goes both ways, by the way.</p><p>So here I was, with a real problem at hand and a potential solution to the problem.</p><h3>Get Started</h3><p>Now that you have a solid understanding of what got me here, it is time to share my experience with using Obeya.</p><p>Before I got started, I dug deeper into the topic of Obeya.</p><p>Checking out the content at the Obeya Association (highly recommend what they have on their page) and then thought to myself, why not just start?</p><p>Luckily for me, one of my customers was very open to the idea and considered the risk of trying it out as only very minimal.</p><p>A couple of considerations I had to make first:</p><ul><li>The Obeya needed to work on a virtual Whiteboard as Miro is the go-to tool.</li><li>Several teams, specialized departments, and the managing line needed to be part of it.</li><li>Not everyone would fall in love with this approach right away, so I needed a way to inspire people to use the Obeya.</li><li>I had the challenge of multiple tools being used: Notion, Wiki, Jira, Miro.</li></ul><p>Instead of trying to find a solution for all these challenges, I decided to start small. I created a first draft sketch on Miro of an Obeya and filled it out with some random data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EFqIFx8mum6brprnD3eHtw.png" /><figcaption>The very first sketch — moving from strategy to implementation</figcaption></figure><p>With this sketch, I set up various calls with people in the company. Mostly people I considered open and interested in such an approach. I quickly explained the concept behind it, what they see, what the potential of this is, listened to their feedback, and asked them additionally what else could be useful to display here.</p><p>It turned out people liked the idea. The only worry they had was that it would take some effort to establish it.</p><p>After every conversation, I updated the Obeya. And it started to look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*TafMWFLjXJMdN6nghKiuJw.png" /></figure><p>Once I finished the rounds with the people I considered interested, I tested the waters with those I considered less enthusiastic about a whiteboard. So I had to up my game for this. I was considering how they could benefit from it, based on their roles and was adjusting the Obeya. And I figured to go where it hurts. What kind of information was important to these people and their roles and which information is difficult for them to find. Once I figured it out, I placed the information on the Obeya and started the round of conversations.</p><p>With a very surprising result: It turns out, people are really amazed if you can reduce their time of looking for information.</p><h3>Let’s Try This Out</h3><p>While having an Obeya was not on the roadmap for the engagement I was in, the decision-makers in the company decided to give this a go. It was relatively quick to set up a first version of an Obeya, given the feedback received.</p><p>The starting Obeya looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sGWZlLZefweQbO_13hDzJg.png" /></figure><p>What you see here is a modified template available in the Miroverse.</p><p>At the bottom top left:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t1qmYlSfD9_bgtHe1wwOxw.png" /></figure><p>The strategic paper with its strategic capabilities, followed by measures of performance, tough problems and a Plan to Value timeline. Cards on this timeline were explaining the delivered usable value.</p><p>Below you see 4 areas:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/1*3ZYsHxBMISYlsq_5Ui9iNw.png" /></figure><p>These are the Delivery Team areas. What is placed here is:</p><ul><li>Topics for their daily huddle</li><li>ideas how to improve their work system</li><li>improvements in progress</li><li>a snapshot on the topics they currently work on</li><li>Constraints to completing their work</li><li>Data (more on this will follow)</li></ul><p>Just right next to the Strategic delivery board, you’ll find the wall that captured ideas, improvements, requests or decisions that needed to be made in order to drive value and remove blockages/impediments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*2pQqtLxVZ8Ywzbb8ztflog.png" /></figure><p>And the last piece is the community piece:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*ylvq-6Y2fmA5Ox7r-PZQCQ.png" /></figure><p>This is where people outside of the delivery teams, were able to put their input in that in return helped the teams to communicate asynchronously with them.</p><p>And then suddenly Obeya became a thing in the company. How was it used?</p><ul><li>It was used to see how the strategy of the company is being driven.</li><li>People started communicating asynchronously where necessary on the Obeya.</li><li>Questions, ideas, and challenges were raised in the boards of the teams or the communities.</li><li>Important notes from meetings were placed in the Obeya for others to see and be aware of.</li><li>Teams started to use the Obeya for their daily huddles as topics were placed there beforehand.</li></ul><p>Generally, everyone was quite happy with how it started. It was an interesting position for me as an external consultant. I was not as much needed anymore, as a lot of communication and collaboration simply started to happen. All I saw were updates on the board and even though I was not involved in the day-to-day business, I was able to keep a good overview of what was going on in the organization. That was a good sign to me!</p><p>Without any guidance, people also started using icons to make sure that information that was important was immediately visible to others — see exclamation marks or orange-colored stickies.</p><h3>The Birth of Flowbeya</h3><p>Probably the most exciting development in my journey with Obeya was the evolution into Flowbeya. This transformation happened when I started integrating Flow Metrics and Monte Carlo simulations into the Obeya.</p><h3>Monte Carlo Simulations and Strategic Capabilities</h3><p>Monte Carlo simulations allowed us to forecast delivery dates and visualize progress on the strategic walls of the Obeya. This transparency helped teams and stakeholders make more informed decisions based on data rather than guesswork.</p><p>The Obeya looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SZN0PlBhjrQQbbNuX-EA2w.png" /><figcaption>The black colored boxes below the value cards demonstrate the Monte Carlo Simulations. (All simulations were generated with the script provided here: <a href="https://github.com/LetPeopleWork/MonteCarloCSV">https://github.com/LetPeopleWork/MonteCarloCSV</a>)</figcaption></figure><h3>Enhancing Conversations with Data</h3><p>The data displayed in Flowbeya transformed how conversations happened in the organization. With clear visualizations of Flow Metrics and forecasted milestones, discussions became more focused and productive. Teams could:</p><ul><li>Prioritize Effectively: By seeing which initiatives were at risk of delay, teams could reprioritise to ensure critical projects stayed on track.</li><li>Identify Dependencies: Dependencies between teams were made visible, allowing for better coordination and collaborative problem-solving.</li><li>Drive Continuous Improvement: With transparent data on their performance, teams could identify areas for improvement and track their progress over time.</li><li>Facilitate Strategic Discussions: The leadership used the Obeya to align on strategic priorities and make data-informed decisions.</li></ul><p>The transparency of the Flow Metrics (see ProKanban.org for more on Flow Metrics) of the different teams brought a different aspect to it. It allowed teams to communicate with each other about what they were doing differently in their work. Teams started to discuss how they were slicing their work so that it could fit into a cycle time of 10 days or less(85th percentile) and generally started to work more with each other and looking beyond their team boundaries. Dependencies were made visible, addressed by placing a sticky note in the space of a specific team and rather discussed ad-hoc instead of waiting for a meeting to happen.</p><p>The data of each team was visible at the bottom of each area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KJTKdSSRqUmrANwEwLjG0w.png" /></figure><p>Another thing that was introduced was the idea of focusing on continuous improvement and getting rid of scheduled improvement sessions (Looking at you, Retrospectives). Teams were open to experiment using a more frequent cadence (2x a week for 30 minutes) and placing their challenges on the Obeya upfront and discussing them latest in the meeting that was called a hybrid of Obeya’s “Deliver Value/Act &amp; Respond” meeting routine. This didn’t work for all the teams though — some returned to a different cadence. For those that it worked for though, it helped them to action more of their improvements, get decisions faster than in the past and in one specific case, getting help from a part of the organization they didn’t expect (a managing director picking up an item on the board and supporting the team in getting access to what they needed).</p><p>The Obeya grew with time and there are areas that containted more information, exchanges and data (including a pretty cool integration of the companys ticket tracking tool), but due to confidentiality I’m not able to share any picture here.</p><h3>Easy Peezy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/0*ECBOtB35w4ULm1Kw" /></figure><p>While all of this sounds amazing, things are never perfect, especially not when humans are involved — is there a pattern, maybe?</p><p>It required a lot of effort to keep this thing going at the beginning. People get used quickly to have someone do everything for them, updating the data, keeping it clean, etc.</p><p>In hindsight, I would have started earlier to find people interested in taking over certain aspects of it.</p><p>Not everyone loved it. Which nowadays I consider normal. But instead of focusing too much on the ones who did not like the approach, I was trying to give my attention to those who saw a big opportunity in this and experienced how it made their day-to-day easier as Jim Benson’s quote came into full swing: “Give professionals information they need to be professionals.”</p><p>And one thing I had to learn as well was that a template is just a template. There is no one-size-fits-all Obeya that you can simply copy and paste, so the magic was really in taking the time to co-create the Obeya together with the people involved. Still it was very helpful to have access to templates on the Miroverse, this way I didn’t have to start from scratch:</p><p><a href="https://miro.com/miroverse/">Miroverse | Miro Community Templates Gallery</a></p><p>Transparency is scary. With the Flowbeya aspect, something new was introduced into the company — data was made visible and accessible to all the people. While this was scary at the beginning and I was even warned that this will be totally used against the teams, the worst nightmares did not come true. The data was used in a very professional manner and no team was compared to the other, but rather the teams used it as a learning opportunity themselves and it brought departments and different levels within the organization closer together.</p><h3>Situation Now</h3><p>Even though my involvement is only minimal, the Obeya is still being used very actively. Things are being moved, removed and color-coding seems to be a habit in the organization now.</p><p>It’s especially exciting seeing how milestones have been delivered and how more and more people within the company got interested in the concept of Obeya.</p><h3>How to Get Started Yourself?</h3><p>My biggest suggestion would really be, to just start. Get yourself familiar with the concept of it — by visiting the mentioned resources in this article and find a way to test it. Maybe even just with your own team and asking the question: What kind of information is needed for us to act like professionals at work?</p><p>From the answers, you might already have a good starting point for your first Obeya version.</p><p>Iterate from there, share it with others, spread the successes and wait for others to approach you and ask you what this thing is you are doing there.</p><p>And expand as needed.</p><p>To find out more about Obeya, I can highly recommend to visit the website of the Obeya Assocation:</p><p><a href="https://obeya-association.com/">https://obeya-association.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22ae02f205e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reality check through scatter plotting]]></title>
            <link>https://medium.com/@peter_89654/reality-check-through-scatter-plotting-6a476523c699?source=rss-b5d367332ea9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a476523c699</guid>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[estimations]]></category>
            <category><![CDATA[story-points]]></category>
            <category><![CDATA[scatter-plots]]></category>
            <category><![CDATA[flow]]></category>
            <dc:creator><![CDATA[Peter Zylka-Greger]]></dc:creator>
            <pubDate>Thu, 29 Feb 2024 13:48:02 GMT</pubDate>
            <atom:updated>2024-02-29T13:48:02.338Z</atom:updated>
            <content:encoded><![CDATA[<p>There is a lot of noise out there in the daily life of companies — especially if you are part of a big corporate. By now, most have undergone at least one transformation and have adopted some form of an agile framework including several tools that come with it — regardless if useful or not.</p><p>Fact is: These tools are being used and if you are one of the lucky ones who works in a proper product driven company, this article is potentially not as useful to you.</p><p>In this article I’d like to share examples of how I have seen one particular tool used and how a simple method helped to open discussions that were not possible before. It’s something that I would encourage everyone using the tool to try out for themselves.</p><p>The tool I’m talking about is of course:</p><p><strong>STORY POINTS</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nVkP7s60KtECy-qE.png" /></figure><p>What are Story Points anyway?</p><p>According to Atlassian:</p><blockquote>Story points are units of measure for expressing an estimate of the overall effort required to fully implement a product backlog item or any other piece of work. Teams assign story points relative to work complexity, the amount of work, and risk or uncertainty. Values are assigned to more effectively break down work into smaller pieces, so they can address uncertainty. Over time, this helps teams understand how much they can achieve in a period of time and builds consensus and commitment to the solution. It may sound counter-intuitive, but this abstraction is actually helpful because it pushes the team to make tougher decisions around the difficulty of work.</blockquote><p>And even though not required by a framework like Scrum, most teams I have come across do use Story Points and some form or Planning Poker to align on the effort that team members think a specific work item will require.</p><p>And while this conversation can be useful, in a lot of teams it ends up being fruitless conversations about “Is this 2 or 3 Story Points?”</p><p>Other frameworks, like a famous scaling framework proposes the idea of “normalized Story Points” to help predicting the story point size for Epics and Features — meaning find a story that requires 1/2 day for coding and 1/2 for testing and call this story your “1 Story Point” work item. Then give every developer or tester in your team 8 Story Points to work on during an iteration and off you go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/0*nmlW2I-dbUgGSYTI.jpg" /><figcaption>Another meme cause…there are so many</figcaption></figure><p><strong>The ugly mess</strong></p><p>When joining companies nowadays and hearing about the organization using Story Points, I have to admit that my alarm bells are going off.</p><p>The first thing I do is to check the understanding of what Story Points mean, so I usually ask the open question: “What are Story Points to you?”</p><p>What comes next is usually a mixture of all the things stated above and “but we are not taking complexity into account, right?” is being shared every single time in these conversations. Which then usually leads to more proof that the understanding of what is even being done is not aligned within teams and companies.</p><p>I usually then try to throw Ron Jeffries into the mix and sharing that the person who invented Story Points even apologized for it.</p><blockquote><em>I like to say that I may have invented story points, and if I did, I’m sorry now. Let’s explore my current thinking on story points. At least one of us is interested in what I think. — </em><a href="https://ronjeffries.com/articles/019-01ff/story-points/Index.html">https://ronjeffries.com/articles/019-01ff/story-points/Index.html</a></blockquote><p>But it seems like the arguments and ideas in the article by Jeffries were still not good enough.</p><p><strong>Go where it hurts</strong></p><p>So my next move was usually to see what benefits companies see in using Story Points to estimate OR where they become a challenge — and very quickly you saw an ugly picture of velocities being (mis)-used to predict the future of teams.</p><p>Be it for Sprint Planning, the quarterly planning or to predict when an important feature/milestone will be reached.</p><p>I have seen a lot:</p><ul><li>Teams tweaking their velocity because humans know how to trick a system</li><li>Complex Excel Sheets in which the Average Base Velocity was being calculated and then mapped to the availability of team members</li><li>Re-estimating a story during the sprint closing</li><li>Weeks spent on getting the capacity and story points estimates into a tool for an entire quarter</li></ul><p>But what almost all teams and organizations had in common was:</p><p>There was some dissatisfaction on the management level about what teams commited to deliver vs. what they delivered</p><p>This usually led to statements like:</p><blockquote>“Teams need to estimate better.”</blockquote><blockquote>“They need to spend more time on refining the stories.”</blockquote><blockquote>“The preparation week needs to be extended (for quarterly plannings).”</blockquote><blockquote>“We need more Agile Coaches.”</blockquote><blockquote>“We need more team members”</blockquote><p>And I could probably go on for even more. At the same time I was not able to get my message across that these things will not necessarily improve the situation, for different reasons. What I was lacking was a visual system that would give me a seat at the table to discuss what is going wrong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*djyvRnMND16II3FG.gif" /></figure><p><strong>Scatterplot to the rescue</strong></p><p>“Have you tried putting the Story Points on a Scatterplot and mapping Cycle Time to it?”</p><p>“Well you know….No”</p><p>This is at least how a conversation between Benjamin Huser-Berta and I must have looked like.</p><p>But my answer was honest — I have never even thought about the option of actually reflecting back on estimates and mapping them to Cycle Time.</p><p>You might wonder, what do you mean by Cycle Time?</p><blockquote><strong><em>Cycle Time:</em></strong><em> The amount of elapsed time between when a work item started and when a work item finished.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/0*sjNKRYie4naHai1B.jpg" /><figcaption>Not me — months ago…</figcaption></figure><p>And here is the thing: Using data was not something I was very fond of in the past. I have considered myself as someone who is simply not interested in it and therefore protected myself from ever digging into it — in Coaching we would probably call it “limiting belief”.</p><p>But here I was mapping Story Points to Cycle Time and the results I got were: <strong>SHOCKING</strong></p><p>You would assume that there is some correlation between story points and time. Not always, as there is variance in complex work. But in general, you would assume that a 13 takes longer than an 8, which takes longer than a 2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6H-t-pQ7crnXsD1UtA6vhQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sAA6dttP_41IHBT6RPvnaQ.png" /></figure><p>Most of the Scatterplots looked like the ones above, they showcased there was almost no relationship between estimated Story Points and the Cycle time.</p><p>And this was indeed a problem as these organizations used the “normalized story point” approach.</p><p>So whenever they did plan their quarter, their firm belief was:</p><p>1 Story Point = 1 day of work</p><p>Only to find out by the end of the quarter that their delivery rate was again not even close to their desired goal.</p><p>As we can see in the 2 Scatterplots, 2 Story Points could mean a range from a few days of Cycle times up to almost 160 days. Or that a Story estimated with 10 Story Points could take just as much time as a Story with 1,2 or whatever number of Story Points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CQGhHfI92eGVNWFUd_vhFQ.png" /><figcaption>Generated with our script: <a href="https://github.com/LetPeopleWork/FlowMetricsCSV">https://github.com/LetPeopleWork/FlowMetricsCSV</a></figcaption></figure><p>And this was not a localised problem but something I can see happening for a lot of teams, regardless of the framework they are working as seen in the scatterplot above. A team working with Scrum and wondering why they are not able to finish what they plan to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xuLEDftY79R6EnSrFovG7Q.png" /><figcaption>Generated with our script: <a href="https://github.com/LetPeopleWork/FlowMetricsCSV">https://github.com/LetPeopleWork/FlowMetricsCSV</a></figcaption></figure><p>A conversation about how their cycle time (85th percentile) is 20 days or less, allowed us to have a good conversation on why this team is struggling to finish things in a 2 week sprint. A conversation about, what we can learn from the other items (below the red line).</p><p><strong>Seat at the table</strong></p><p>And this to me is the real magic and proved me with a valuable lesson for the future: Visualizing something fosters dialogues and conversations about what matters.</p><p>Bringing this scatterplot into meetings with management and teams shifted the conversation from:</p><p>“They need to estimate better.”</p><p>to</p><p>“We might have a systemic issue here.”</p><p>With very little effort, we were able to give people visualized information they were able to base their conversations on. It was not information they all individually had in their heads, but it was visible on their screens, in their meeting rooms and finally a dialogue was made possible.</p><p>The visualization helped to understand what was happening in the system and why this department was getting the results they were getting.</p><p>We gave them an idea of their reality.</p><p><strong>My recommendation</strong></p><p>It’s very tempting in a situation like this to now hire experts and have them work with the team to improve Estimates and work on the symptom. As written in another article, this is also the go-to move for most companies. Start looking for who is accountable for the situation, change people, change managers, keep everyone busy and generate a new kind of noise which will probably dilute the issue at hand for moment.</p><p>In a situation like this, my recommendation is and was to start looking into what you already have. Look for patterns that look different, see what you can learn out of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ASBbSmOIkMPwz3WrXk7TCA.png" /></figure><p>Like with the team above — we can see that this team was able to finish most of their work items in 10 days or less. Go and talk to the team — what do they do differently? What can we now do with this information? Is this a concept that would help us with the challenge at hand?</p><p>Once you have the conversation, you can bring in different ideas which yes, could include paying closer attention to Flow Metrics and using your Throughput to do Monte Carlo Simulations that will give you a better prediction.</p><p><strong>Try it out for yourself</strong></p><p>If you are in a environment in which Story Points are being used to predict the future (sprint plannings, Quarterly Planning etc.):</p><p>Take a look at the script we provide at LetPeople.Work:</p><p><a href="https://github.com/LetPeopleWork/FlowMetricsCSV">GitHub - LetPeopleWork/FlowMetricsCSV</a></p><p>Within our FlowMetricsCSV you can extract your issues from your working tool and create a Scatterplot with your data.</p><p>If python is too tricky for you (Trust me though, you can do it, even I’m able to do it):</p><p>You can also do it manually and extract your completed issues from the last quarter into an Excel file-take the Cycle Time and Story Points for your input and create a Scatterplot in Excel.</p><p>Using Scatterplots gave and still gives me a lot of answers on why certain things do not work for teams and organizations — i.e. a cycle time of 19 or days or less (85th percentile) for teams that work in a 2 week sprint, says a lot about why a team is not able to finish their tasks within a specific time frame.</p><p>As stated above: It gives us a glimpse into reality and opens doors for fruitful conversations.</p><p><strong>Use what makes sense but do not lose sight on alternatives</strong></p><p>And hear me out: I don’t ask anyone to stop doing something that works for them. If you are using Story Points (or any other form of estimation) and it works for you and your teams, good job. Keep it going, keep reflecting and listen to the feedback you get from inside and the outside.</p><p>Also if you read the article and think: What is he even talking about? We do proper product development, we work closely together, work quickly to verify assumptions and then get on with the work that is upcoming and do not even waste our time thinking what happens in 2 weeks, let alone 3 months, I’m really happy for you and the work environment you seem to work in.</p><p>My reality though is that there is still a big demand for predictability in companies (especially bigger ones) and I’d ask everyone to be curious about other options to predict what can be done and when something can be done.</p><p>Some useful resources can be found here:</p><p><a href="https://www.letpeople.work/blog">https://www.letpeople.work/blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a476523c699" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Feel-Good Folder]]></title>
            <link>https://medium.com/@peter_89654/the-feel-good-folder-c41103a59932?source=rss-b5d367332ea9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c41103a59932</guid>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[positive-thinking]]></category>
            <dc:creator><![CDATA[Peter Zylka-Greger]]></dc:creator>
            <pubDate>Tue, 23 Jan 2024 07:09:49 GMT</pubDate>
            <atom:updated>2024-01-23T07:09:49.917Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Simple Strategy to Demonstrate your Self-Worth to Yourself</h4><p>“I love working with people”</p><p>is a statement I can sign without any hesitation. In my day-to-day work, I usually spend most of my time collaborating with others, mentoring, coaching, or simply interacting with them.</p><p>And while it brings me a lot of energy and joy, the complexity of humans also brings doubts — doubts about the worthiness of doing this, the value of it, and more importantly, the ability to do it.</p><p>Especially the last point occasionally comes up for me. I’d like to introduce you to my favorite tool for when that tiny demon of doubt asks, “Don’t you see — you’re not contributing anything to those around you.”</p><p>I’ll include quotes by Adam Grant in this article, as his book was a great read for understanding how we humans function.</p><p><a href="https://www.goodreads.com/book/show/157095669-hidden-potential">Hidden Potential: The Science of Achieving Greater Thin...</a></p><p><strong>But first…</strong></p><p>Working with humans is complex — I’m usually careful with facts, but to me, this feels true and is something I deeply respect. Take yourself as an example: You’re here, reading this article, probably having several thoughts while doing so. Consider these thoughts:</p><ul><li>Where do they come from?</li><li>What are they based on?</li><li>Your past experiences as a child?</li><li>Something you’ve read?</li><li>An identity you’ve adopted and hold onto?</li></ul><p>See — it’s complex.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*50QILZceSPWCK6wL" /><figcaption>Photo by <a href="https://unsplash.com/@ryoji__iwata?utm_source=medium&amp;utm_medium=referral">Ryoji Iwata</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In most organizations nowadays, we work not just with one other individual but often try to make a team of up to 15–20 individuals work together.</p><p>This is complexity!</p><p>And yes — people tasked with supporting a team to grow together, achieve their goals, create amazing products, and help each other do have success. We’re usually super proud of big achievements like:</p><ul><li>Helping to build a group of individuals into a cohesive team.</li><li>Releasing the desired product on time with the desired outcome that customers love.</li><li>Seeing the action items from an improvement session improve the team’s workflow.</li><li>Creating a plan that effectively addresses a long-standing problem.</li></ul><p>But do these happen every week? Speaking from my own experience, they’re not frequent. So, are we failing the rest of the time, or are there other smaller details that we’re missing?</p><h3>The small print</h3><blockquote>When we confuse past performance with future potential, we miss out on people whose achievements have involved overcoming major obstacles. We need to consider how steep their slope was, how far they’ve climbed, and how they’ve grown along the way. The test of a diamond in the rough is not whether it shines from the start, but how it responds to heat or pressure.-Adam Grant</blockquote><p>We tend to forget where we started and what we encountered along the way, thus overlooking the small details that occur more frequently than the big achievements.</p><p>Small details like:</p><ul><li>A team member deciding to stay with the company after their probation period.</li><li>A “Thank you for listening” message from a team member you’ve supported.</li><li>Being asked for a moment of your time for a simple coffee chat.</li><li>A round of laughter during a Friday check-in session.</li><li>Offering help or, even better, being asked for it.</li></ul><p>These things happen much more frequently.</p><p>But in moments of self-doubt, when we wonder, “What value am I actually bringing, if any?” we tend not to think of these small moments. Our tendency is to “think big,” which is also something society wholeheartedly supports.</p><blockquote>If you knew five years ago what you’d accomplish now, how proud would you have been? — Adam Grant</blockquote><h3>What can we do?</h3><blockquote>The key to overcoming self-doubt is not to convince yourself of your worth, but to develop a habit of focusing on your contributions, not your insecurities. -Michael Singer</blockquote><p>Here comes the imposter syndrome and things like “I’m not good enough.” “When will they finally notice?” and plenty of other amazing stories we tell ourselves and even worse, with time start believing.</p><p>The imposter syndrome became a completely new meaning to me when reading what Adam Grant had to say about it.</p><blockquote>Not long ago, it dawned on me that impostor syndrome is a paradox:</blockquote><blockquote>Others believe in you</blockquote><blockquote>You don’t believe in yourself</blockquote><blockquote>Yet you believe yourself instead of them</blockquote><blockquote>If you doubt yourself, shouldn’t you also doubt your low opinion of yourself?</blockquote><blockquote>I now believe that impostor syndrome is a sign of hidden potential. It feels like other people are overestimating you, but it’s more likely that you’re underestimating yourself. They’ve recognized a capacity for growth that you can’t see yet. When multiple people believe in you, it might be time to believe them.-Adam Grant</blockquote><p>This changed my perspective completely.</p><p>But recognizing this isn’t enough for me. What it does, though, is help me pause when I hear those self-doubting thoughts, and then I turn to my tool of choice.</p><h3>A folder that works wonder</h3><p>It’s one of those things where I can’t remember who shared it with me — I suspect it was my wife, but she can’t recall either. So, if you’re reading this and it was you, please reach out. I’d be happy to say “thank you.”</p><p>What is this magical thing I’m talking about? It’s simply a folder on my laptop — it sits on my desktop and is easily accessible. From the outside, it’s just a folder, but once opened, it helps me every single time.</p><p>This is how the folder looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*TllCVHptAAMkm_Q8CEDtPQ.png" /></figure><p>Pretty simple right? From the outside it’s just a folder but once opened it helps me every single time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/0*wNEFg8u3ypOz2s94" /></figure><h3>So how does it work?</h3><p>Every Friday in the afternoon, I have a blocker in my calendar that looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/322/1*ctH1tIns08Bso4C9IGif6A.png" /><figcaption>A friday afternoon blocker</figcaption></figure><p>Every Friday I take 30 minutes to reflect on my week and collect all the good things that I can still remember. I go through my calendar, go through the meetings I had, the workshops I facilitated, the people I spoke to, I scroll through my messages and whenever I can think of something that was positive in this week, it gets put into my “feel good” folder. This could be a screenshot of something, a feedback form or just a text of me writing down something that I can still remember.</p><p>And all these beauties get into this folder.</p><p>A very nice by-product is that I usually feel good leaving into the weekend on a Friday.</p><p>But this folder serves me well beyond that — it becomes especially powerful in moments of doubt. When I start to think, “What am I even doing here?” Instead of spiraling into a lengthy self-monologue, I go to my feel-good folder and scroll through it — old messages, new messages, it doesn’t matter. Looking through it pulls me out of the negative story I’m about to construct for myself and helps me gain a new perspective.</p><p>I’m still a work in progress and aim to catch myself sooner, but yes, it’s called “work in progress” for a reason.</p><p>How to build your folder?</p><ol><li>Create a folder on your laptop, your mobile device or simply in your analogue notebook (whatever works best for you)</li><li>Block some time in the week — start with 30 minutes and jot down anything positive you can still remember about the last days.</li><li>Put them into your feel-good folder</li><li>Don’t forget to smile while closing your folder</li><li>Go back to your folder whenever you catch yourself generating a story about how you do not provide any value to others around you.</li><li>Make it a habit of filling the folder — don’t skip it. Let it grow — it’s like the tiny angel on the other shoulder you are trying to build up — don’t let it dissappear.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HtpTzXV_1EhU1We4" /><figcaption>The last bullet point according to the AI</figcaption></figure><p>As you start creating your own ‘feel-good folder’, remember it’s more than just a collection of positive moments.</p><p>It’s a snapshot of your growth, a reminder of your impact on others, and a powerful antidote to self-doubt.</p><p>Each entry is a step towards recognizing your hidden potential and the value you bring to every human interaction.</p><p>Start today, and watch this simple tool transform not just your perception of self-worth but also how you navigate the complexities of working with others.</p><p>And good things might just be a folder away…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c41103a59932" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting a team out of learned helplessness using Flow Metrics — a Case Study]]></title>
            <link>https://medium.com/@peter_89654/getting-a-team-out-of-learned-helplessness-using-flow-metrics-a-case-study-e2ef886838c4?source=rss-b5d367332ea9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2ef886838c4</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[learned-helplessness]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[flow]]></category>
            <dc:creator><![CDATA[Peter Zylka-Greger]]></dc:creator>
            <pubDate>Tue, 09 Jan 2024 07:16:35 GMT</pubDate>
            <atom:updated>2024-01-09T07:16:35.928Z</atom:updated>
            <content:encoded><![CDATA[<h3>Getting a team out of learned helplessness using Flow Metrics — a Case Study</h3><p>Writing this article has been on my mind for quite some time, but I somehow didn’t get around to writing it due to a million reasons, mostly excuses.</p><p>In this article, I’d like to introduce you to a team I was fortunate enough to be part of. It’s a pretty common team, one that probably most of us have met or been part of during our time working in teams. It is probably a bit too large in team size and has team members with a variety of skills, with the aim of delivering software to customers. And, like other teams in the realm of software development, something was not quite right with this team — you could say that this team was stuck.</p><p>I was brought in as an external consultant to work with the team, as usual with my engagement in the form of ‘do something with the team and improve it.’</p><p>In this case study, I’d like to invite you on the journey we took, how we were able to get unstuck, and even more importantly, become a team of individuals that creates value — with some support from data that we always had but never thought of using.</p><h3>Question to myself: Any regrets that I delayed writing the article?</h3><p>It’s actually the opposite — I’m quite happy about it, because it was only when I got my hands on Jim Benson’s book “The Collaboration Equation” that I truly understood what was happening in this specific team I will write about.</p><p>The book, which is already my ‘must-read for 2024 recommendation,’ gave me the understanding and also the right words to describe what this team went through and how they moved from their learned helplessness to a state in which “individuals in teams create value.”</p><p>Link to Jim’s book:</p><p><a href="https://www.goodreads.com/book/show/62796385-the-collaboration-equation">The Collaboration Equation: Strong Professionals Strong...</a></p><h3>Learned Helplessness</h3><p>Let’s start with the definition of Learned Helplessness — Jim Benson describes it as:</p><blockquote><em>Learned Helplessness is the tendency not to act at all because you increasingly expect the system to thwart you and then penalize you for even trying. Logically, it is safer to not act (to give up your agency). It is easy to blame the victim and tell people to go that extra mile, but learned helplessness isn’t simply giving up. Learned helplessness is the result of realistically assessing no-win situations and realizing that action will yield no or negative results. In an anti-collaborative environment, acting with confidence is dangerous, which means that professionalism is dangerous — </em>Jim Benson/The Collaboration Equation</blockquote><p>Everyone working in this team would have noticed symptoms that were visible in this team — there we plenty of them.</p><p>If I had to pick three they would be:</p><ul><li>not able to control their own working environment</li><li>a very limited flow of information within the team and outside the team</li><li>a self-fulfilling team identity of “that’s just how we are”</li></ul><p>The last point is the most interesting to me, as it is also something often observed in individuals. After some time, we tend to believe a story others tell about us or that we tell ourselves. And given that the collaboration equation is ‘Individuals in teams create value,’ maybe it’s not so surprising after all.</p><h3><strong>What we usually do vs. what we should do instead</strong></h3><p>So what was it?</p><p>Did we start by changing the people?</p><p>Were these individuals who simply didn’t care?</p><p>I guess the usual tendency in most companies nowadays is to focus on the performance of individuals, conduct awkward yearly reviews, and just hope things will improve. And if not, they start looking again to find who could be accountable for the situation, change people, change managers, keep everyone seemingly busy, and yet generate no real change at all. It’s like being in a constant loop.</p><p>From my point of view, there is a better question we could ask instead:</p><p>Do these professionals work in an environment/system that allows them to be good professionals?”</p><p>As Jim Benson puts it:</p><blockquote>No incentives, no negative reinforcement, no threats to their livelihood, can get people to perform well in an environment which does not give them the freedom or even the ability to perform well — Jim Benson/The Collaboration Equation</blockquote><p>So instead of working on the people, let’s have a look into the system they worked in.</p><h3><strong>Collaborating when it was not avoidable</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/0*wB120ZOLDknqJFcj.jpg" /></figure><p>The team was working within a system that enforced the use of Scrum. To avoid any conversation that might completely miss the mark, I’d describe it more accurately as a “push” system.</p><p>Every two weeks, new work was pushed onto the team’s workflow. While there was initial feedback from the team about this situation, it eventually subsided over time, leading to a state of learned helplessness within the team.</p><p><em>Now comes the most crucial part of it:</em></p><p>This situation dragged on for more than four years. During this time, every two weeks, new work was pushed into the system, regardless of whether the previous tasks were completed or not. This often resulted in a sprint backlog of over 70–80 tasks, with a team struggling to survive week by week. The situation reached a point where even frustration wasn’t openly expressed anymore, as it became accepted as “just how things are.” Team members simply picked up another ticket, worked on it, and moved to the next one, collaborating when it was not avoidable.</p><p>I’m pretty sure that if this team would have looked at the 5 dysfunctions of a team, we would have scored quite high in all of them.</p><p>And every attempt to help the team from the outside, came from the perspective of “fix them” and “make them understand” and never looked at the system the team was working in and if the system made it possible for good professionals to actually be good professionals.</p><h3><strong>Fix the system, not the people</strong></h3><p>So what happened?</p><p>Hopefully not surprising to a lot of my readers, it wasn’t a big transformation that helped this team move into the right direction.</p><p>What might be surprising is the fact that it all started with a simple question:</p><p><em>“What if we would just stop working as we do now?”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/0*4QtaPRshVc-pCv0M.png" /></figure><p>And, although it might have seemed like a fairly standard question from the outside, the reactions on the faces of those we were looking at on the screens told a different story. It appeared that in four years, no one had thought to ask this team what their ideal working environment would look like.</p><p>This was the beginning of what I call our “culture bubble” story.</p><p>Check Evolve2B for more information on Culture Bubbles:</p><p><a href="https://evolve2b.com/how-to-build-a-culture-bubble/">How to Build a Culture Bubble - Evolve2B</a></p><h3><strong>How the right environment looked for this team</strong></h3><p>I have to admit that I myself didn’t expect this to work as well as it did. But more suprisingly, I was shocked on how quickly these professionals were able to be in charge of their professionalism again.</p><p>The first step was an obvious one:</p><p>We changed from a push system into a pull system. Work was not longer being pushed into the system every 2 weeks but instead was waiting in a backlog to be pulled by the team. We still kept our iterations of 2 weeks for 2 reasons:</p><ul><li>we wanted to keep a dedicated time we would get together and discuss priorities, learnings and also look back at what we achieved</li><li>the second reason is that the system around kept on working in iterations of 2 weeks so we decided to build adapters and this way were able to reduce noise regarding the changes we have made and at the same time, were aligned with the teams outside the team</li></ul><p>A next step was that we wanted to make sure that the way our work flows becomes visible — to us, but also to the people relying on our work.</p><p>So the look of our working board changed — we have added new columns that we hoped would make the progress of our work more visible:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oEJ4D0vy0QymVKt4pgprPQ.png" /><figcaption>Our board before the change</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pFfHVjjou-AjFTN1oWnTgw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qCUmSKngg_GE2IIr5TGxSg.png" /><figcaption>Our board after the change</figcaption></figure><p>As another point of discussion, we talked about Flow Metrics and decided that the data they provided could be a valuable indicator of our work. This data would provide us with information, allowing us to act with confidence. We agreed to give this approach a try and have another conversation about it in six weeks, at which point we would decide if this was the right path.</p><p>I’d love to tell you more about what we did — about all the amazing workshops we conducted with the team, about the fruitful one-on-one sessions, and how we unlocked deep-seated personal issues. But the truth is, we didn’t do anything else. It wasn’t that these professionals were incapable of working together, or even worse, unwilling.</p><p>Rather, the image that formed in my mind was that of individuals at work, chained to a wall. In this scenario, all that was necessary was to help them realize that they could break free from the chains themselves.</p><figure><img alt="What DALL·E imagines a working system like this to look like" src="https://cdn-images-1.medium.com/max/1024/1*0jJZQptPSvahJic1jL2F6w.png" /></figure><p>I already told you at the beginning of this section how quickly it went.</p><p>Well…how quickly did something change?</p><h3><strong>Professionals who are in charge of their professionalism</strong></h3><p>It took about two to three days for the new working system to click in. Cleaning up the backlog was obviously necessary, and this wasn’t a task performed by a single person but rather a team effort.</p><p>Getting accustomed to accurately reflecting the status of our work on the new board was probably the hardest part for everyone on the team. But once we overcame that, collaboration and work began to flow smoothly.</p><p>So, what did we see happening next?</p><p>Fruitful conversations about work in progress became a regular part of our daily huddles.</p><p>We shifted from dull daily meetings to ones where we:</p><ul><li>Actively engaged in conversations about how we could collaborate to move aged items to the right side of the board (action on data)</li><li>Team members sought support from others</li><li>People decided to pair up for specific complex analyses or tasks</li><li>Challenged priorities using the information that was visible and available to us</li></ul><p><em>Eliminating value-negative tasks</em></p><ul><li>While sitting in meetings, we openly challenged their value, quickly agreeing to try alternatives. Mostly it was along the lines of, “Let’s see if we miss anything if we don’t have this meeting.”</li><li>The board introduced new ways to quickly and effortlessly find information.</li><li>We implemented quick fixes swiftly. For example, “Could we visualize information for the person who picks this up next right on the first screen? It would then be easier for them to decide what to do next.” This meant, for instance, letting the team member who would take over QA know in advance which environment was needed for testing:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*Lp1xpZ0mS1uY1YEblXwcQw.png" /><figcaption>a small text field to support collaboration</figcaption></figure><p>The last part was an interesting one, as it happened naturally. No Retrospective was performed for these changes. These were all things that simply happened or that were brought up during a daily huddle.</p><p><em>Quickly identifying bottlenecks and acting on them</em></p><p>Thanks to our new way of visualizing our work, we were quickly able to identify bottlenecks within the system we were working in. To my great surprise, even though most of these bottlenecks were beyond our direct control, the team realized that there was something they could do to alleviate these choke points to some extent, and they swiftly took action on it.</p><p>There was also an instance where the team, without any external interference, started discussions about having smaller work items and how it would benefit their feedback loop. (The 85th percentile cycle time proved quite useful in determining a good starting point for this.)</p><p>It’s important to note that we never started with a Work In Progress (WIP) limit. However, due to the collaboration and the pull-system in place, it never became a real issue. If a problem did arise, it was quickly addressed in the daily huddle, actions were taken, and we moved forward.</p><p><em>Increase in engagement</em></p><p>The points mentioned above already suggest an increase in engagement. But one aspect that really stands out to me is the atmosphere you experience when you enter a room with these individuals. There’s a palpable difference in their demeanor and in the way they work.</p><blockquote>We see systems that engage people professionally, leaving them energized at the end of the day and not tired and spent. — Jim Benson/The Collaboration Equation</blockquote><h3><strong>Give me the data</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/0*pwnl3kfdApJJTS0I.jpg" /><figcaption>Possibly you, reading until now</figcaption></figure><p>Although we rarely discussed the data itself, simply accepting it as information to enhance our team decision-making and our collaboration, we were still surprised by the results of the first data set.</p><p>This is what we got:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LFkYuu75pMT3fQ9Obqi3sw.png" /><figcaption>Scatterplot created with <a href="https://github.com/LetPeopleWork/FlowMetricsCSV">https://github.com/LetPeopleWork/FlowMetricsCSV</a></figcaption></figure><p>The graphic above shows what we were capable of achieving in the three months prior to the changes: a throughput of 140 items, with each taking 37 days or less to complete (as indicated by the 85th percentile, highlighted in light green).</p><p>When we took another measure after the first 3 months, and got the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s94Y2-RGEqKtSXiqBx4oYQ.png" /><figcaption>Scatterplot created with <a href="https://github.com/LetPeopleWork/FlowMetricsCSV">https://github.com/LetPeopleWork/FlowMetricsCSV</a></figcaption></figure><p>With the same scope of three months, we now achieved a throughput of 186 items and reduced the cycle time from 37 days or less to 17 days or less (again, refer to the light green line for the 85th percentile).</p><p>Also, take note of the changes in the Y-graph. Although we still had outliers, as unexpected things happened, we took action or were consciously aware of them. The more our items aged and approached our 85th percentile line, the more we discussed them in our huddle.</p><p>There is one aspect that is difficult to measure, and perhaps shouldn’t be, but it’s one that keeps this team continuously improving in their collaboration: the increase in the number of professionals who were empowered to work effectively.</p><p>A key learning for us was that having data helped shape our conversations within the team, leading to more informed and effective decisions.</p><h3><strong>What came after?</strong></h3><p>Understandably, people around this team became curious about how they managed to break free from their previous state and are now trying to adapt their systems to achieve something similar. This is the beauty of a “culture bubble”— extensive promotion isn’t even necessary. People from the outside quickly notice the change and start asking questions.</p><p>Using data also opens up new opportunities to answer questions like, “When will it be done?” (Thank you, Monte Carlo simulations). This hopefully serves as another example of how visualizing our work, and planning future tasks, aids in collaborating with others and making informed decisions.</p><p>Another interesting aspect is delving into the concepts of Obeya, as described in Benson’s book (Did I mention that it’s an absolute must-read?).</p><p>To me, the most significant takeaway remains the fact that no matter what we do, working within a system that allows individuals to excel in what they do best is crucial for awakening the professional within them.</p><blockquote>Individuals in Teams create value- — Jim Benson/The Collaboration Equation</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2ef886838c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We are team! Wait…are we really?]]></title>
            <link>https://medium.com/@peter_89654/we-are-team-wait-are-we-really-559ef49724fa?source=rss-b5d367332ea9------2</link>
            <guid isPermaLink="false">https://medium.com/p/559ef49724fa</guid>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Peter Zylka-Greger]]></dc:creator>
            <pubDate>Thu, 10 Nov 2022 16:10:20 GMT</pubDate>
            <atom:updated>2022-11-10T21:55:04.472Z</atom:updated>
            <content:encoded><![CDATA[<h3>We are a team! Wait…are we really?</h3><figure><img alt="Foosball table" src="https://cdn-images-1.medium.com/max/1024/0*eY6Nr56UJywocWgZ" /><figcaption>Photo by <a href="https://unsplash.com/@pascalswier16?utm_source=medium&amp;utm_medium=referral">Pascal Swier</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Teams — most of us nowadays are part of a team. At least, that is what we tell and what we believe and often it is what we are being told.</p><p><strong>The question though is: is this the case?</strong></p><p>In the world of business, teams make up an essential part of an organisation’s structure. But what defines a team? The definition of a team according to Katzenbach and Smith “is a small group of people with complementary skills who are committed to a common purpose, performance goals, and approach for which they hold themselves mutually accountable.”</p><p>I personally often like to describe a team as “a group of people that needs each other to achieve a common goal.”</p><p>My definition often raises a lot of doubts for me about what I see in organisations. Do teams need each other to achieve a common goal? Or is every individual just happy to have enough work within a 2-week sprint and have as little interaction with colleagues as possible? Only to bring it back to the sprint review 2 weeks later and demonstrate the results from their individual work.</p><p>So what is the missing link here? Why are people joining teams and are they truly benefiting from being part of a group?</p><p><strong>I currently see 3 major factors contributing to it:</strong></p><p><em>1. Having teams became the norm within organisations.</em></p><p>But only a little effort was put into some fundamentals: What is the purpose of having a team in the first place? Do we need a team for what we are trying to achieve? What kind of personalities do we even need within the team (the book “Good to great” gives a perfect explanation of “First who and then what?”) — just to name a few. When questions like this are not asked or answered correctly, we end up with teams that are not fit for the tasks at hand.</p><p>Signs to look out for:</p><p>- you get blank stares when you ask “why they are a team”</p><p>- when you ask for the team’s top 3 challenges, you get a bunch of individual challenges thrown at you</p><p>- Swarming, Mob, Pair Programming? “Listen…we do not do this here. But we have someone else review our code.”</p><p><em>2. There is no common goal.</em></p><p>This could be an entire blog post on its own. Organisations seem to endlessly struggle with this. Even though there is a goal defined for what they would like to achieve with teams, once established everyone seems to go back to what they have known before — simply deliver output. As a result, everyone is focused to finish his/her story. There is no motivation to work together to reach a goal because there is none except for finishing everything that was put into the sprint. So everybody becomes busy with their tasks and forgets about the others in the team.</p><p>Signs to look out for are:</p><p>- In your sprint planning, every team member makes sure to have enough tasks assigned to them (bonus if they make sure to have their Story point capacity fulfilled)</p><p>- your sprint goal sounds like this “finish all the stories in the sprint”</p><p>- your Sprint Review is a demonstration of individual work and often starts like this “This is what I have worked on in this sprint…”</p><p>- there are no team challenges (collaboration, attitude etc.) raised during the Retrospectives, and also no one understands why they need to sit in yet another Retrospective.</p><p>bonus sign to look for: you are getting new team members to get more things done…</p><p><em>3. There is little to no questioning of the team set up and the way they work together</em></p><p>In one of the “real” teams, I had the privilege to work with, there was a constant exchange on how we could not only improve the work within the team but also if there is something we could do to improve the team setup. And we experimented with a lot of things before we settled on a team setup that we considered good enough to proceed with. And this was a team that was completely co-located (and working 5 days a week in an office pre-pandemic — and we loved it!).</p><p>But what about the teams that are distributed over different time zones and in different countries? I rarely see this being questioned by the team or even by the people that have set them up in this way. I know the agile community is all about stable teams, but doesn’t it require time to find the right people and the right setup for this team in the first place?</p><p>I recently saw an interview by football coach Jurgen Klopp where he stated that the secret to a well-working team is, to take your time to have the right group together and that especially in the beginning he had to change a lot until they had all the right characters together, the right people, the right skill set, and the right mentality. How much time do we take in organisations to form teams? How much are we continuously looking for better ways? For new approaches? Or is it the norm to stick with a “set it and forget it” approach to forming our teams?</p><p>signs to look for:</p><p>- everything about your team is exactly as it was on day 1 when it was formed</p><p>- team members leaving the team do not spark conversations about what to change</p><p>- “the enemy is outside” attitude</p><p>- Do you think Patrick Lencioni wrote the 5 dysfunctions of a team about your team</p><p><strong>What’s the alternative?</strong></p><p>I, unfortunately, do not have an answer. There is another element that almost made it, which is “Is there really no “I” in team?”, but that is a story for another day.</p><p>I would like to see an approach where we are more careful with the term “team”, and consider if this is the right approach, or if a working group would not be a good starting point.</p><p>Teams can be super powerful, and I would not write these lines if I haven’t experienced it myself. This was a team where the common goal was always present, where feedback was on our daily menu, where limits were challenged and finally where individuals understood why they came together every day and how they would benefit from it and through that, the product/customer.</p><p>But this was a team that was co-located, had the right people, let go of the people that weren’t a fit for the culture and loved what they do.</p><p>How many of these teams do we have nowadays? And how do we set up teams in the best possible way? Is it the best way to have people from 3 different time zones in the same team working together? Or are we losing out with this setup and its limitations due to language, different cultures, different working times etc.? Will the future bring us different setups -more localised setups?</p><p>Is there a better way, like the fluid scrum teams and dynamic reteaming — as often described by Joe Justice at Tesla?</p><p>As Heidi Helfand said:</p><blockquote>“Whether you like it or not, teams are going to change. You might as well get good at it.”</blockquote><p>As already stated above, I do not have an answer for this, but I feel like this is a challenge that is present in a lot of organisations and might be a topic that inspires others to take a look in the mirror — preferably with their teams and ask the question:</p><p>“Are we a team? And if so — why are we a team?”</p><p>Find out more about me and my work on zylka-greger.com or on <a href="https://www.linkedin.com/in/peterzylkagreger/">https://www.linkedin.com/in/peterzylkagreger/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=559ef49724fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four Ways to Get Support as a Scrum Master]]></title>
            <link>https://medium.com/better-programming/four-ways-to-get-support-as-a-scrum-master-8a506a7199ff?source=rss-b5d367332ea9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a506a7199ff</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Peter Zylka-Greger]]></dc:creator>
            <pubDate>Sun, 28 Aug 2022 10:37:15 GMT</pubDate>
            <atom:updated>2022-08-30T12:11:54.251Z</atom:updated>
            <content:encoded><![CDATA[<h4>#2 — Read a lot of different things</h4><figure><img alt="Get support as a Scrum Master" src="https://cdn-images-1.medium.com/max/720/0*WNT3KrYG1GH3aooT.png" /></figure><p>The Scrum Master role is crucial within a Scrum team and an agile organization. The Scrum Master helps the team stay focused, removes obstacles, and promotes continuous improvement — among numerous other vital responsibilities.</p><p>Over the last years, I have seen Scrum Master struggling with the role. Either because they were new to the role or because they lacked specific knowledge they needed to succeed at the job. Knowledge about themselves, learning how to work with the system they are part of, and understanding how to relate to their team members. And I’m not talking about the recent trend of having a “20% Scrum Master” within the team — this is a story for another post.</p><p>It’s easy to write these lines for me now, mostly because I have been through this myself. When I started my Agile journey in 2016, I was a new Scrum Master. I had no experience, and back then, I didn’t know that this role would significantly impact my life. I would soon discover that the Scrum Master role is much more than just facilitating meetings and helping teams solve their problems. It’s an opportunity to learn about yourself, develop your skills, and become a better person at work and at home.</p><p>These are four ways I’ve learned to find support as a Scrum Master:</p><h3><strong>Get yourself a mentor</strong></h3><p>Having a good mentor can be the key to your success in Scrum. Your mentor can help you learn the ropes of your role and help you overcome your challenges along the way. Reflecting on my projects over the years, I have had mentors at every company. And while some of them were Scrum Master or Agile Coaches, most were not. Instead, they were leaders, people I felt inspired by, people who role-modeled behavior I wanted to learn, and people I admired. So take the time to find mentors that inspire you, and take the time to listen to them. Observe their behavior in situations when stakes are high, how they interact with others or ask them specific questions about things you might want to improve in yourself, or even share with them your own goals or aspirations. And be open to getting feedback from them. I have to admit that I often didn’t really understand what my mentors were doing and only realized and understood it later, like, i.e., working with a brilliant Product Manager and seeing him in action daily. Only later did I discover through my understanding and interest in the topic what he was doing and how he shaped the product culture within the team.</p><h3><strong>Read everything you can get your hands on</strong></h3><p>I believe that is the beauty of the Scrum Master role and its industry. Plenty of passionate people are also willing and happy to share what they know with others. In the Scrum Master community, there are tons of blogs, articles, and podcasts available online that you can consume and learn not only how to become a successful Scrum Master but also allow you to learn a lot about topics that are outside of the Scrum world, like leadership, management, time management, problem-solving, collaboration, communication and much more. There’s no limit to what you can learn and gain from the available resources as long as you are willing to dedicate some time to it and are not afraid to reach out for help. Read what feels suitable for you at the pace you want to move at, and read what is relevant to you at the moment of your growth stage. I remember starting with some “classics,” like Geoff Watts’s “Scrum Mastery” or “Agile Retrospectives” by Esther Derby and Diana Larsen. Followed by blog posts by Mike Cohn and articles by Barry Overeem and Christiaan Verwijs. Over time, I started looking for different ways: going to meetups, attending conferences, joining online communities, and asking different questions to other people. My reading over the past couple of years went through different stages, always depending on my current interest and pain points — some of the main topics were systems thinking (“Fifth Discipline” by Peter Senge), Team development (“The 5 Dysfunctions of a Team” by Patrick Lencioni), Self-Development books (“The Untethered Soul” by Michael Singer) or books on changing cultures within companies (“Leading beyond change” by Michael and Audree Sahota). It has always been a constant process of learning and growing as a human being and as a professional. Don’t be afraid to ask other people what they are reading and what resources they would recommend to you because we are all here to learn.</p><h3><strong>Pick the right training for you</strong></h3><p>The obvious choices here are attending another Scrum training, and I did so too. They were a lot of great lessons I was able to get out of them. And they certainly helped me to become a better Scrum Master overall. However, you might want to look at other options as well. Especially the options that aren’t so focused on Scrum specifically. Look for things that interest you personally, and most importantly, look for things that you can put into practice rather immediately. That way, you avoid the trap of learning something in training, thinking of it as a good idea, but as you do not put it into practice, rather forget about it afterward quickly.</p><p>I came across a training course through participating in an Agile Coaching Camp (another great resource to get inspired and learn) when a colleague there mentioned the work done by Michael Sahota. Little did I know back then what an impact the CAL1 and CAL 2 training offered by Michael and Audree would have on me. Not only in terms of knowledge about leadership but, more importantly, understanding myself on an intense level.</p><p>Depending on your environment, everything related to Product Management can also be super helpful. For example, attending a class by Jeff Patton and having my idea of Product Ownership challenged was a real game-changer for me. It helped me support Product Managers more effectively.</p><p>Whatever you decide to do, choose it wisely! Look how the training is structured, if the trainer is someone you feel inspired by if there is a community of participants after the training etc…</p><h3><strong>Be part of the community</strong></h3><p>I’ve already stated how vital community is to learn and develop as a Scrum Master. It’s one thing to attend a training or read a book that talks about how to be a good Scrum Master; it’s another thing entirely to be surrounded by a group of people who share your same passion, who want to learn, who are curious and are willing to help you learn as well. Nowadays, connecting to peers is very easy thanks to various social media options — there is LinkedIn, Slack spaces, and Discord servers. Pick one that works best for you and get involved. Be open to sharing your knowledge, challenges, questions, etc., and help others grow. One thing I’ve learned during my time in Australia is that a community is about giving as much as receiving. There is no need to withhold information because you’re afraid someone else might take over your role or have an advantage over you. This is just fear triggered by your ego. If you’re worried about that, it’s time to let go and grow as a community member instead. My own experience showed me that when you open yourself up to the community and share your knowledge with others, that’s when the magic happens. You learn from others, you get to inspire others, and opportunities will show up in the most amazing ways.</p><p>I hope this post will help you if you’re considering getting support. It’s a necessary step, and you would miss out on a big opportunity if you decide not to seek support. If you need advice on where to look for it, reach out to me, and I’ll do my best to help you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a506a7199ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/four-ways-to-get-support-as-a-scrum-master-8a506a7199ff">Four Ways to Get Support as a Scrum Master</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get started on a new team?]]></title>
            <link>https://medium.com/@peter_89654/how-to-get-started-on-a-new-team-65e7672a64f3?source=rss-b5d367332ea9------2</link>
            <guid isPermaLink="false">https://medium.com/p/65e7672a64f3</guid>
            <category><![CDATA[employee-engagement]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[team-development]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Peter Zylka-Greger]]></dc:creator>
            <pubDate>Sun, 21 Aug 2022 11:58:36 GMT</pubDate>
            <atom:updated>2022-08-21T11:58:36.295Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="joining new team" src="https://cdn-images-1.medium.com/max/1024/0*px4FWHgB5uQeAC-d" /><figcaption>Photo by <a href="https://unsplash.com/es/@hannahbusing?utm_source=medium&amp;utm_medium=referral">Hannah Busing</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Joining a new team as a Scrum Master can be an exciting experience, but it can also be daunting. Here are some tips to help you start off on the right foot:</p><p>1. Establish a good relationship with your team from the start. Set up 1:1 conversations early in the game with your team members to get a sense of who they are and at a later stage what their pain points are.</p><p>2. Listen, listen and listen again! While it is important to add value through your own experience and expertise, your first priority as a new Scrum Master is to listen to your team. Try to suspend judgment as you begin to learn how your team works and what their needs are. You will be surprised by how much you will learn as you ask questions and take the time to really listen.</p><p>3. Be open to feedback and suggestions from your team. Rather than imposing your vision on the rest of the team, invite them to share their ideas and provide feedback on your approach. This will help you gain an understanding of what makes your team tick and help you build a strong rapport that will lead to greater success in the future.</p><p>4. Get to know key stakeholders outside of the development team. Take the time to understand who is involved and how you can help them to be successful.</p><p>5. Pay your taxes. We need to pay taxes in our daily lives, regardless if we like paying them or not. They are a way of society working, and to get them off your back (You do not want to mess with the IRS/tax agency), you need to be responsible and deal with them accordingly. The same applies when you deal with structures outside your team. Not paying your taxes will result in people making your team’s life more challenging and difficult. Paying taxes as a team will help you to build better relationships within the organization and allow your team more freedom to build their own culture bubble. (Thanks, Michael, for offering this analogy — it is so incredibly helpful and true)</p><p>6. Listen more than you talk. Oh — I did mention listening already under point #2. But it is important to remember to listen. In the beginning, when we join a new team, it would be easy to connect patterns we personally have seen in the past and apply them to the current situation we are presented with. As tempting as it might be to take this course of action, it will only get us in trouble since every situation is unique on its own, and we are missing vital information if we are too focused on our experience or preconceptions about the situation at hand. Whenever I feel tempted to jump in too early, one method that worked for me was to internally ask myself, “How can I stay curious just a bit longer?” This usually helps move me out of the mode of trying to prove my point and instead leaves me in the mindset to truly listen and observe what is actually happening before trying to “fix.”</p><p>I hope these tips can help you and your team on your journey of new beginnings!</p><p>What are tips you would share? What has worked for you in the past? I would love to hear about it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65e7672a64f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why the Scrum Mastery Pathway would have been the Scrum training I needed when I started (Part 2)]]></title>
            <link>https://medium.com/@peter_89654/why-the-scrum-mastery-pathway-would-have-been-the-scrum-training-i-needed-when-i-started-part-2-a039cc4ab668?source=rss-b5d367332ea9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a039cc4ab668</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agility]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[career-change]]></category>
            <dc:creator><![CDATA[Peter Zylka-Greger]]></dc:creator>
            <pubDate>Tue, 09 Aug 2022 12:17:08 GMT</pubDate>
            <atom:updated>2022-08-09T12:17:08.107Z</atom:updated>
            <content:encoded><![CDATA[<p><em>If you haven’t read part 1, I’ve got you covered — click </em><a href="https://www.zylka-greger.com/post/why-the-scrum-mastery-pathway-would-have-been-the-scrum-training-i-needed-when-i-started-part-1"><em>here</em></a></p><p>In part 1, I shared how challenging it was to start in this entirely new role called “Scrum Master”, but eventually things worked out. I got more settled in the role, learned more about the framework and more importantly, understood better how a Scrum Master can support the team.</p><p>But as Nelly Furtado taught us in 2006: “Why do all good things come to an end?”</p><p>This was also the case for me and the project I was in. It ended and I had to look for a new gig. I was lucky and fortunate to find a new one fast and got myself into a new environment: a start-up</p><p>2 things I wished I knew back then:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*DomVwtmCJ7zagNmQ.jpg" /></figure><p><strong>Number 1: Not everyone will like what you do</strong></p><p>This one was quite a challenging one for me. Considering the assumptions I had about start-ups and that everyone in a start-up is surely “agile”, which to some extent was quite true, I’ve met amazing people and learned so much from them.</p><p>But as a pretty new Scrum Master, I was not prepared for all of this:</p><blockquote><em>Do we really need to do a Sprint Review every 2 weeks?</em></blockquote><blockquote><em>Why do we need the Refinement?</em></blockquote><blockquote><em>Can we not just work as we used to do?</em></blockquote><blockquote><em>All this doesn’t make sense!</em></blockquote><blockquote><em>I do not think, this Scrum process fits our needs.</em></blockquote><p>If you just thought, some of these questions sounded familiar, I’m sure you are not alone.</p><p>I on the other hand back then thought I was alone: Wasn’t my job as a Scrum Master to convince everyone in the team how amazing working in Scrum is? If they do not like it, I’m sure the one to be blamed, right?</p><p>So I tried really hard to convince everyone of how amazing all this could be, without really having anything any foundation for my approach. I simply went from discussion to discussion to discussion…</p><p>Eventually and with a bit of time, we got into a mode where it worked out, but looking back, I could have handled things a lot better.</p><p>Behind all of this though there was a deeper problem:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*SmkymwKjcmHKkzJn" /></figure><p><strong>Number 2: You do not need the answer for everything!</strong></p><p>“Wait? What?” would have probably been my reaction if someone told me that during that time. Back then, I thought there was a reason I was hired as a Scrum Master. And the reason was an inner dialogue I kept for quite a long time: “I’m here to fix things. So I need to know things and I need to prove quickly that I do know these things so that I can have answers for everything someone asks me.”</p><p>There was this urge to demonstrate to everyone who put their trust in me, that they have made the right decision — and the only way I knew back then, was to go into the “doing” and “knowing” parts. And due to that, I stopped doing an essential thing all along: LISTENING!</p><p>With what I know now, I’d be super curious to find out what people were saying to me and how different of a picture I would have gotten, if I was already able to truly listen. (Invite: If anyone knows how to time travel, let me know. But only if it is unlimited time travel I would think about going back, because if I only get 1-time travel, I still choose to see dinosaurs)</p><p>How would the Scrum Mastery pathway have helped me?</p><p>2 modules that we go through in the Scrum Mastery Pathway come to my mind.</p><p>The first one is the “Tactful” model — Saying What Needs To Be Said:</p><p>In this module, we will talk about the “bystander effect”, and “people-pleasing”, but also get to experience and practice a powerful tool to communicate what needs to be said in a tactful manner, which will perfectly build on the modules “Respected” and “Enabling”.</p><p>The second module is one of my favorites: “Enabling”, because:</p><blockquote><strong>A good ScrumMaster encourages people to talk to each other; A great ScrumMaster encourages people to listen to each other</strong></blockquote><p>In this module, we’ll not only practice with a truly amazing listening exercise, but we will also cover why empathy is so important, yet there are many stumbling blocks when using empathy (or trying to use empathy).</p><p>Just writing about this module, helped me get excited about sharing it with future participants of the Scrum Master Pathway training.</p><p>Speaking of which:</p><p>Benefit from the <strong>very early bird prices</strong> for my first two Scrum Mastery pathway classes — one virtually and the other one in Munich, Germany (the latter being held in German)</p><p>Virtual course (24th and 25th of October): Click <a href="https://www.eventbrite.com.au/e/scrum-mastery-pathwaytm-tickets-369516071517">here</a></p><p>on-site course in Germany (10th and 11th of November): Click <a href="https://www.eventbrite.com.au/e/scrum-mastery-pathwaytm-deutsch-tickets-369531327147">here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a039cc4ab668" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How starting as a Scrum Master was tough and a certificate was not enough (Part 1)]]></title>
            <link>https://medium.com/@peter_89654/how-starting-as-a-scrum-master-was-tough-and-a-certificate-was-not-enough-part-1-6f8979a6631e?source=rss-b5d367332ea9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f8979a6631e</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[training]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Peter Zylka-Greger]]></dc:creator>
            <pubDate>Sat, 06 Aug 2022 14:22:37 GMT</pubDate>
            <atom:updated>2022-08-06T14:22:37.472Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*un2Xa5VYdv1f_Z5_.jpg" /></figure><p>When people ask me how it was for me to start working as a Scrum Master, it is easy to tell stories about how it all worked out and how I found purpose in what I did back then. Ultimately, I’m still working in the field and thoroughly enjoy what I do daily (even writing a blog post on a Sunday).</p><p>But If I reflect a little deeper, the reality looked different. I was someone who had never heard of the role before. I was very fortunate (and forever grateful) that I had someone who not only introduced me to the role but also helped me get my first project and even did a lot of handholding throughout the project because, honestly speaking, going to a 3-day Scrum Master class helped me to cover a basic understanding of the Scrum framework, but what followed after that, was scary!</p><p>Let’s take the Retrospective as an example: Through the training, I obviously knew the goal of a Retrospective and received ideas about how I conduct a Retrospective through the training. However, when the moment of your first Retrospective arrives, it is a whole new ball game. I had so many doubts about conducting it and what would happen within the room.</p><p>The good news is: I survived, but as mentioned previously, I was lucky to have a supporting system actually sitting next to me for most of my working day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*Ux5zkS4_V97VUlRL.jpg" /></figure><p>But what I would have wished for is a training concept where I learn about aspects that help me conduct a Retrospective and where I have an ongoing support system through a trainer or a community where surely others went through a similar situation.</p><p>That is why I’m eager to get started with the Scrum Mastery Pathway and make that support system available to you. Not only will you be continuously supported for six months, but we will also meet bi-weekly to talk about your real-life challenges (i.e., the Retrospective you have to facilitate with this difficult team of yours). In addition, you will also have access to a community of fellow Scrum Master and trainers. And we will also support this by going through the content of the RETRAINED attributes. Right at the beginning of our time together, we go through the “Respected” module. In the module, we cover how helpful a Coaching contract with your team is right from the beginning. <em>Spoiler alert</em>: It will also help you in your Retrospectives. Or the “Enabling” module, where we will look at why “A good ScrumMaster is wary of influencing the team; A great ScrumMaster can act normally and know the team will still make their own decisions.”</p><p>Because let me tell you, I did a lot of influencing during my first Retrospective.</p><p>If that sounds like something you would like to be part of, check out the next available dates for the cohorts I will start :</p><p><a href="https://www.zylka-greger.com/scrum-mastery-pathway">https://www.zylka-greger.com/scrum-mastery-pathway</a></p><p>More information can also be found on: <a href="https://agilemasteryinstitute.com/">https://agilemasteryinstitute.com/</a></p><p>And stay tuned for part 2 where I will describe another reason why the Scrum Mastery Pathway would have been exactly what I needed during my starting time as a Scrum Master.</p><p>This article was originally posted on <a href="https://www.zylka-greger.com/post/why-the-scrum-mastery-pathway-would-have-been-the-scrum-training-i-needed-when-i-started-part-1">https://www.zylka-greger.com/post/why-the-scrum-mastery-pathway-would-have-been-the-scrum-training-i-needed-when-i-started-part-1</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f8979a6631e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>