<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>scrum master tips on Kuldeep Pisda</title><link>https://kdpisda.in/tag/scrum-master-tips/</link><description>Recent content in scrum master tips on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 04 Dec 2025 12:48:04 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/scrum-master-tips/index.xml" rel="self" type="application/rss+xml"/><item><title>10 Sprint Planning Best Practices That Will Save Your Startup's Sanity</title><link>https://kdpisda.in/10-sprint-planning-best-practices-that-will-save-your-startups-sanity/</link><pubDate>Thu, 04 Dec 2025 12:48:04 +0530</pubDate><guid>https://kdpisda.in/10-sprint-planning-best-practices-that-will-save-your-startups-sanity/</guid><description>&lt;p&gt;I&amp;rsquo;ve been in that Monday morning meeting. You know the one. Coffee in hand, staring down a two hour calendar invite for &amp;ldquo;Sprint Planning.&amp;rdquo; You brace yourself for a rambling discussion, scope creep happening in real time, and a team that leaves feeling more confused than committed. It&amp;rsquo;s the kind of meeting that truly could have been an email, or at least a much more focused conversation.&lt;/p&gt;
&lt;p&gt;I once led a team where our planning sessions became so bloated we called them &amp;lsquo;sprint meandering&amp;rsquo;. We would consistently overcommit, wildly underestimate complexity, and then spend the next two weeks firefighting our way to the finish line. It felt like we were always one step behind. It was exhausting, demoralizing, and completely unsustainable. That painful experience forced me to get serious about finding a better way, moving from chaotic guesswork to a structured, predictable process.&lt;/p&gt;</description></item></channel></rss>