<?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 Sandeep Dey on Medium]]></title>
        <description><![CDATA[Stories by Sandeep Dey on Medium]]></description>
        <link>https://medium.com/@mailtosandeep.dey?source=rss-80093ece65a8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xCjWtpNKzSxEy4vm3fp_uw.png</url>
            <title>Stories by Sandeep Dey on Medium</title>
            <link>https://medium.com/@mailtosandeep.dey?source=rss-80093ece65a8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:15:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mailtosandeep.dey/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[The waterfall approach to agility makes no sense]]></title>
            <link>https://medium.com/@mailtosandeep.dey/the-waterfall-approach-to-agility-makes-no-sense-e9e892b79843?source=rss-80093ece65a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9e892b79843</guid>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Sandeep Dey]]></dc:creator>
            <pubDate>Sat, 22 Oct 2022 09:26:18 GMT</pubDate>
            <atom:updated>2022-10-22T09:26:18.562Z</atom:updated>
            <content:encoded><![CDATA[<p>Agile Transformation can’t be achieved using the waterfall approach. So stop trying it. Leaders need to adapt to an empirical approach to inspiring their organization.</p><p>Agility requires</p><ul><li>empowering the team,</li><li>helping them make their own decisions,</li><li>and learning from their experience as they go.</li></ul><p>They need to be Self-organized.<br> <br>Yet organizations or leaders often have these practices forced on their employees. The conclusion is a Team who doesn’t understand “why” they are on an agile journey.</p><blockquote>Agile transformation can’t be planned, there can not be a predefined roadmap to agile transformation (predictive approach). One can not use a waterfall approach for implementing an Empirical approach to deliver business value. We need to let the team learn from their own journey, validate their assumptions with short iterations, and let them organize themselves to achieve the best result.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XLibWV1fKX0drm8D" /><figcaption>Photo by <a href="https://unsplash.com/ja/@helloimnik?utm_source=medium&amp;utm_medium=referral">Hello I&#39;m Nik</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Not everyone in an organization can follow this belief, and we should not enforce the belief on everyone. When their beliefs are not supportive of the change, forcing them to change is ineffective.<br> <br>Instead, leaders should work on changing their beliefs, by helping them to understand that a predictive approach to product delivery will not help them achieve the results they want. Let the experience speak for you to transform an organization to agility.<br> <br>Remember you can’t force a belief, you can inspire them though. Leaders have a strong influence over the beliefs of an organization, and they usually have the ability to help their organizations see things in a new way. <br> <br>Believe in inspiration by examples, test your assumptions, and inspect and adapt.</p><p>Reference: <a href="https://www.scrum.org/resources/blog/freeze-pond-versus-take-hill-two-metaphors-enterprise-agile-change">https://www.scrum.org/resources/blog/freeze-pond-versus-take-hill-two-metaphors-enterprise-agile-change</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9e892b79843" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can SCRUM really help you manage complex problems]]></title>
            <link>https://medium.com/@mailtosandeep.dey/can-scrum-really-help-you-manage-complex-problems-af64ce1b7495?source=rss-80093ece65a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/af64ce1b7495</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile-project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[problem-solving]]></category>
            <dc:creator><![CDATA[Sandeep Dey]]></dc:creator>
            <pubDate>Thu, 21 Jul 2022 21:23:03 GMT</pubDate>
            <atom:updated>2022-07-21T21:23:03.678Z</atom:updated>
            <content:encoded><![CDATA[<p>It is the predictive nature of what we are building, that changes the way, teams are managed and put together. If there is a mismatch between management style and the type of complexity of the product being worked on, then we see all sorts of challenges and hurdles.</p><p>When organising a team, always ask yourself these set of questions :</p><ol><li>Would you prefer your team to be made up of cross-functional individuals or specialists?</li><li>Would you like to increase opportunities for communication and learning, or limit them?</li><li>Would you want the team to be independent and have a sense of responsibility, or have a manager assign their tasks?</li><li>Who should make the decisions? The team members or their manager?</li><li>What kind of activities would you like the manager to do?</li></ol><p>Dave Snowden, a researcher on complexity theory, created the <strong>Cynefin framework</strong> in 1999, which aims to help leaders understand that every situation is different, and requires a unique approach to decision making.</p><p>Cynefin is a sense making framework in which, the ‘<em>Data precedes framework&#39;</em> contrary to categorisation framework where the <em>framework precedes data</em>. In this kind of a framework, the patterns of the framework itself emerges from the data in a social process.</p><p>Cynefin is not a model but a framework.</p><p><strong><em>A model seems to represent a reality but a framework is a way of looking at reality. — </em>Dave Snowden</strong></p><p>The goal of Cynefin framework is to answer this question: <strong>How do you approach problems differently, depending on the domain they belong to?</strong></p><p>The framework outlines five situational domains that are defined by a cause-and-effect relationship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*iokboZlxvrfCwBwaK8ckYQ.png" /></figure><ul><li><strong>Disorder(Confused)</strong> — this is the state of not knowing what type of system or domain you are in. For most of the time we are in this space, where people don’t know if you are ordered or complex or chaotic. Depending on your own personal preference or personal history, you will tend to assess the situation. An expert will choose the complicated domain, a politician will choose complex domain where he will bring lot of experts to propose the best solution.</li></ul><p><strong>In ordered system there is a linear relationship between cause and effect. The same thing will happen repeatedly, and not by accident but by the nature of the system. Ordered systems can be further categorised into Obvious (Clear) and Complicated Domains where the constraints are either strict or under governance of a boundary.</strong></p><ul><li><strong>Obvious Domain (Clear Domain)</strong>— Everybody can see what the relationship is and nobody disputes it. One operates within the parameters of the known-known. The approach is to <strong><em>sense →categorise →respond</em></strong>, which is repetitive for anyone who can follow the instructions. Therefore, the cause-effect relationship in the obvious domain are the <strong>best practices.</strong></li><li><strong>Complicated Domain </strong>— The relationship between cause and effect is not evident other than to certain experts. You operate with known-unknowns, and the approach is to <strong><em>sense →analyze →respond</em></strong>. For such an approach, an expert needs to be consulted because for them, the complicated domain repeats itself from project to project and hence <strong>good practices</strong> are established over time. This is unlike the obvious domain where the same steps (best practices) are always applicable.</li></ul><blockquote>Major mistakes that organisations make, is to impose <strong>“best practices” </strong>into <strong>“good practices” </strong>domain.</blockquote><ul><li><strong>Complex Domain — </strong>There is no linear relation between cause and effect. We don’t know what is right unless we act and find it. Complexity is best described as the domain with the unknown-unknowns, which calls for a <strong><em>probe →sense →respond</em></strong> decision making approach.<strong><em> </em></strong>If the situation is complex, where the evidence produces conflicting hypothesis and it can’t be resolved in an acceptable time frame, then we test and search out ideas that are coherent. We run these coherent ideas in parallel, within safe to fail mode, which then reveals what is possible solution. In complex domain, everything we do, changes the scenario in hand. So a diagnostic is an intervention and in turn an intervention is the needed diagnostic.</li></ul><p>Generally what happens is the experiments merge, mutate and change. It’s okay if one experiment fails, but it’s in the combination of these experiments, that the situation begins to change so that it becomes easier to manage the problem and take decision.</p><p>In the obvious domain, you have tight constraints because you can rely on the established best practices. You know how long a certain job will take and how much it will cost. In the complicated domain, you work with governing constraints. You review certain calculations and have an agency oversee your work to make sure you do not deviate and that you analyze correctly. However, in the complex domain, you need enabling constraints that will help you understand the problem at hand so that you can tackle it.</p><ul><li><strong>Chaos Domain </strong>— In chaos, the decision making behaviour is <strong><em>act-sense-respond</em></strong> without any relationship between cause and effect as there are no constraints. It is the unknowable-unknowables.</li></ul><h3>Conclusion</h3><p>There are two approaches to “manage” a product. The approach you choose depends on the predictive nature of what is your product.</p><p>On one end of the spectrum is ordered (obvious and complicated) and on the other is unordered (complex and chaos).</p><p>With product development, most of what we build resides in the complex domain. These products are typically far too difficult to analyze upfront, often leading to “analysis paralysis.”</p><p>By breaking out a piece of the complex pie, Scrum allows you to analyze just that piece for the upcoming Sprint and make it plannable. This is done through continuous refinement, preparing just enough of the Product Backlog for Sprint Planning. In Sprint Planning, a plan for the next Sprint is created — the Sprint Backlog, which the Development Team tracks closely throughout the Sprint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/1*IOEsGk8VPC84trSw8zs-Dg.png" /></figure><p>By doing this, you establish a circular current between the complex and complicated domains. The product is complex, the plan for the Sprint is complicated. At the end of the Sprint, the Scrum Team and stakeholders reflect by reviewing the new product Increment in the context of the whole and update the complex Product Backlog accordingly.</p><p>However, the product will always remain complex, you are never completely safe from the unknown-unknowns. Strange things can and will happen along the way, possibly causing short interludes with chaos.</p><p>Reference</p><ul><li>Don, McGreal; Jocham Ralph. The Professional Product Owner: Leveraging Scrum as a Competitive Advantage</li><li>Cynefin Framework : <a href="https://thecynefin.co/about-us/about-cynefin-framework/">https://thecynefin.co/about-us/about-cynefin-framework/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af64ce1b7495" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is scrum events really a waste of time]]></title>
            <link>https://medium.com/@mailtosandeep.dey/is-scrum-events-really-a-waste-of-time-71e62f069e9e?source=rss-80093ece65a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/71e62f069e9e</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Sandeep Dey]]></dc:creator>
            <pubDate>Thu, 21 Jul 2022 21:18:55 GMT</pubDate>
            <atom:updated>2022-07-21T21:18:55.341Z</atom:updated>
            <content:encoded><![CDATA[<p>Quite often whenever we talk about introducing Scrum framework in an organisation or project, one of the common feedback we get is “okay lets try it, but you know Daily scrum is too much for everyday, lets do it every alternate day otherwise its too much of meeting”</p><p>And before you know it, they are asking to have retrospective every alternate sprint so that it will allow team to gather more points for the retrospective. And then we will hear, let’s not have review every sprint, instead lets send an email to all stakeholder with a presentation of all feature being released in the sprint and they can comment and provide feedback.</p><p>And after few months of execution, it’s not working with scrum. SCRUM framework is not for our kind of project and team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mHnUz6q1RW_Esu3G" /><figcaption>Photo by <a href="https://unsplash.com/@jasongoodman_youxventures?utm_source=medium&amp;utm_medium=referral">Jason Goodman</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Let’s take a step back and try to answer something basic.</p><p>What is the framework of scrum based on ?</p><ul><li>Scrum is based on empiricism. Empiricism asserts that knowledge comes from experience and making decision based on what is observed.</li><li>How does anyone implement the method of Empiricism ?</li></ul><p>To explain this let me illustrate you with an example a very common device “Thermostat”</p><p>Why do we need a thermostat. We need thermostat for one sole function and that is to maintain the target temperature in a room. And how does the thermostat do that. The thermostat compares current temperature with the target temperature. Every couple of minutes the thermostat calculates the delta and reacts accordingly. It doesn’t matter what is the weather forecast or more heat sources are introduced in the room or how many people are in the room. The thermostat just copes with the variability. It inspects the delta from target adjust the temperature and shows the temperature of the room and this continues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1ThtDqJ14Ot8s2RH" /><figcaption>Photo by <a href="https://unsplash.com/@mojamsanii?utm_source=medium&amp;utm_medium=referral">Moja Msanii</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The thermostat is a beautiful metaphor. It decouples you from all the unknowns and instead introduces a feedback loop. It takes a transparent reading, inspects, then adapts. The shorter this loop, the more accurate the temperature.</p><p>Now imagine the following scenarios</p><ul><li>thermostat inspects the delta temperature once in 5 hour ?</li><li>thermostat does the adaptation only every 2 inspection ?</li><li>thermostat shows the temperature only once in a day ?</li></ul><p>I know what you are thinking, you are thinking, what is the use of a device who inspects the temperature at so long duration or adapts the temperature every 2 inspection ?</p><p>Exactly the same thing is true for a project team using the framework of scrum to manage and control the risk of a complex product. The Scrum events are a formal opportunity to inspect and adapt Scrum artifacts (Product backlog, Scrum Backlog, Increment). These events are specifically designed to enable the transparency required. Failure to operate either of the event results in lost opportunities to inspect and adapt.</p><p><strong>Sprint Planning</strong></p><ul><li>Provides the transparency of requirements and the relevant value that is needed to be developed to achieve product goal.</li><li>Inspects the plan of the team based on the unknowns and add value to product goal by planning the increment that help verify the assumptions made.</li><li>Provides opportunity to adapt the plan of action taking into consideration of the value of product</li></ul><p><strong>Daily Scrum</strong></p><ul><li>Provide the transparency to the scrum team on the team progress towards scrum goal.</li><li>Inspects the impediments towards the sprint goal</li><li>Allows the adaptation to provide resolution which helps the team achieve the sprint goal.</li></ul><p><strong>Sprint Review</strong></p><ul><li>Provides the transparency of the work done and the value added by the increment</li><li>Allows the inspection of the increment and product backlog.</li><li>Opportunity to adapt the product backlog and various other artifacts based on feedback from stakeholders that will help the team attain the product goal.</li></ul><p><strong>Sprint Retrospective</strong></p><ul><li>Provide the transparency of common understanding of process, people, tool and communication in the team</li><li>Inspects the team performance to make proper adaptation to allow team achieve the product goal.</li></ul><p>All Scrum events are designed to rightly balance the team opportunity to inspect, adapt and be transparent.</p><p>I always tell to others, not believing and following the scrum events are just like trying to keep your bedroom clean by putting everything under the bed, it might work for sometime but it will come out one day. And the day it comes out we will loose more time and money to clean the dirt than we would have spent if we managed them at the right time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71e62f069e9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Did they get the agile manifesto wrong ?]]></title>
            <link>https://medium.com/design-bootcamp/did-they-get-the-agile-manifesto-wrong-94ad498be4c7?source=rss-80093ece65a8------2</link>
            <guid isPermaLink="false">https://medium.com/p/94ad498be4c7</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[agile-manifesto]]></category>
            <category><![CDATA[value-management]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Sandeep Dey]]></dc:creator>
            <pubDate>Tue, 07 Dec 2021 22:26:30 GMT</pubDate>
            <atom:updated>2021-12-20T21:21:31.487Z</atom:updated>
            <content:encoded><![CDATA[<h3>Did they get the agile manifesto right?</h3><p>Agile Manifesto, four “simple statements”,the focal point when discussing agility or agile transformation; but how often have we seen teams/leaders misinterpreting them?</p><p>And when these “simple statements” are misunderstood, have you experienced the domino affect ,which is sometime inevitable and sometime simply obvious ? Have you ever wondered why most of them failed to understand what Agile Manifesto meant ? (Shared below for reference)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3QJYL_kaS_-mwzw-" /><figcaption>Photo by <a href="https://unsplash.com/@charlfolscher?utm_source=medium&amp;utm_medium=referral">Charl Folscher</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Agile Manifesto</h4><h4>(Reference : <a href="https://agilemanifesto.org/)">https://agilemanifesto.org/)</a></h4><blockquote><em>We are uncovering better ways of developing software by doing it and helping others do it.</em></blockquote><blockquote><em>Through this work we have come to value:</em></blockquote><blockquote>Individuals and interactions over processes and tools</blockquote><blockquote>Working software over comprehensive documentation</blockquote><blockquote>Customer collaboration over contract negotiation</blockquote><blockquote>Responding to change over following a plan</blockquote><blockquote><em>That is, while there is value in the items on the right, we value the items on the left more.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SuMzBBBqkzoa8BYd" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=medium&amp;utm_medium=referral">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>One random day, a manager walks into a conference room, wearing his thinking hat, and makes an announcement “Market is becoming more and more dynamic. We have to work more efficiently, to be more productive and excel our time-to-market. Agility is the way forward. Let us begin with the manifesto which says we must choose X <strong>over</strong> Y.”</p><p>Did he say X <strong>over</strong> Y? Was that really what the manifesto indicated? And yet, trust me when I say this, if you were in that room you would find yourself nodding, just as most of the others present in that room. (….<strong>here goes the</strong> <strong>First domino)</strong></p><p><strong>Choosing</strong> one over the other, was never the intended idea. When they said we decided to choose X over Y, they never said we will not do Y. They simply said we choose to “perform” X first, but Y is also important and we will do it after we are done with X.</p><p>Often, I have been part of a conversation which said “We need to be an agile team and being agile means we only need to focus on the results, not worry about process and tools, or documentation, or follow a plan” and every time I have smiled and said “Well unfortunately, you have got it all wrong my friend”.</p><p>Every organisation, which wants to be ready for market or has a complex product, wants to make Agile transformation. They tend to miss out the real reason why they need to be Agile, they just want to be Agile which “seems” to be a secret recipe to success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gfsqu57_3m14p2dU" /><figcaption>Photo by <a href="https://unsplash.com/@mikejerskine?utm_source=medium&amp;utm_medium=referral">Mike Erskine</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When all those 17 people sat together at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah and decided to do things differently, they never thought the impact they were going to create in the world, nor had they imagined, their simple approach to complex world, could be misinterpreted so easily.</p><p>Agile Manifesto how I read it …</p><ul><li>In a complex uncertain environment, we need to focus on developing value for the product and the Manifesto gives us a powerful guidance on how to manage expectations on building it , performing some things <strong><em>before</em></strong> we perform another.</li><li>Remember, value is highly dependent on the period of time. Today, if a certain task has lower value than the others, it doesn’t mean it will remain that way. Based on time/feedback the value of the task can increase or decrease and so should our action be based on it.</li><li>We choose to perform interaction and clear exchange of information, before we follow tools or process. Interaction brings clarity of value and expectation and then we realise those expectations by utilising process and tools.</li><li>We choose to build a working software before we make a compressive document. A working software that provides an opportunity to obtain continuous feedback to build value of the product, while preparing a comprehensive document which is itself, a note of value.</li><li>We choose collaboration with customer before reviewing the contracts. Collaboration with customers help us to keep the focus on the value of the product(the one that matters),while contracts defines the liabilities and boundaries, around which the value of the product is built.</li><li>We choose to respond to changes before following a plan. Continuous value development in an uncertain environment can be managed by responding to changes, before following a plan which was devised without consideration of those uncertainties.</li></ul><blockquote>Agile is helping us to efficiently build VALUE in this complex uncertain world.</blockquote><p><strong>Let’s not blame Agile if productivity cannot be improved, or if unable to be at par with the competitive market.</strong></p><p><strong>First discover the value that you want to build, and then Agile manifesto and principle, will guide you into efficiently building them.</strong></p><p>Let me know what do you think as the anti pattern of teams to Agile ?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94ad498be4c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/did-they-get-the-agile-manifesto-wrong-94ad498be4c7">Did they get the agile manifesto wrong ?</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>