<?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 Réka Szellmann on Medium]]></title>
        <description><![CDATA[Stories by Réka Szellmann on Medium]]></description>
        <link>https://medium.com/@reka-szellmann?source=rss-b2b3e743c8ba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Rdj6eNP5oMrvEUgkkewTzQ.jpeg</url>
            <title>Stories by Réka Szellmann on Medium</title>
            <link>https://medium.com/@reka-szellmann?source=rss-b2b3e743c8ba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:50:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@reka-szellmann/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[Step-by-step guide to create your time master plan!]]></title>
            <link>https://reka-szellmann.medium.com/step-by-step-guide-to-create-your-time-master-plan-98094b1cdb22?source=rss-b2b3e743c8ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/98094b1cdb22</guid>
            <category><![CDATA[time]]></category>
            <category><![CDATA[time-management-tips]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Réka Szellmann]]></dc:creator>
            <pubDate>Tue, 09 Sep 2025 23:08:53 GMT</pubDate>
            <atom:updated>2025-09-09T23:08:53.340Z</atom:updated>
            <content:encoded><![CDATA[<h4>Do you ever feel like life is slipping through your fingers? Well, we all do, and it has a scientific explanation. Time management is one way to get back in control. In this article I’ll mention why and give you a step-by-step tutorial of how I handle it.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S2DW5zgCwfD8xdkQ" /><figcaption>Photo by <a href="https://unsplash.com/@andriklangfield?utm_source=medium&amp;utm_medium=referral">Andrik Langfield</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>How can time management be useful?</h3><p>There is a very interesting study about why time speeds up once we are older. The answer — in short — is that we create fewer new and exciting memories hence we don’t remember our days that much. You can see the whole article here:</p><p><a href="https://invertedpassion.com/why-time-seems-to-pass-faster-as-we-age/">Why time seems to pass faster as we age - Inverted Passion</a></p><p>Other than <strong>getting ourselves to start meaningful stuff</strong>, time management also helps with:</p><h4>Keep in mind what we want to do</h4><p><a href="https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two">Our short-term memory is only able to keep 7 +/- 2 items</a>. Once your attention is divided you will most likely forget what you wanted to do.</p><p>Like my grandmother always says:</p><blockquote>“If your brain is short, keep a pencil with you”.</blockquote><h4>Avoid procrastination</h4><p>When faced with many tasks without clear priorities, we often end up postponing everything, ultimately completing nothing.</p><h4>Stress management</h4><p>For me, time management is one of the most effective ways to handle stress. The first step is to admit that we have a limit; we simply can’t finish everything right now.</p><p>With time management we can:</p><ul><li>Avoid <a href="https://www.runn.io/blog/workload-paralysis#what-is-workload-paralysis">workload paralysis</a>; select what you want to do in the next days and plan everything else for later</li><li>Clear our head; writing things down effectively stops them from keep coming back to our mind</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*6FBoEjZ_OfcjLO7Vr8S85A.jpeg" /></figure><p>Building a habit <a href="https://www.scientificamerican.com/article/how-long-does-it-really-take-to-form-a-habit/">may take some months</a>, but the good news is that using time management practices can help you a lot even if you only use them occasionally.</p><h3>So, how do I do this?</h3><h4>Getting Things Done (GTD®)</h4><p>I will not explain the system in this article, you can find all the resources you may need in their website:</p><p><a href="https://gettingthingsdone.com/">Home</a></p><p>One video shortly (~7 minutes) capturing the essentials:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FgCswMsONkwY%3Fstart%3D76%26feature%3Doembed%26start%3D76&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DgCswMsONkwY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FgCswMsONkwY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/331a0472dabf3a18ceda2e1702525d88/href">https://medium.com/media/331a0472dabf3a18ceda2e1702525d88/href</a></iframe><h4>Asana + Google Calendar</h4><blockquote><strong>You learn by doing, so I highly recommend not just read the following steps, but also do it with me! What’s the worst that can happen?</strong></blockquote><p>I use Asana since 2016, <a href="https://asana.com/">it’s a work management tool</a>, free for personal use. (But of course if you have another tool (e.g. <a href="https://trello.com/home">Trello</a>) you can use that too).<br>I have two workspaces because I don’t like to mix work and personal tasks:</p><ul><li>Me: for my personal life</li><li>Company name: my personal To Do for work</li></ul><blockquote>In work we usually use JIRA which I find too heavy for everyday usage.<br>I track there my goals which needs to be visible, and use Asana for my personal reminders, recurring tasks, quick ideas, etc.</blockquote><p>Let’s start with a summary, then I will guide you through the process in detail.</p><h3>Summary of the steps</h3><ol><li>Write everything down from your head until it’s empty</li><li>Move them to the right category:</li></ol><ul><li><strong>If it’s not an action item </strong>-&gt; save or trash</li><li><strong>Idea, not now </strong>-&gt; <em>Later</em></li><li><strong>Someone else can do it</strong> -&gt; <em>Delegate</em></li><li><strong>One-step action -&gt;</strong> <em>Actions </em>+ set a date (recurrence too if it’s useful)</li><li><strong>More-step action / needs planning</strong> -&gt; <em>Projects </em>+ create at least the first step with a date</li></ul><p>Create a new project called “Getting Things Done”</p><ul><li>Blank project</li><li>Default view: List</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*qun3jkbsuA-el4JeVv8EYQ.png" /><figcaption>New project in Asana</figcaption></figure><p>You can customize it as you wish, I have the following suggestions:</p><ul><li><strong><em>Set the filter to “incomplete tasks” </em></strong>→ tasks disappear if you tick them Done. It will be great later, because you can filter for ‘Completed tasks’ to see how many things you have already achieved!<br>Having the motivation is important, especially in cloudy days</li><li>You can order tasks by deadline</li><li><strong>! Save view</strong> (at the right side) to keep the changes</li></ul><p>Add the following sections:</p><ul><li><strong>What’s in mind?</strong> (<strong>optional</strong>, you can just collect on the top): this is where you will empty your head out</li><li><strong>Actions:</strong> things you need to do</li><li><strong>Projects: </strong>things you need to do taking more step</li><li><strong>Delegate:</strong> things you need someone else to do</li><li><strong>Later</strong> — or not: things you may want to do / think about later</li></ul><figure><img alt="The project view isopened, and the five sections are visible below each other" src="https://cdn-images-1.medium.com/max/1024/1*X0hAFgK1Gt-ACwwIQaHwbw.png" /><figcaption>GTD project with the sections added</figcaption></figure><p>After the project is created, I do something similar to the official process:</p><figure><img alt="Visualizing the steps I will talk about later." src="https://cdn-images-1.medium.com/max/412/0*_PQwFjv8HYWlX-qq" /><figcaption>GTD process</figcaption></figure><blockquote>The following steps are the ones you need to make a habit of</blockquote><h3>1. What’s in mind?</h3><p>Sit down, stare into the abyss (but not until it stares back at you), and write EVERYTHING out of your mind into new tasks:</p><ul><li>Take your time</li><li>Don’t filter anything; if you have a picture of a unicorn that keeps coming back to your mind -&gt; write it down too! There must be a reason why it’s there</li><li>At the end your mind should be completely empty and calm</li></ul><p>I like to do this exercise before I go to sleep. If you have never done it, or much time has passed since, prepare that you will have A LOT OF tasks. The more frequently you do this, the less things will accumulate in your head.</p><blockquote>You will be surprised how many things are going on in your head</blockquote><figure><img alt="Project view is open, the section “What’s in mind” contains many tasks, for example: “pay for garage”, “learn to play guitar”, “vacation with my partner”, “try horse riding”" src="https://cdn-images-1.medium.com/max/1024/1*D-kxd8GbOxwqqljwonrTLQ.png" /><figcaption>Example tasks collected, not yet organized</figcaption></figure><h3>2. Sort things through</h3><p><strong>If it’s not an action item</strong>, you just need to categorize it and you’re done!</p><ul><li>Save it as a reference (bookmark, add to Drive, etc.) ✔️</li><li>Trash if it’s something useless️️ ✔️<br>-&gt; “<em>Later</em>” if it keeps coming back</li><li>Put in the “<em>Later</em>” section️ (✔️for now)<br>-&gt; think about it later</li></ul><p><strong>If it’s an action item</strong>:</p><blockquote>The MOST important step: if you can do it in 2 minutes, DO IT NOW! <br>Don’t delay it anymore. ️️️️✔️️</blockquote><h4>If it’s just an idea / you don’t have time for it now</h4><ul><li>Move to “<em>Later</em>”</li><li>Forget about it, you can always come back later and scan this section when you have extra free time ✔️️</li></ul><figure><img alt="Project view, later section with examples: “Try horse riding”, “Try the new coffee place at the corner”, “A fun product idea”" src="https://cdn-images-1.medium.com/max/902/1*xjWsLJ3YzZdCeX6kbM8uhg.png" /><figcaption>Example tasks in Later</figcaption></figure><h4>If you can delegate, delegate!</h4><blockquote>Super important for people like me who tend to take on a lot of stuff</blockquote><ul><li>Move to “<em>Delegate</em>”</li><li>Set a deadline when you will kindly remind the other person</li></ul><p><em>Get my friend’s cheesecake recipe: I write him now (&lt; 2 minutes), and I’m waiting for him to look for it.</em></p><figure><img alt="Project view, task example under delegate section: “Get my firend’s cheesecake recipe”" src="https://cdn-images-1.medium.com/max/904/1*UEVoWY1lVa3k_6m8u394rg.png" /><figcaption>Example task in Delegate</figcaption></figure><h4>If it requires only one step, but takes more than 2 minutes</h4><p><em>(or your own magic number)</em></p><ul><li>Move to “<em>Actions</em>”</li><li>Set a realistic deadline</li><li>Set recurrence if it helps</li></ul><figure><img alt="Project view, task example under Actions section: “Pay for garage (with recurrance)”, “Collect cloths from dressmaker”,”Practice singing”" src="https://cdn-images-1.medium.com/max/892/1*Y1EbsD2gouVmil0GNsQ8gw.png" /><figcaption>Example tasks in Actions</figcaption></figure><p><em>Pay for garage: I need to pay every month, so I set a monthly repetition:</em></p><figure><img alt="Pay for garage task, calendar is open to set a start day and recurrance" src="https://cdn-images-1.medium.com/max/822/1*HZhmI6AR_SeF6Z_ZM9GABw.png" /><figcaption>How to set a task for every month</figcaption></figure><p><em>Practice singing: I don’t have a clear plan for this, so I just aim for one day, and set “Periodically”, which means that upon competition Asana will create another task for two days later</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*B4RjmLRZiP7fOQVGqgKcFw.png" /><figcaption>How to set recurrence that only creates a new task when the original is done</figcaption></figure><h4>Requires more steps / some planning to finish it</h4><ul><li>Move to “<em>Projects</em>”</li><li>Set a deadline only if you need to finish it until</li><li>Create at least the first step as a sub-task</li><li>Set a realistic deadline to the first step</li><li>(Optional) you can add the sub-task(s) to the project’s Action section</li></ul><figure><img alt="Project view, example tasks in projects section: “Motorcycle tour”, “Learn to play guitar”, “Vacation with my partner”" src="https://cdn-images-1.medium.com/max/907/1*jCdxYCPd0teeAGCRqmYT6g.png" /><figcaption>Example tasks in Projects</figcaption></figure><p><em>Motorcycle tour: during the long weekend we plan to go on a tour with my partner. This project has a deadline because we need to leave on the 27th of April. The first step is also dated, as it needs to be started soon.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*1UNeEirvmfV95Caw-m0-ow.png" /><figcaption>Sub-tasks created for motorcycle tour</figcaption></figure><p><em>Learn to play guitar: No rush with this one, so only the first step is dated.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*MOi20tqT143a8YV1mbawtQ.png" /><figcaption>Sub-tasks created for playing guitar</figcaption></figure><ul><li>At this point, I start to realize that I have too many things to do, so I move “Vacation with my partner” to <em>Later</em>.</li><li>My partner agreed to do the road planning, so I move Motorcycle tour to <em>Delegate</em>, but keep the dates (it will be a reminder now)</li></ul><p>After sorting everything out:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YgDH1ItlzaUIoFQdI3UTxA.png" /><figcaption>Getting Things Done project after “What’s in mind” is sorted</figcaption></figure><p>You can switch to Calendar view, and see the tasks with deadlines:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cllmQFBXSbZ_PYsld5q-jg.png" /></figure><h4>Export to your calendar</h4><ul><li>You only need to set this once</li><li>Copy the URL, and subscribe to it</li></ul><figure><img alt="Asana project settings showing the option to export calendar" src="https://cdn-images-1.medium.com/max/968/1*OVfZ3R625WyYn_R1RVgOPw.png" /><figcaption>How to synchronize the tasks with dates</figcaption></figure><p>I usually don’t set time to the deadlines because I like to see the tasks as all-day events, but if you want to, it is allowed in Asana.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g44aa8Wc19ftIvxgymjcuQ.png" /><figcaption>Google Calendar synchronized with To Do tasks from Asana</figcaption></figure><p>Voilà! Now if you set deadline to a task in your GTD project, it will appear in your calendar.</p><h3>3. Actually do what you planned!</h3><p>Super important, otherwise you will lose motivation.</p><ul><li>Don’t overwhelm yourself, plan longer dates if needed, you can always finish them earlier if you find the time</li><li>If you find yourself moving the tasks from day-to-day, move everything to later, and give yourself an empty week. Having a lazy time is completely ok, you need your break sometimes</li><li>Finishing less stuff consistently is much better than planning tightly and keep moving them. You will experience with time how much time you need between the tasks</li><li>Be careful with recurring tasks because they can easily overwhelm you. Use the <em>“Periodically” </em>option if you’re unsure that you will do them regularly</li></ul><p>Feel free <a href="https://www.linkedin.com/in/reka-szellmann/">to reach out</a> if you have any questions, I’m happy to help!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98094b1cdb22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why do we struggle to implement Agile, and what can we do about it?]]></title>
            <link>https://reka-szellmann.medium.com/why-do-we-struggle-to-implement-agile-and-what-can-we-do-about-it-dcef527ba1aa?source=rss-b2b3e743c8ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcef527ba1aa</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[practical]]></category>
            <category><![CDATA[mindset]]></category>
            <dc:creator><![CDATA[Réka Szellmann]]></dc:creator>
            <pubDate>Tue, 23 Jul 2024 23:20:23 GMT</pubDate>
            <atom:updated>2024-07-24T16:06:36.931Z</atom:updated>
            <content:encoded><![CDATA[<p>Explore the social factors and understand some usual problems and solutions through examples</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qADlJTgmU2HYuqdg" /><figcaption>Photo by <a href="https://unsplash.com/@helloimnik?utm_source=medium&amp;utm_medium=referral">Nik</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Big Misunderstanding of Agile frameworks</h3><p><em>A long time ago in a galaxy far, far away</em></p><p><a href="https://en.wikipedia.org/wiki/Assembly_line">The idea of assembly lines has been with us since the 1800s… </a>Over the last <strong>centuries, </strong>we have been trying to understand how to improve efficiency and have learned that the answer lies in following best practices and creating clear, standardized processes.<br><strong>The problem is that it’s no longer effective enough. <em>But why?</em></strong></p><ul><li>Software is not a factory but knowledge work, something we have never had in mass production before</li><li>Everything changes, and rapidly</li></ul><blockquote>If all you have is a hammer, everything looks like a nail.</blockquote><p>Many professionals understood the need for a paradigm shift, so they created different Agile frameworks to promote the adoption of the Agile mindset. However, if people used to best practices and predefined processes merely adopt the frameworks, they might end up replacing old methods with new ones without truly understanding the underlying mindset.</p><h4>Why can’t we just implement the framework and learn the mindset later?</h4><p>Even implementing a framework by the book might help… if it’s truly followed and not altered into a half-baked custom solution without fully understanding the consequences. For example, simply renaming roles doesn’t mean people will automatically know what they’re doing.</p><p>But what does it mean in practice? Some of the frequent mistakes I saw when companies intended to implement <a href="https://scrumguides.org/scrum-guide.html"><strong>Scrum</strong></a>:</p><ul><li><em>“Successful use of Scrum depends on people becoming more proficient in living five values: Commitment, Focus, Openness, Respect, and Courage”<br></em>→ <strong>Scrum Values are completely forgotten</strong></li><li><em>“Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint.”</em><br>→<strong> There should be no ‘Backend team’ or ‘Frontend team’; value should be defined by customer impact.</strong></li><li><em>“Within a Scrum Team, there are no sub-teams or hierarchies”<br></em>→<strong> We should focus on having just ‘developers’ rather than distinct roles like ‘tester,’ ‘DevOps,’ or ‘backend developer.’</strong> Team members should collaborate, taking on the roles that are most needed without compromising quality. Even if team members start with expertise in a specific area, such as backend development, they should gradually become ‘T-shaped’ professionals which means that they would learn and contribute to other areas, like testing or frontend development, through supervision, pair programming, or code reviews.<br>→<strong> There should also be no team/tech leader who manages the team by directing tasks or defining processes.</strong> While support roles such as agile/tech leaders are important, their focus should be on teaching and mentoring rather than managing. Hierarchical structure is not suitable for Scrum, we want the teams to become mature and manage themselves.</li><li><em>“For Product Owners to succeed, the entire organization must respect their decisions.” + “The Product Owner is also accountable for […] developing and explicitly communicating the Product Goal”</em><br>→ T<strong>hey should have authority over the product and guide the teams with the Product Goal. </strong>Two common issues I see:<br> 1. Product Owners lack authority over the product and/or focus only on a small segment of it.<br> 2. Individuals assigned the Product Owner role from other positions don’t always understand how to manage the Product Backlog or create an effective roadmap. I have met Product Owners who were unfamiliar with even basic concepts like the Product Backlog or Sprint Backlog.</li><li><em>“The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint”<br></em>→<em> </em><strong>The Scrum team is meant to work as one, but instead of focusing on a common goal, team members often work in silos and fail to assist one another. </strong>Three possible root-causes:<br>1. There is no Sprint Goal<br>2. The ‘100% utilization’ mentality from traditional project management promotes constant activity in silos, such as developers coding and testers testing. This approach misplaces priorities; team members should focus on achieving shared goals through collaboration instead of just staying busy with coding or testing.<br>3. Lack of cross-functionality; when team members are unwilling to step outside their traditional roles, such as ‘backend developer,’ and collaborate more broadly, for example, by helping with testing</li></ul><p>Let’s also see some examples from <a href="https://en.wikipedia.org/wiki/Kanban"><strong>Kanban</strong></a>:</p><ul><li><em>A Kanban board should visualize the entire value flow<br></em>→ <strong>Instead of following the whole flow the board only focuses on a specific part like development or QA</strong></li><li><em>Kanban limits work in progress (WIP) to enhance focus, reduce bottlenecks, and improve overall efficiency</em><br>→ <strong>Some teams may skip implementing WIP limits, which are crucial aspects of Kanban.</strong></li><li><a href="https://en.wikipedia.org/wiki/Kaizen"><em>Kaizen</em></a><em> (Continues Improvement) is a key aspect of Kanban<br></em>→ <strong>Kanban doesn’t have a formal event like Scrum’s Retrospective, which may lead teams to overlook opportunities for self-improvement.</strong></li><li><em>Teams need a clear goal or purpose<br></em> → <strong>Kanban doesn’t mandate a common goal for teams explicitly, so it can be easily forgotten</strong>. However, having a direction like Product Goal is crucial, especially when multiple teams are working on the same product. It helps ensure alignment, focus, and coordination across teams, making sure that all efforts contribute toward a unified objective.</li><li>Teams switching to Kanban simply because they can’t complete tickets within a sprint often aren’t truly adopting Kanban. Instead, they’re just trying to hide the issues that Scrum has made visible.</li></ul><figure><img alt="Sing: This is the sign you’ve been looking for" src="https://cdn-images-1.medium.com/max/1024/0*GG1EUTjUo7-abvs9" /></figure><h3>Well then, how can implement the Agile mindset?</h3><p>Bad news, there’s no predefined recipe for this either… We need to be <em>very</em> patient and keep emphasizing the <a href="https://agilemanifesto.org/">Agile values and principles</a>. If anyone sees that something is not working accordingly, they should highlight it so the team can handle it more effectively next time.</p><blockquote>Use common sense: how can you resolve something the most effective way?</blockquote><h4>Let’s look at some typical red flags that can be spotted by anyone</h4><ul><li><em>There are 8+ comments under a ticket<br></em>→ it can be a sign that <em>the team avoids direct communication.</em><br>I’ve seen a conversation going on for a month under a JIRA ticket which could have been a 10-minute call instead</li><li><em>The team is very passive, reactive only<br></em>→ There can be multiple reasons, but a common one is that <em>the team is told exactly what to do and how to do it -&gt; </em>This prevents them from learning how to self-organize and leads them to wait for instructions rather than taking initiative.</li><li><em>Developers are only allowed to talk to their manager / the Product Owner<br></em>→ developers should be able to directly call stakeholders for clarification. Avoid indirect communication, as it often delays progress and causes information to be lost</li></ul><h4>Advice for leaders:</h4><ul><li><em>Don’t try to solve everything</em>; let the team fail and learn from it. Michael Jordan’s quote sums it up: “To learn to succeed, you must first learn to fail.”</li><li><em>Don’t share your opinion until your team has had a chance to express theirs</em>. They might be influenced by your views, and if you’re higher in the hierarchy, it’s natural for them to hesitate to speak up against your perspective.</li><li><em>Try counting to 10 in your head before responding to or closing a question. </em>Some people feel uncomfortable speaking up and - despite having brilliant ideas - won’t speak up until they’re certain no one else will respond.</li><li><em>Show that you value and act on people’s feedback</em>, or they may stop offering it.</li></ul><h3>What can be your next step?</h3><ol><li>You can learn from case studies, such as those in <a href="https://less.works/case-studies">LeSS</a> (where the early books focus heavily on case studies). I also have another article covering <a href="https://medium.com/@reka-szellmann/scaled-agile-case-studies-8865a5670770">scaled agile case studies</a>.</li><li>Understand the framework you’re currently using and identify what you might be missing from the original guidelines (e.g., the <a href="https://scrumguides.org/scrum-guide.html">Scrum Guide</a> for Scrum). Follow the <a href="https://en.wikipedia.org/wiki/Shuhari">Shu-Ha-Ri</a> approach: master the rules first, then break the rules only if you fully understand their purpose and consequences.</li><li>Learn more frameworks to understand possible problems and how they intend to solve them. While no framework will fit perfectly for every product, knowing more options allows you to customize effectively. For example, you might use Kanban’s Work In Progress (WIP) limits in Scrum, not just to restrict column limits on the board, but also to limit new tickets added.</li></ol><p>Let’s close with a positive thought: everything can be fixed if people are willing to learn and change. If you’re feeling overwhelmed, start with small steps! <a href="https://en.wikipedia.org/wiki/Five_whys">Ask why until you arrive to one root cause</a>, and start working on that! You can also ask ChatGPT, it’s a great tool for brainstorming.</p><p>Don’t forget to celebrate what you’ve already achieved! 🎉 Like finishing this article! I hope you’ve learned something new or reinforced what you already knew.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0K1t9Yz83ngqq-i-" /><figcaption>Photo by <a href="https://unsplash.com/@clarktibbs?utm_source=medium&amp;utm_medium=referral">Clark Tibbs</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcef527ba1aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scaled Agile case studies]]></title>
            <link>https://reka-szellmann.medium.com/scaled-agile-case-studies-8865a5670770?source=rss-b2b3e743c8ba------2</link>
            <guid isPermaLink="false">https://medium.com/p/8865a5670770</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scaled-agile]]></category>
            <dc:creator><![CDATA[Réka Szellmann]]></dc:creator>
            <pubDate>Sat, 30 Mar 2024 21:09:38 GMT</pubDate>
            <atom:updated>2024-03-31T20:25:07.422Z</atom:updated>
            <content:encoded><![CDATA[<h3>What are the most typical scaling problems, how to overcome them, and some case studies</h3><figure><img alt="Colorful wass with terrace grids" src="https://cdn-images-1.medium.com/max/1024/0*O6eAnrFGI6bL-TJF" /><figcaption>Photo by <a href="https://unsplash.com/@ninjason?utm_source=medium&amp;utm_medium=referral">Jason Leung</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The world is not black and white but very colourful!</h3><p>Let’s start by stating that none of the solutions is universally “good” or “bad”. The more you learn, the bigger toolset you will have to tailor your own environment.</p><p>We are all in a journey, <em>nothing is ever perfect</em><strong>. </strong>Even the companies mentioned below have many areas to improve<strong>. </strong>But hey, it’s good news, because it means that there is always room for improvements!</p><h3>Difficulties coming from scaling</h3><p>The bigger the company gets, the more difficult it will be to deliver complex software.</p><h4>Some of the most typical scaling problems</h4><ul><li>Growing legacy systems</li><li>Complexity, dependencies on other systems</li><li><a href="https://www.pmi.org/learning/library/overcoming-communications-complexity-ambiguity-projects-6631">Complexity of communication</a></li><li>Bureaucracy, change resistance</li><li>Losing sight of the big picture</li></ul><h4>How can we overcome them?</h4><p><strong><em>Lean, Agile, and engineering practices are all important; </em></strong>Having a good mindset helps you avoid endless bureaucracy and micromanagement. On the other hand, you need the right engineering practices to be able to focus on the important work instead of wasting your time on repeating manual work. <a href="https://medium.com/@markbarbs/the-7-wastes-of-lean-software-development-1a6acbe9d5d7">See the 7 wastes of Lean for software development.</a></p><p>I find these especially important:</p><ul><li><strong>Clear vision</strong> constantly communicated by product, and connected to everyday development</li><li><strong>High transparency in team structures</strong> (Who is working on what?)<br>-&gt; so, teams can self-organize their work with other teams</li><li><strong>Continuous Integration</strong> for frequent code integration</li><li><strong>Continuous Delivery</strong> for frequent customer feedback</li><li><strong>Create a culture which attracts and keeps talent</strong><br>(<a href="https://fortune.com/2016/03/07/fast-growth-companies-fail/">Why Two-Thirds of the Fastest-Growing Companies Fail</a>)</li></ul><h3>Case studies</h3><h4>Spotify</h4><p>You can learn about scaled Agile, and engineering practices implemented in Spotify:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYvfz4HGtoPc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYvfz4HGtoPc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYvfz4HGtoPc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2cf1586f1bb617f34fcb223418328a63/href">https://medium.com/media/2cf1586f1bb617f34fcb223418328a63/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FvOt4BbWLWQw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DvOt4BbWLWQw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FvOt4BbWLWQw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/975a718214398d082696102b14932d2a/href">https://medium.com/media/975a718214398d082696102b14932d2a/href</a></iframe><h4>PayPal</h4><p>To make scaled changes you usually need an iterative approach, because big bang solutions carry a huge risk and can easily fail. Well... they can, but not always. You can see a counter example with PayPal:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FFtzJjbEATKk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DFtzJjbEATKk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FFtzJjbEATKk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/be381c344e87faf665ef76609a6d709d/href">https://medium.com/media/be381c344e87faf665ef76609a6d709d/href</a></iframe><h4>Microsoft</h4><p>You can learn about the technological, and process changes that helped Microsoft to reduce release time from 3 years to 3 months:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fnno6DwevspI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dnno6DwevspI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fnno6DwevspI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b25d1aee3417ab2d33ed53d54f7cf38d/href">https://medium.com/media/b25d1aee3417ab2d33ed53d54f7cf38d/href</a></iframe><p>What do you find easy and challenging in scaling? Do you have any advice? Let us know in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8865a5670770" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>