<?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 Krisna Parista on Medium]]></title>
        <description><![CDATA[Stories by Krisna Parista on Medium]]></description>
        <link>https://medium.com/@krisna.parista?source=rss-169cef473e7c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*gZsJEc-JzTIL-fQz</url>
            <title>Stories by Krisna Parista on Medium</title>
            <link>https://medium.com/@krisna.parista?source=rss-169cef473e7c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:56:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@krisna.parista/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[Delivery Control Dashboard]]></title>
            <link>https://medium.com/@krisna.parista/delivery-control-dashboard-d9345692501c?source=rss-169cef473e7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9345692501c</guid>
            <dc:creator><![CDATA[Krisna Parista]]></dc:creator>
            <pubDate>Fri, 17 Jul 2026 14:04:23 GMT</pubDate>
            <atom:updated>2026-07-20T14:55:36.957Z</atom:updated>
            <content:encoded><![CDATA[<p>#Agile #Project Management #AI #productivity #SoftwareDevelopment</p><p>Berlin, 14.07.2026.</p><p>Hi, my name is Krisna. For the past months I have been working with Comdecon (Computational Design Consulting) here in Berlin as Project Management Officer.</p><p>I am doing a Dashboard Vibe Coding with Claude Fable. I seriously love Fable.</p><p>👉 <strong>Now You Can Try It Here</strong></p><p><a href="https://krisnaparista.github.io/delivery-control-dashboard/">https://krisnaparista.github.io/delivery-control-dashboard/</a></p><h3>Pain Point: When can we deliver?</h3><p>The real problem, in my view, is that story points are inherently vague and humans are bad at absolute estimates. Stakeholders push the Product Manager “When can we deliver?” so the Product Manager and Project Manager sit down with the Tech Lead to work it out. And the honest answer is rarely as clean as “by the end of the sprint.”</p><p>So I wanted to build a tool that doesn’t judge how fast developers work. It simply makes the delivery-date assumption visible. To do that, I connected the burndown chart to a delivery-date prediction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v6GBCVs8HbCSxvlR9KOnPQ.png" /></figure><h3>The Requirements</h3><p>The classic tool for this is a burndown chart. Picture a line that starts with all your work on the left and slopes down to zero as you finish things. If it hits the floor before the deadline, you make it. Simple idea.</p><p>The problem is most of these charts quietly lie. They pretend the team is free five full days a week. They ignore meetings. They show one confident number for work nobody can size that precisely. Then the deadline slips and everyone acts surprised.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7VCEPMy5oMLW1i84vh6GDQ.png" /></figure><h3>Result:</h3><p>One HTML file. You double-click it and it opens in your browser. That is the whole install.</p><p>Try the live demo here:</p><p><a href="https://krisnaparista.github.io/delivery-control-dashboard/">https://krisnaparista.github.io/delivery-control-dashboard/</a></p><p>The file itself lives on <a href="https://github.com/krisnaparista/delivery-control-dashboard">GitHub</a>, with a short guide to connect it to your own board.</p><h3>Lesson Learned</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NNfoD1ZRPuxdV_mFfbnbCg.png" /></figure><h4>Part 1: Will We Make It?</h4><p>This question is Stakeholder’s favorite question, and Developers’ most hated question. Not “July 20th, happy path.”</p><p>but it’s more like a range date“somewhere between October 6 and 19, most likely the 13th, here is the bottleneck and the Backend work is solving it.”</p><h4>Part 2: People, Not Resources</h4><p>Each person is a lane on the board with two dials: how much of their time this project actually gets, and a rough pace. Each pace is labelled either “measured” or “assumed”, so you always know which numbers are real and which are hopes.</p><p>But that pace is never a personal score. The tool never tracks how long someone took on a task. The person only carries a “fit”: good, okay, or a stretch. A stretch assignment costs more effort, so the math naturally steers work toward the person it suits best.</p><p>Meetings get the same honesty. Planning, reviews and sync calls each subtract their real cost from the week. Everybody knows meetings eat into delivery time. Almost no forecast admits it.</p><p>Task cards with size ranges, and the calculation shown live <em>The full calculation is printed on the page. When the date moves, you point at the line that changed. No black box.</em></p><h3>The Cool Part</h3><p>So how do the real numbers get in? Your AI assistant fetches them.</p><p>The page gives you a ready-made instruction. You paste it into an assistant like Copilot, Claude or Codex. The assistant reads your project board, and hands back a small block of data. You paste that block into the page. Two minutes, and it works with Jira, Azure DevOps and Trello.</p><p>The dashboard itself stores no passwords and touches nothing. Your AI has the access, the page just does the math. That split is cleaner and safer than most reporting tools I have used.</p><p>The data sync section: copy the instruction, paste the data back <em>The page ships with a made-up project so you can click around and break nothing.</em></p><h3>My End Thoughts</h3><p>So, that is it. And tell me in the comments: What do you think?</p><p>I’m open for suggestion and improvement.</p><p>It helps us shape the next version.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9345692501c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mind Dump Mobile-App with Claude Fable (MVP 2)]]></title>
            <link>https://medium.com/@krisna.parista/mind-dump-mobile-app-mvp-2-f541a725ead4?source=rss-169cef473e7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f541a725ead4</guid>
            <dc:creator><![CDATA[Krisna Parista]]></dc:creator>
            <pubDate>Tue, 14 Jul 2026 19:51:59 GMT</pubDate>
            <atom:updated>2026-07-17T14:27:47.348Z</atom:updated>
            <content:encoded><![CDATA[<p>Mind Dump App (MVP 2):</p><p>👉 <strong>Now You Can Try It Here </strong><a href="https://krisnaparista.github.io/mind-dump-prototype-public/">https://krisnaparista.github.io/mind-dump-prototype-public/</a></p><p><em>Berlin, 14.07.2026</em></p><p>Hey, I’m back.</p><p>In <a href="https://medium.com/@krisna.parista/mind-dump-app-mvp-1-c2710d9d3d9f">Part 1</a> I built a little mobile-app to catch the ideas that pop into my head on my daily Berlin walks. The idea is as simple as dump the thought on my phone, sort it later on my Mac. It works, I use it every day, and I’m genuinely proud of it.</p><p>So for this part, I am doing Vibe Coding with Claude Fable: <strong>let anyone try it, right in the browser, without installing anything. So okay, this is what I have done. It is not perfect, but I’m damn proud of myself! :)</strong></p><p>👉 <strong>Try it live here:</strong> <a href="https://krisnaparista.github.io/mind-dump-prototype-public/">https://krisnaparista.github.io/mind-dump-prototype-public/</a></p><h3>MVP 1 vs MPV 2</h3><p>Actually, it’s just about the UI.</p><p>This is the Minimum Viable Product — MVP 1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/0*bLyw6eoQDhQcnmxg.png" /></figure><p>This is the Minimum Viable Product — MVP 2.</p><p>I kept the rules the same as Part 1 — free, local, no accounts, no subscriptions. On top of that:</p><ul><li><strong>A new, playful UI.</strong> It is supposed to be “not boring”.</li><li><strong>The real dashboard.</strong> People should see not just where thoughts go in, but how they get sorted afterward.</li><li><strong>Nobody can ruin it for the next person.</strong> A public demo everyone shares shouldn’t turn into a mess.</li><li><strong>Zero cost to run.</strong> Still $0. Hosted for free on GitHub Pages for demo and I love it.</li></ul><h3>Result MVP 2: The Interactive Page</h3><p>So I made a change to the UI and I also duplicate it to Public Repo for anyone to try (if you’re interested).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mYrM4KUWWYJJ9QRy_sKTZg.png" /></figure><h4>Part 1 — Meet the Muncher</h4><p>Instead of a text box, you get a hungry blue monster. You type your stray thought <em>into its mouth</em>, hit the big yellow <strong>GULP!</strong> button, and it chomps! That simple, actually. It’s silly, but hey! That’s the point. It also blinks at you every ten seconds while it waits.</p><h4>Part 2 — Sort It (the Dashboard)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*usQfebHgT_xSEjwnrbMFsQ.png" /></figure><p>There’s a bar chart of tasks by quadrant, a donut of tasks by status, and a table you can manually edit: set urgency, importance, status, notes.</p><p>The quadrant (Do First / Schedule / Delegate / Backlog) is worked out automatically from urgent + important, the classic Eisenhower way.</p><p>And because I mostly capture on my phone, I added a <strong>Browser / Phone</strong> toggle.</p><h3>The Part that I like: it’s free</h3><p>Here’s what still surprises me: <strong>the entire thing is one HTML file.</strong> No server. No database. No backend. No account. No cost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ERyfNTkKQENCpL94g8tmhg.png" /></figure><p>The whole demo is a faithful little simulation of the real system which runs locally across an Android app and a macOS dashboard, talking to each other through plain files. The web page is the <em>brochure</em>, not the product.</p><p>Oh, and there’s a <strong>“Found a bug?”</strong> button in the corner. I’m constantly improving.</p><h3>Try it, then tell me</h3><p>That’s MVP 2 — the app is no longer just mine.</p><p>👉 <strong>Play with it:</strong> <a href="https://krisnaparista.github.io/mind-dump-prototype-public/">https://krisnaparista.github.io/mind-dump-prototype-public/</a></p><p>Then let me know what you think and if the monster eats something it shouldn’t, there’s a button for that.</p><p>Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f541a725ead4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mind Dump Mobile-App with Claude Fable (MVP 1)]]></title>
            <link>https://medium.com/@krisna.parista/mind-dump-app-mvp-1-c2710d9d3d9f?source=rss-169cef473e7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2710d9d3d9f</guid>
            <dc:creator><![CDATA[Krisna Parista]]></dc:creator>
            <pubDate>Fri, 10 Jul 2026 19:41:00 GMT</pubDate>
            <atom:updated>2026-07-15T11:45:04.604Z</atom:updated>
            <content:encoded><![CDATA[<p>Berlin, 10.07.2026.</p><p>Hi, my name is Krisna.</p><p>Recently I have moved to Berlin and everyday walk approximately 10,000 steps. (compared to Bali, I go everywhere with scooter). Everytime I walk suddenly I get some insights. That’s amazing.</p><p>I wasn’t trying to become a software engineer (I am a PMO). I wanted to understand the technical side well enough to ask better questions with Claude Fable. This helps me better ask for a more scalable, replicable, and maintainable version.</p><p>Most of the time, I don’t know what I’m doing and it’s frustrating. The result isn’t perfect, but I’m genuinely proud of how far I came.</p><h3>Pain Point: Fleeting Ideas</h3><p>It’s been said that people get ideas and to-do-lists when they walk. The moment they remember it, it will be gone. They can only remember for a very short time, sometimes, it can be just within seconds. So, here it is, I create “mind dump and sort it later”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*44ZIgu6MdhdnZs3yUOmwOA.png" /><figcaption>The Pain Point</figcaption></figure><h3>The Requirements MVP 1</h3><p>So, here’s it. Start small. My goal for <strong>MVP 1 (Minimum Viable Product 1)</strong> is just enough; simply to build something that work. Then I tried to use Claude Fable to make a prototype, and I thought about the requirements using the MoSCoW method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zqdSbcoyak_HyT2XXXdi2g.png" /></figure><p>Additional Notes:</p><ul><li>Zero third-party dependencies except syncthing-fork (supply-chain and maintenance surface stays minimal).</li><li>All effects (animation/sound) generated in code — APK stays &lt; 1 MB, no asset pipeline.</li><li>Respect Android lifecycle: blink loop attaches/detaches with the view; sync writes are atomic per-file (unique names, single write).</li><li>Never read possibly-dataless cloud placeholder files (legacy Google Drive lesson); the Mac side skips blocks==0 files.</li></ul><h3>Result:</h3><h4>Part 1: Dump It!</h4><p>By the way, I hate this Claude Fable’s message <em>“usage limit reached”</em> message. So it took me 2 days to build this simple Mobile-App. I did it!</p><p>On my <strong>Android Mobile-App,</strong> I just need to write things down and hit the “Dump It” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*I8woQEA_uUvpPPWplfiFsQ.png" /></figure><h4>Part 2: Sort It!</h4><p>And then, when I arrive back home, I can see the Mind Dump list on a simple, nice, and clean dashboard on my MacBook.</p><p>After the dumping part, now it’s time to sort it out.</p><ul><li>MoSCoW: Must Have, Should Have, Nice to Have, Not to Have</li><li>Urgency &amp; Importance: each Y/N, and the output is automatically set on the Quadrant: Do it Now, Schedule, Delegate, or Backlog it.</li><li>I can change the status (To Do, WIP, Review, Done).</li><li>I can change the rules.</li><li>There is start date, end date, deviation, and due date.</li><li>Intuitive Charts.</li></ul><p><strong>This is pretty cool; a beautiful one-page dashboard:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mk6MUQnX0_38GvqODJ1GLw.png" /></figure><ul><li>Another important automatic Output suggestion: Automatable, Assistable with AI, High Leverage.</li></ul><h3>The Cool Part</h3><p><strong>Why does this work better than a traditional checklist?</strong></p><p>Because I’m not just tracking tasks. I’m collecting data. Every mind dump becomes a data point that helps me understand my thinking patterns. From there, I can automate repetitive work and batch everything else.</p><h3>Lesson Learned: Bridging Discipline</h3><p>Nowadays, almost anyone can build an app. I’m not a software developer, yet I built a mobile app. But here’s what I learned as a non-tech (PMO, to be precise):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LX0_ckpwB5jWjCL0QOiI8Q.png" /></figure><p>Next article will be the MVP 2, with a beautiful layout hopefully. I will also build a web-page for the prototype.</p><p>Let me know your thoughts.</p><p>Thank you for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2710d9d3d9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum Master’s Dilemma: To Participate or Not in a Retro]]></title>
            <link>https://medium.com/@krisna.parista/scrum-masters-dilemma-to-participate-or-not-in-a-retro-3a4399a3e705?source=rss-169cef473e7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a4399a3e705</guid>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Krisna Parista]]></dc:creator>
            <pubDate>Wed, 03 Jan 2024 11:17:22 GMT</pubDate>
            <atom:updated>2024-02-01T08:38:04.927Z</atom:updated>
            <content:encoded><![CDATA[<p>#Retrospective #AgileJourney #TeamEmpowerment</p><p><strong>Hi Scrum peeps, love your passion for Agile!</strong></p><p>Let’s say you are a new Scrum Master at a company, and finally, you are facilitating your first Retrospective, but your team wants to know your opinion, too. So, you’re wearing Scrum Hats, the facilitator, the coach, etc. The question is, wondering if you can switch roles from moderator to active participant in a Retro?</p><p>Let’s dive into the Agile world and find out.</p><h4><strong>Why Not?</strong></h4><p>Well, the answer is, “Why not?”</p><h4>Based on Reference</h4><p>The description from SAFe indicates that the Scrum Master facilitates but also says that “The entire team participates in the retrospective.” According to SAFe’s definition, the entire team includes the Scrum Master and the Product Owner.</p><h4>Terms and Conditions</h4><p>As a Scrum Master, your main gig is serving the team! It’s natural that your team wants to know your opinion. The Developers and QAs might bring up some topics that you can give interesting perspectives. Your observations about blockers and impediments are gold; so it’s okay to share your observations but not judgments. Let them figure out the solution (not you!), because they are the experts.</p><p>Here is the tricky part, though — if you’re silent and insist to become the moderator role, then this will put you in a bad position. They’ll ask, “Didn’t you learn anything from us?” or the opposite, when you over-shared, “Ah, you’re talking too much!” You don’t want to dominate the conversation because it’s really a bad vibe!</p><h4>Conclusion</h4><p>The Retro’s goal is to create a culture of continuous improvement. If your active participation is what they want, then dive in! But if it’s a vibe killer, stick to the facilitator role. So, Scrum Masters, put on your cool hats, strike a pose and go for it!</p><p>What do you think? Let me know your thoughts.</p><h4><strong>Reference</strong></h4><p><a href="https://scaledagileframework.com/iteration-retrospective/?fbclid=IwAR0vWY4sn4jkWhZ8xGZrqRpypKDcZiv54Lzh3DAQ4hxxheYBJ8wBkfhi09E">https://scaledagileframework.com/iteration-retrospective/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a4399a3e705" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Incorporate Retrospective into your Remote Team]]></title>
            <link>https://medium.com/julotech/how-to-incorporate-retrospective-into-your-remote-team-ae2b45a6c188?source=rss-169cef473e7c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae2b45a6c188</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Krisna Parista]]></dc:creator>
            <pubDate>Wed, 12 Apr 2023 08:27:32 GMT</pubDate>
            <atom:updated>2023-04-12T08:27:32.423Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to do Retrospectives with your Remote Teams</h3><h3>Introduction</h3><p>I joined JULO as a Scrum Master in Q3 of 2022. Scrum had already been implemented at the time but doing retrospectives effectively was a big challenge as the Developers work remotely. Over time, I’ve come up with a few techniques to take on this challenge that may be useful for others.</p><h4><strong>Work from Anywhere</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zr0nRU_lxd5P50WIjeHx2g.jpeg" /><figcaption>JULO Engineering Team Outing in Bogor, 2022</figcaption></figure><p>Last year, Engineering teams organized an outing as a chance for everybody to meet one another in-person. Since the pandemic hit, the Developers have been working remotely. Most of us in Jakarta, some in Bandung, and a few others in other cities. Around the same time, the teams also have grown. For product engineering, JULO comprises into 6 tribes, each containing 11 Squads. Therefore, delivering products requires us applying a framework effectively.</p><h4><strong>Retrospective as part of Scrum Framework</strong></h4><p>A framework like Scrum is<em> </em><strong><em>purposefully incomplete</em></strong> so that the team adds whatever necessary to reach the goals. It provides a basic structure, guidelines and principles. Like Google Map showing places relative to one another. For directions, it provides the starting and the end points as well as the recommended route. However, <strong>it gives</strong> <strong>flexibility</strong> how we are going to take the path. We believe the Retrospective is an essential part of the Scrum that often requires flexibility to make it work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rEBMcNgASNV1aRkO" /><figcaption>Scrum Framework in JULO</figcaption></figure><h3>The Retrospective Questions to Ask</h3><blockquote>“By the end of the sprint, the team inspects the processes, tools, individuals, interactions.”- Scrum Guide</blockquote><p>Based on the well-practiced guide, there are four questions that we ask as a template for the squads:</p><ol><li>Is there anything that makes you frustrated and the team should drop it?</li><li>Do you have any ideas you’d like to introduce in our team?</li><li>What would you like to keep in our team and why?</li><li>What is your burnout rate level?</li></ol><h3>4 Elements of the Retrospective for our Remote Teams</h3><p>We’ve learned that for retrospectives to be effective, we have to starting thinking about it before the session, we have to have some guidelines, get in the mindset of problem solving, and go out with actionable items.</p><h4>1. Preparation</h4><p>We use two online tools that are essential for preparations:</p><ul><li><a href="https://retrotool.io/">Retro Tool</a> app for online retrospective boards,</li><li><a href="https://methods.yerbo.co/">Yerbo</a> app to measure the burnout level.</li></ul><p>The links to the Retro Tool and Yerbo app are sent one hour before the meeting, so the squad members can give their thoughts earlier separately. This will maximize the 1 hour session for a full discussion.</p><p>If some of the squad members are unable to join, they are responsible to inform the squad on Slack and provide a valid reason for it. However, they still need to share thoughts on the retrospective questions.</p><p>If most of the squad members are busy, we reschedule the retrospective instead of cancelling because it’s an essential activity for the squad to inspect and adapt as they work together.</p><h4>2. Guidelines</h4><p>We conduct retrospectives on Google Meet and participants are expected to have their cameras on. To strengthen personal connections between members, I ask the team to open their camera. A picture is worth a thousand words and a video amplifies that saying. When we see one another, squad members can be focused and actively participating, creating the same atmosphere like being physically present with one another. We also encourage live chats during the session and sometimes it can start with ice-breaker topics to get to know the people more.</p><p>When discussing difficult technical problems, for some members it can be difficult to communicate in English. We allow everybody to speak in Indonesian first and have others translate the meanings to English. Another example of having some flexibility to increase engagement.</p><p>We believe having a meeting agenda creates structure and gives full context so the session can be effective. The meeting agenda is divided into 4 sessions:</p><ul><li>Reviewing Jira Reports. Mainly looking at the Completion Rate, the Sprint Burndown and the Velocity update.</li><li>Evaluating action plans from previous retrospectives.</li><li>Discussing the points gathered on the retro board.</li><li>Summarizing the action plans.</li></ul><p>Finally, the participants are limited for the Scrum Team only (the Product Owner, the Scrum Master, the Developers). The Stakeholders are typically not invited, as their presence might make the members hesitant to open up.</p><h4><strong>3. Problem Solving Mindset</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*FYd3Vqyg2uypYp82lrPAew.png" /></figure><p>Like in the onsite setting, we gather all insights on the retro board and base our discussions from there, so that we can get into the problem solving mindset.</p><p>Despite having the preparations and guidelines above to overcome the lack of in-person interactions, minor things being expressed can still be understood the wrong way. So, there is a simple mindset that I repeat in every session to ensure to eliminate hard feelings.</p><blockquote><strong><em>“Attack the problems, not the people.”</em></strong></blockquote><p>Discussing a failure on achieving the sprint goals is typical. However, certain problems require more in depth discussions. In these cases, we branch out the retrospective into a <strong>separate Root Cause Analysis (RCA) session</strong> per each problem. At JULO, we normally produce RCA documentation and organize sessions for solving technical problems, and we utilize the same format for feature development issues.</p><p>Comparing retrospectives and RCA sessions:</p><ul><li>Retrospective: discussing based on the start-stop-continue questions</li><li>RCA: discussing what went wrong, what the impacts are, how likely it would happen again, how can it be detected, solutions and mitigation actions to prevent similar problems in the future.</li></ul><p>We can see the RCA format extends the Retrospective questions deeper, giving an effective way to address why particular feature development has failed and to address prevention.</p><p>To ensure everyone’s concerns are heard and addressed, as a Scrum Master, the key mindset <strong>for me is to ask open-ended questions</strong>. I take notes from comments and opinions that each member says during daily stand-ups during the sprint. During the session, if the team is being silent, I would ask specific members a question like “How is your workload? I remember you saying that in the past few sprints have been tough for you. Would you like to elaborate on that?” This usually helps to kick start in-depth discussions.</p><h4><strong>4. Closing</strong></h4><p>In retrospectives, I act as the facilitator. So I ensure that at the end I wrap up the session by summarizing all the points mentioned and repeating the action plans, which may be taken directly in the next sprint or to be done over time across sprints. After the meeting, I write everything down as retrospective notes and share them again for the squad as takeaway items.</p><h3>Takeaways</h3><p>There are several things to consider when doing retrospectives in remote teams:</p><ul><li>Preparations: using the right collaboration tools, gathering thoughts before the session, and ensuring people can be present and focused.</li><li>Guidelines: what ground rules to set to ensure focus, inclusive participation, and high engagement and how the session agenda is structured.</li><li>Problem solving mindset: Focus on problems, not the people. Go deeper into problems with RCA mode. And asking open-ended questions.</li><li>Closing: gathering points and ensuring action plans are tracked.</li></ul><p>In Scrum, there are three pillars: transparency, inspection, adaptation. I do believe the retrospective is an important tangible application of these pillars for deriving knowledge from our experiences and make progress towards creating a great product. As a Scrum Master, using these pillars personally, I am also able to make retrospectives effective for remote teams.</p><h4>Reference</h4><ul><li>Scrumguide <a href="https://scrumguides.org/">https://scrumguides.org/</a></li><li>Scrum Theories and Values <a href="https://www.scrumalliance.org/learn-about-scrum/scrum-elearning-series/scrum-theory-and-values">https://www.scrumalliance.org/learn-about-scrum/scrum-elearning-series/scrum-theory-and-values</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae2b45a6c188" width="1" height="1" alt=""><hr><p><a href="https://medium.com/julotech/how-to-incorporate-retrospective-into-your-remote-team-ae2b45a6c188">How to Incorporate Retrospective into your Remote Team</a> was originally published in <a href="https://medium.com/julotech">julotech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>