<?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 Kusha Singh on Medium]]></title>
        <description><![CDATA[Stories by Kusha Singh on Medium]]></description>
        <link>https://medium.com/@kusha.singh6?source=rss-de0a213f8f42------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*OUyqhTUcPSGlb-jf</url>
            <title>Stories by Kusha Singh on Medium</title>
            <link>https://medium.com/@kusha.singh6?source=rss-de0a213f8f42------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:28:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kusha.singh6/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[Ways of Working in Agile: Turning Every Sprint into a System Upgrade]]></title>
            <link>https://medium.com/@kusha.singh6/ways-of-working-in-agile-turning-every-sprint-into-a-system-upgrade-d014ca810a9a?source=rss-de0a213f8f42------2</link>
            <guid isPermaLink="false">https://medium.com/p/d014ca810a9a</guid>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[agile-ways-of-working]]></category>
            <dc:creator><![CDATA[Kusha Singh]]></dc:creator>
            <pubDate>Fri, 17 Apr 2026 07:49:34 GMT</pubDate>
            <atom:updated>2026-04-17T07:49:34.095Z</atom:updated>
            <content:encoded><![CDATA[<p>Agile promises continuous improvement.<br>But in many teams, improvement becomes occasional — dependent on retros that vary in quality, energy, or participation.</p><p>What if improvement itself became structured, lightweight, and embedded into every sprint?</p><p>That’s where a <strong>Ways of Working (WoW) session</strong> becomes powerful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5eRAl3sisfF8ZVYhkFLZw.png" /></figure><h3>What Is a Ways of Working Session?</h3><p>A Ways of Working session is a short (generally 30-min), focused discussion held every sprint where the team reflects specifically on:</p><p><em>“How are we working together — and what small change would make us more effective next sprint?”</em></p><p>Unlike a traditional retrospective (which can be broad and emotional), WoW sessions are:</p><ul><li>Practical</li><li>Forward-looking</li><li>Improvement-oriented</li><li>Action-driven</li></ul><h3>Why Teams Need It (Even If They Already Do Retros)</h3><p>Many retros end with:</p><ul><li>5 improvement ideas</li><li>2 unclear owners</li><li>0 measurable follow-up</li></ul><p>When teams become mature, the action points from retros reduce too.</p><p>WoW shifts the emphasis from discussion to execution.</p><p>Instead of:</p><blockquote><em>“We need better refinement.”</em></blockquote><p>You define:</p><blockquote><em>“Starting next sprint, all stories must have test scenarios before estimation.”</em></blockquote><p>It converts insights into working agreements.</p><h3>Types of Improvements WoW Surfaces</h3><p>Over time, WoW sessions typically surface improvements in five areas:</p><h4>1. Estimation Discipline</h4><h4>2. Flow Optimization</h4><h4>3. Dependency Management</h4><h4>4. Quality Engineering</h4><blockquote><strong>and most important of all,</strong></blockquote><h4>5. Communication &amp; Culture</h4><h3>The Long-Term Impact</h3><p>When done every sprint, WoW creates:</p><h4>Predictable Delivery:</h4><p>In the short term, WoW improves small behaviours.<br>In the long term, it stabilizes the system.</p><p>When teams regularly adjust:</p><ul><li>Story slicing</li><li>Definition of Ready</li><li>WIP limits</li><li>Dependency handling</li><li>Estimation guardrails</li></ul><p>You begin to see:</p><ul><li>Reduced spill over trends</li><li>Lower estimation variance</li><li>More stable velocity bands</li><li>Fewer last-minute escalations</li></ul><p>Predictability isn’t achieved through pressure. It’s achieved through iterative system tuning.</p><p>WoW is that tuning mechanism.</p><h4>Root Cause Awareness:</h4><p>Because patterns are documented and revisited.</p><h4>Continuous System Evolution:</h4><p>Because the team’s process improves in small increments.</p><h4>Higher Team Maturity:</h4><p>Because improvement becomes shared ownership — not Scrum Master-driven.</p><h3>Common Pitfalls</h3><ol><li>Turning it into a complaint session</li><li>Trying to fix everything at once</li><li>Not tracking whether changes helped</li><li>Skipping it when the sprint is “busy”</li><li>If improvement is optional, it disappears under pressure.</li></ol><h3>Final Thought</h3><p>Agile is not just about delivering features faster.</p><p>It’s about improving the system that delivers those features.</p><p>A consistent Ways of Working session ensures that:</p><p><em>Every sprint doesn’t just ship value.<br>It upgrades the team itself.</em></p><p>In my next article, I’ll break down the structure of an effective Ways of Working session and how teams can run it consistently every sprint. Stay tuned. If you have any questions, leave them in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d014ca810a9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spice Up Your Sprint Retro (Yes, It Can Be Fun!)]]></title>
            <link>https://medium.com/@kusha.singh6/spice-up-your-sprint-retro-yes-it-can-be-fun-6f2f9efc20a8?source=rss-de0a213f8f42------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f2f9efc20a8</guid>
            <dc:creator><![CDATA[Kusha Singh]]></dc:creator>
            <pubDate>Mon, 06 Oct 2025 05:10:29 GMT</pubDate>
            <atom:updated>2025-10-06T05:10:29.915Z</atom:updated>
            <content:encoded><![CDATA[<p>In Agile teams, few ceremonies are as powerful — yet often underrated — as the <strong>sprint retrospective</strong>. At its core, a retro is about <strong>reflection and improvement</strong>: the team comes together to talk openly about what went well, what didn’t, and how to make the next sprint better. Done well, it fuels learning, strengthens collaboration, and helps the team continuously improve.</p><p>But retros can easily become stale if they feel repetitive or mechanical. The key is to keep them <strong>valuable, engaging, and fresh</strong>. Let’s explore why retros matter, and some creative ways to keep your team looking forward to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqgJu-8o3kqvurYAybyqzQ.png" /></figure><h3>Why Retrospectives Matter</h3><ol><li><strong>Continuous Improvement: </strong>Retros give teams a structured space to pause, reflect, and commit to change. It’s how small adjustments become big leaps in performance over time.</li><li><strong>Psychological Safety: </strong>A regular, trusted forum for sharing feedback helps teams build openness and trust. When people know their voices are heard, collaboration improves.</li><li><strong>Celebrating Success: </strong>Retros aren’t just about problems — they’re also about acknowledging wins and giving teammates the kudos they deserve.</li><li><strong>Team Alignment: </strong>By discussing processes, blockers, and opportunities together, retros keep everyone aligned and moving in the same direction.</li></ol><h3>Creative Themes for Retros</h3><p>To avoid retros feeling like “just another meeting,” many teams add a <strong>theme</strong>. Themes make the session fun, spark fresh perspectives, and create a shared team vibe. Here are some popular ones that I like to use with different teams:</p><ul><li><strong>Sailboat</strong>: <em>Wind </em>= what pushed us forward, <em>Anchor </em>= what held us back, <em>Rocks </em>= risks ahead, <em>Land </em>= our goal.</li><li><strong>Weather Forecast</strong>: <em>Sunny </em>= positives, <em>Cloudy </em>= uncertainties, <em>Stormy </em>= problems, <em>Rainbow </em>= hopes.</li><li><strong>Food</strong>: <em>Tasty Bites </em>= what we loved, <em>Too Spicy</em> = pain points, <em>Missing Ingredient</em> = what we lacked, <em>Recipe Ideas</em> = improvements, <em>Chef’s Specials</em> = shout-outs.</li><li><strong>Video Game</strong>: <em>Power-ups</em> = what boosted us, <em>Boss fights </em>= challenges, <em>Extra lives </em>= what we want more of, <em>Next level</em> = future improvements.</li></ul><p>A theme doesn’t change the essence of the retro — but it <strong>shifts the energy</strong> and keeps the team engaged.</p><h3>Ways to Run a Retro</h3><p>Different formats work for different teams. I like to mix it up to keep things interesting:</p><ol><li><strong>Classic “Start, Stop, Continue”</strong><br> Simple and effective: what should we start doing, stop doing, and continue doing?</li><li><strong>Mad, Sad, Glad</strong><br> Focuses on emotions: what made us mad, sad, or glad during the sprint? Great for surfacing morale issues.</li><li><strong>4Ls (Liked, Learned, Lacked, Longed for)</strong><br> Encourages reflection on knowledge and process as well as delivery.</li><li><strong>Silent Retro (with sticky notes or online board)</strong><br> Everyone writes feedback quietly first, then discussions happen after grouping themes. Helpful for quieter teams.</li><li><strong>Gamified Retros</strong><br> Add trivia questions, riddles, or quick icebreakers to lighten the mood and keep energy high.</li></ol><h3>Making Retros Stick</h3><p>The most important part of a retro is not the discussion — it’s the <strong>follow-through</strong>. To make retros impactful:</p><ul><li>Capture <strong>clear action items</strong> with owners.</li><li>Limit the number (1–2 is better than a long list).</li><li>Revisit actions at the start of the next retro to ensure accountability.</li></ul><h3>Final Thoughts</h3><p>Sprint retrospectives are the engine of continuous improvement. When run well, they go beyond process check-ins — they build stronger teams, celebrate wins, and surface opportunities for growth. By introducing creative themes and varying formats, you can keep retros engaging and meaningful instead of routine.</p><p>Next time you run a retro, try mixing in a new theme, end with a fun riddle or quiz, and most importantly — commit to one small change. Over time, those small steps will transform how your team works.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f2f9efc20a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Fixed Power BI Dashboard Refresh After a Laptop Change]]></title>
            <link>https://medium.com/@kusha.singh6/how-i-fixed-power-bi-dashboard-refresh-after-a-laptop-change-9c095dd694d0?source=rss-de0a213f8f42------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c095dd694d0</guid>
            <category><![CDATA[microsoft-power-bi]]></category>
            <dc:creator><![CDATA[Kusha Singh]]></dc:creator>
            <pubDate>Wed, 01 Oct 2025 06:03:11 GMT</pubDate>
            <atom:updated>2025-10-01T06:03:11.501Z</atom:updated>
            <content:encoded><![CDATA[<p>When I recently switched to a new laptop, I expected my work to carry on smoothly. But the next morning, my Power BI dashboard failed to refresh, and I was greeted with this dreaded error message:</p><blockquote>‘Report has failed to refresh. The last refresh attempt failed because of an internal service error. DMTS_OAuthTokenRefreshFailedError… Device used during authentication is disabled.’</blockquote><p>At first, I thought it was a one-off glitch. But after retrying, the error persisted. That’s when I discovered — this is a <strong>common issue Power BI users face after changing laptops or when IT disables an old device in Azure Active Directory</strong>. The problem boils down to cached credentials and authentication tokens that no longer work once your old device is decommissioned.</p><p>Here’s what worked for me (and should work if you’re facing something similar):</p><p><strong>Update Credentials in Power BI Service</strong></p><ul><li>Go to <em>Power BI Service → Settings → Datasets → Data Source Credentials</em>.</li><li>Re-enter authentication details (OAuth, organizational account, or API keys depending on your source).</li></ul><p><strong>Refresh and Test</strong></p><ul><li>Run a manual refresh to confirm the fix.</li><li>Once successful, re-enable <strong>scheduled refresh</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*y4nL91Lep6i-DNJxEGZYsA.png" /><figcaption>Power BI service — Settings for reports</figcaption></figure><h3>💡 Key Takeaways</h3><ul><li><strong>New laptops ≠ seamless transition</strong> for Power BI. Always double-check your gateway and credentials.</li><li>Laptop changes often break Power BI refreshes because of <strong>gateway dependencies and expired Azure AD tokens</strong>.</li><li>To avoid this dependency, consider moving from a <strong>personal gateway</strong> to a <strong>shared/enterprise gateway</strong> so refreshes don’t rely on a single machine.</li></ul><p>Closing thought: If your Power BI dashboards stop refreshing after a laptop change, don’t panic. It’s usually a credentials or gateway issue — and with a quick reset, you’ll have your reports running smoothly again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c095dd694d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Behind the Bugs: Power BI Dashboard for Quality Insights]]></title>
            <link>https://medium.com/@kusha.singh6/behind-the-bugs-power-bi-dashboard-for-quality-insights-aa312781b54f?source=rss-de0a213f8f42------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa312781b54f</guid>
            <dc:creator><![CDATA[Kusha Singh]]></dc:creator>
            <pubDate>Mon, 23 Jun 2025 20:35:39 GMT</pubDate>
            <atom:updated>2025-06-23T20:35:39.745Z</atom:updated>
            <content:encoded><![CDATA[<p>Delivering high-quality software is no longer just the responsibility of QA teams — it’s a shared goal across development, product, and platform engineering. But how do you measure quality effectively and act on it in real time?</p><p>To bridge this gap, we developed a <strong>Defects Analysis Dashboard</strong> in <strong>Power BI</strong> that gives our teams and leaders visibility into key defect metrics like <strong>total defects, leakage, turnaround time, lead time </strong>and <strong>cycle time trends</strong>. This dashboard empowers us to identify problem areas, improve test coverage, and ultimately drive better product outcomes.</p><h3><strong>Purpose</strong></h3><p>In any software delivery lifecycle, defects are inevitable — but what really matters is <strong>how quickly you detect, respond to, and learn from them</strong>. Before this dashboard, defect tracking was fragmented across spreadsheets, ad hoc queries and siloed systems, leaving key quality questions unanswered:</p><ul><li>Are we catching defects early enough?</li><li>Which modules are most error-prone?</li><li>How quickly are defects being resolved?</li><li>Is our quality improving over time?</li></ul><p>We needed a centralized, interactive, and up-to-date solution that could surface insights in real time, and Power BI was the perfect tool for that.</p><h3>A Look Inside the Defects Analysis Dashboard</h3><p>Here’s a glimpse of the Power BI dashboard in action:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T17oA0rskrF4b8yJssiMGA.png" /><figcaption>Power BI Dashboard</figcaption></figure><h3><strong>Key Visuals &amp; Metrics</strong></h3><p>Here’s a breakdown of the core visuals in the dashboard and how they’re used:</p><p><strong>Total Defects Overview</strong></p><p>A dynamic card and bar chart shows the total number of defects over selected period of time, broken down by status (active/design/in review).<br><em>Benefit</em>: Quickly understand the overall defect volume and severity distribution.</p><p><strong>Defect Leakage Rate</strong></p><p>Visualizes how many defects were found in production vs. pre-production (e.g., UAT or QA). <em>Benefit</em>: Helps identify test coverage gaps and improve pre-release testing strategies.</p><p><strong>Turnaround Time</strong></p><p>Measures the time taken from defect logging to closure. Represented as a dynamic card grouped by environment.<br><em>Benefit</em>: Highlights responsiveness of teams and SLA adherence.</p><p><strong>Lead Time and Cycle Time Trend</strong></p><p>A line chart shows how long it takes to detect, start work on, and resolve defects on monthly basis.<br><em>Benefit</em>: Tracks process efficiency and helps spot delivery bottlenecks.</p><p><strong>Interactive Filters</strong></p><p>Filters for projects, dates, priority, environment (QA, UAT, Prod), etc.<br><em>Benefit</em>: Allows users to drill down and find root causes quickly.</p><h3><strong>Benefits We’ve Seen</strong></h3><p>We’re in the early stages of adoption, but the dashboard is positioned to bring meaningful improvements to our quality management processes:</p><ul><li>Transparency: Leadership now has clear KPIs on quality without relying on manual reporting.</li><li>Faster triage: Engineers and QA teams can focus on high-impact defects thanks to clear visibility.</li><li>Better release planning: Product managers can make data-informed decisions about go/no-go readiness.</li><li>Continuous improvement: Historical trend data helps us run more meaningful retrospectives.</li></ul><h3><strong>Lessons Learned</strong></h3><p>One key learning from building this dashboard is the importance of <strong>aligning on consistent defect categorization early</strong>, particularly around fields like severity and root cause — this ensures clean, reliable reporting. It’s also essential to <strong>automate data refreshes</strong> using scheduled Power BI updates from Azure DevOps, so the dashboard always reflects the latest information. Lastly, make sure to <strong>engage both QA and product stakeholders</strong> in defining the most meaningful metrics — they’ll not only provide valuable insights but also become strong advocates for using the dashboard across teams.</p><h3><strong>Closing Thoughts</strong></h3><p><em>Quality is a journey, not a destination</em>.</p><p>With our Defects Analysis Dashboard in Power BI, we now have a single pane of glass to track, analyse, and improve our quality efforts. If you’re building something similar or want to explore how dashboards can support your quality goals, feel free to connect!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa312781b54f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Power BI + Azure DevOps: Release Management Dashboard in Action]]></title>
            <link>https://medium.com/@kusha.singh6/power-bi-azure-devops-release-management-dashboard-in-action-52bc9a4feea6?source=rss-de0a213f8f42------2</link>
            <guid isPermaLink="false">https://medium.com/p/52bc9a4feea6</guid>
            <category><![CDATA[release-management]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[power-bi]]></category>
            <category><![CDATA[delivery-management]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <dc:creator><![CDATA[Kusha Singh]]></dc:creator>
            <pubDate>Thu, 12 Jun 2025 16:47:47 GMT</pubDate>
            <atom:updated>2025-06-12T16:47:47.770Z</atom:updated>
            <content:encoded><![CDATA[<p>In fast-moving tech environments, visibility into software releases is critical — but often overlooked. To bridge this gap, I developed a <strong>Release Management Dashboard</strong> using <strong>Power BI</strong> and <strong>Azure DevOps</strong> data.</p><h3>Purpose</h3><p>This dashboard is designed to give <strong>teams</strong>, <strong>platform leads</strong> and <strong>senior stakeholders</strong> a real-time view of release activity across various teams within the platform. It helps answer key questions like:</p><ul><li>How many releases have been deployed over time?</li><li>How many were successful vs. failed?</li><li>What exactly was released, and when?</li></ul><h3>Key Features</h3><ul><li><strong>Live Data Integration</strong> with Azure DevOps</li><li><strong>Trend Analysis</strong> of release frequency over days, weeks, months</li><li><strong>Success/Failure Breakdown</strong> to identify problem areas</li><li><strong>Detailed Drilldowns</strong> showing release content, owners, and environments</li><li>Clean, <strong>interactive visuals</strong> built in Power BI with filters for team, date range, environment, and more</li></ul><h3>Why It Matters</h3><p>Most organizations track releases — few visualize them well. This dashboard turns Azure DevOps data into <strong>actionable insights</strong>, improving coordination between engineering, QA, and platform teams.</p><p>It also promotes a <strong>culture of transparency</strong>, making release patterns visible to leadership without digging into DevOps pipelines.</p><h3>A Look Inside the Release Management Dashboard</h3><p>Here’s a glimpse of the Power BI dashboard in action:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*noFR57jJMMvHkygy-3FRsA.png" /><figcaption>Power BI Dashboard</figcaption></figure><p>This dashboard is broken into <strong>four key sections</strong>:</p><ol><li><strong>Release Trend Over Time</strong><br>A line chart showing the number of releases over a period of time e.g. year, month<br>It helps track the pace of delivery and spot gaps or surges in release activity.</li><li><strong>Success vs Failure Rates</strong><br>A stacked bar chart visualizing the ratio of successful to failed releases.<br>This helps teams quickly identify reliability trends over time.</li><li><strong>What Was Released?</strong><br>A decomposition tree listing:</li></ol><ul><li>Total no. of releases</li><li>Release year</li><li>Release month</li><li>Release ID</li><li>Deployed items e.g. User Stories, Improvements, Bugs</li></ul><p><strong>4. Detailed table view</strong></p><p>Table listing released items (along with title, type) within each release.</p><p><strong>5. Filters and Slicers</strong><br> Interactive filters by:</p><ul><li>Project</li><li>Item Type e.g. user story, bug etc.</li><li>Year</li></ul><p>Cross-filtering/highlighting on each visual</p><p><strong><em>Real Impact</em></strong><em>: Senior leaders now get a real-time view of our release activity. Platform teams use it to monitor trends, identify bottlenecks, and drive more informed discussions during planning.</em></p><h3>Takeaway</h3><p>If your team uses Azure DevOps, combining it with Power BI can unlock meaningful insights into your release process. This dashboard has already sparked conversations and driven improvements in our own delivery pipeline.</p><p>Curious how we built it? Reach out, or follow for more info.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52bc9a4feea6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>