<?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 Rushan Sameera on Medium]]></title>
        <description><![CDATA[Stories by Rushan Sameera on Medium]]></description>
        <link>https://medium.com/@rushansameera?source=rss-1491f7e3bbee------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8Zkrq5DNOsnamcrpOeflOA.png</url>
            <title>Stories by Rushan Sameera on Medium</title>
            <link>https://medium.com/@rushansameera?source=rss-1491f7e3bbee------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:40:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rushansameera/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[6 Common Myths About Scrum]]></title>
            <link>https://medium.com/6-common-myths-about-scrum/6-common-myths-about-scrum-c43fddb9ef4e?source=rss-1491f7e3bbee------2</link>
            <guid isPermaLink="false">https://medium.com/p/c43fddb9ef4e</guid>
            <category><![CDATA[process]]></category>
            <dc:creator><![CDATA[Rushan Sameera]]></dc:creator>
            <pubDate>Sun, 20 Sep 2020 15:20:31 GMT</pubDate>
            <atom:updated>2020-09-20T15:20:31.552Z</atom:updated>
            <content:encoded><![CDATA[<p>Many organizations follow scrum believing that it is a wand to make things done. But sometime later many of them realize that scrum is not delivering what it is expected to do. They feel bad about its magical power. All success stories about scrum become fairy tales.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*1ZdhYp9_68Il3_jyLZKjQQ.png" /></figure><p>Let’s see why scrum is not as <em>magical </em>as it is expected to be.</p><p>Scrum is just a framework. It has its own roles, artifacts and events. Most importantly it’s very simple and adaptive. Any team can easily migrate to scrum. But… it is not easy to get its benefits merely by following the framework. Because there are some myths that have been established in scrum and it takes away from the intended outcome.</p><h3><strong>6 Common Myths…</strong></h3><h4>1. Scrum can be used as a tool to improve the existing process.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/1*MM5DOXt6B6gcgIirDe__bA.png" /></figure><p>The simplicity of scrum can be misunderstood as it is possible to get part of the scrum and try it along with another process. This makes both processes vulnerable and probably does not deliver anything better than before because scrum provides a room to evolve itself while it does not guarantee an improvement of some other process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*mAKb7Rzmjc9WALcfDgUNug.png" /></figure><p>It is recommended that instead of making changes to the scrum framework to adhere to some other process, making changes to the prevailing process until it fully adheres to the scrum.</p><h4>2. Rebrand the team as scrum roles and go.</h4><p>Renaming the existing people and groups according to the scrum roles does not make scrum compliance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*eGuvmzhpYq8FkigxHuR3mQ.png" /></figure><p>Scrum roles are not there for the sake of differentiating their designations. They come with a relevant mindset. Changing the Project manager to PO and Team Lead to Scrum master and the rest of the group to scrum team won’t make any sense if they are not changing their mindset, actions and responsibilities along with it.</p><h4>3. PO has the authority to rule and manage the team and scrum master.</h4><p>This is one of the things that scrum wants to fundamentally eliminate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/551/1*WdctIh8ekxaKK8KNAwFkhA.png" /></figure><p>Scrum promotes teamwork, team responsibility, and self-management of the team. PO is there to show the broad picture and guide the team to achieve it. According to scrum, it can achieve only through self-organized teams. If there is an issue belonging to the development, solutions should come from the team and it is a sign that the team is matured with the process and they are moving with it. Mostly other inputs may not be healthy to the team.</p><h4>4. Accuracy of estimations and story points are very important. Use diagrams and detailed plans to estimate correctly.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/567/1*hVL-C5vmN6ZkqQur7Hn8tw.png" /></figure><p>In scrum, estimations are important and useful as long as they know that it is not accurate. In software development, estimations highly depend on the skills and experience of the team. When it comes to agile its accuracy is impacted since it has to accommodate new requirements. Estimations and story points are just indicators. Spending more time on design diagrams and detailed plans which can be useless with upcoming requirements and might be a waste of valuable time. Scrum recommends planning just enough to start the development of a feature. Unlike the waterfall method, scrum always welcomes changes at any stage of the development.</p><h4>5. All stories in the sprint must be completed at the end of the sprint.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*lK3meWmdqxXP4yPQzpsVfw.png" /></figure><p>A sprint is based on some estimated values which can’t guarantee the accuracy. Uncertainty of features and situations are always there. It is normal to have in-completed stories at the end of the sprint.</p><h4>6. Scrum helps to complete a project with all requirements in a given time period under the budget.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*4U1RMmQPbT96SPdloI588w.png" /></figure><p>Simply scrum can’t do that. But scrum builds an environment that helps to deliver the most important features according to the specification even with frequent and late changes of requirements. In other words, scrum can deliver software with the most important and fully completed features in a given time for an allocated budget.</p><h4>Conclusion</h4><p>Scrum is just a simple framework. It is easy to learn but difficult to master. Understand the basic principles and capabilities of Scrum to avoid misunderstandings and misinterpretations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c43fddb9ef4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/6-common-myths-about-scrum/6-common-myths-about-scrum-c43fddb9ef4e">6 Common Myths About Scrum</a> was originally published in <a href="https://medium.com/6-common-myths-about-scrum">6 common myths about scrum</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>