<?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 Ben Butler on Medium]]></title>
        <description><![CDATA[Stories by Ben Butler on Medium]]></description>
        <link>https://medium.com/@rigidity?source=rss-f6f70a8ca7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Ben Butler on Medium</title>
            <link>https://medium.com/@rigidity?source=rss-f6f70a8ca7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:10:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rigidity/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[Big Design Up Front is Back]]></title>
            <link>https://rigidity.medium.com/big-design-up-front-is-back-8cb2df4f4768?source=rss-f6f70a8ca7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cb2df4f4768</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ben Butler]]></dc:creator>
            <pubDate>Fri, 13 Feb 2026 05:32:19 GMT</pubDate>
            <atom:updated>2026-02-13T05:32:19.708Z</atom:updated>
            <content:encoded><![CDATA[<p>Big Requirements Up Front had its place in software development. When the cost of change during implementation is high, the act of change is concentrated where the cost is lowest, in requirements gathering.</p><p>Unfortunately, it was found that requirements, while easy to change, had a hidden cost. It poorly communicated the user and stakeholder experience, among other undesirable implications. Luckily, as technology progressed, opportunities lower the cost of change during implementation grew. Once the cost of change during implementation became less than the cost of upfront requirements gathering, requirements merged with implementation. This became known <em>as Agile</em>. A similar phenomenon appeared once the cost of replicating software moved from physical distribution to digital distribution development and operations merged, becoming <em>DevOps</em>. Testing was also merged with development with automated testing, called <em>Continuous Integration</em>. The outcome of this great combination of phases became <em>Concurrent Engineering</em>. Now complex systems can be developed entirely with verbal communication, faster than with written requirements.</p><p>Today, as AI is finding its place, it is changing the game of working iteratively. AI can implement requirements from scratch, quickly. Combine that with the fact that the usefulness of requirements holds true to this day; it is still the lowest cost to make a change. Now that users can use the product the same day as written requirements, based on the written requirements, there is another merge that is happening. Concurrent Engineering is merging with writing requirements.</p><p>Product owners can now develop, prototype, and use complex systems rapidly, and do so with only requirements. Need a change? Update the requirements document. No need for a single face-to-face conversation. No longer do users need to force awkward changes fit into an existing implementation. Instead, implement a replacement system from scratch using the new requirements document. Requirements will be version-controlled and packaged with their systems.</p><p>Imagine when the entirety of the development lifecycle began and ended with a single requirements document, most of which was also written by AI. Big Requirements Up Front is back.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cb2df4f4768" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Problem With The Daily Scrum is Itself]]></title>
            <link>https://rigidity.medium.com/it-is-time-to-end-the-daily-scrum-c5c5cc789a35?source=rss-f6f70a8ca7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5c5cc789a35</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ben Butler]]></dc:creator>
            <pubDate>Sat, 24 Jan 2026 06:07:30 GMT</pubDate>
            <atom:updated>2026-02-07T19:57:03.387Z</atom:updated>
            <content:encoded><![CDATA[<p>Why does Daily Scrum have a reputation for being a waste? Is it difficult to master? Is it misunderstood? Are people distracted?</p><p>No. The Daily Scrum itself is intrinsically the root cause of the problem. The waste is an inseparable property of the event when done as prescribed.</p><h3>Excessive Planning Undermines Productive Use of Time</h3><p>Scrum sets the narrative of the team: all communication must be about project management. Your agenda is project management. Your outcome is project management. Everything in between is project management.</p><p>Value from the Daily Scrum comes from the plan, and only the plan:</p><blockquote>“Adjusting previously planned work”</blockquote><blockquote>“Producing an actionable plan for the day”</blockquote><p>Scrum wants teams to plan and to continue planning. Everything in Scrum is about planning.</p><blockquote>“The Daily Scrum is not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s work.”</blockquote><p>But what if teams need something other than planning? What if the people doing the work need to collaborate in a way that is valuable and useful? No need, says Scrum. There are so many planning meetings that they</p><blockquote><em>“eliminate the need for other meetings.”</em></blockquote><p>This raises the question, why is there so much fixation and inflation of planning in the Daily Scrum?</p><h3>A Failed Imitation of Actual Productivity</h3><p>The Daily Scrum was inspired by a publication <strong><em>Borland Software Craftsmanship: A New Look at Process, Quality and Productivity</em></strong><em>.</em></p><p>It described an outliar of a team, one that was uniquely hyperproductive.</p><blockquote>“Analyses of the development process are ‘off the charts’ relative to most other processes we have studied.”</blockquote><blockquote>“the phenomenal productivity of this group and the factors contributing to that productivity are thought-provoking.”</blockquote><p>Something stood out out about the team. They didn’t just use a daily meeting, but long daily meetings.</p><blockquote>“<em>these daily meetings were several hours in duration; from what I heard, the project was made more of meetings than anything else.</em>”</blockquote><p>The creators of Scrum tried to imitate this by adding a daily meeting to Scrum, but with critical changes.</p><ul><li>They “fixed” a perceived duration problem in Borland&#39;s meeting by having a fixed 15-minute timebox in the Scrum meeting</li><li>They meddled with the agenda of the meeting, from being about something valuable to being about project management.</li></ul><p>At Borland, the meeting was about solutioning, brainstorming, and integrating each other&#39;s work.</p><blockquote><em>“The core architecture team met daily to hammer out C++ class interfaces, to discuss overall algorithms and approaches, and to develop the basic underlying mechanisms on which the system would be built.</em>”</blockquote><p>Despite the meeting being about solutioning and not project management, the outcome was a team where each person knew what to do next. Borland demonstrated that the information of what team members need to do next was a product of talking about design and architecture, not a product of talking about project management.</p><blockquote>“In spite of the intense meeting-oriented development culture the project built around its architectural development, class implementations were fleshed out in private.”</blockquote><p>The misunderstanding that Borland&#39;s meeting duration was a waste of time was from the perspective of project management, which views collaboration as being at the cost of man-hours. If instead teams looked like they were working, heads down, mouths shut, the hypothesis was that it would squeeze more output from the team.</p><p>Hence, the timebox is a control mechanism rooted in distrust of the team. What Scrum forgot, though, was that the team at Borland wasn’t studied because of how detrimental the hours-long daily meeting was, but because of how phenomenally productive it was.</p><blockquote>“There will always be debate about how much of the phenomenal productivity of QPW owes to its culture”</blockquote><p>By meddling with the agenda and boxing the meeting beneath 15-minutes, the Daily Scrum violates the one lesson that Borland was meant to teach us: our problem is not the duration of a meeting, but the uselessness of the meeting.</p><blockquote><em>“</em>our fear of meetings likely comes more from our memories of the ineffectiveness of our meetings, not from their frequency.<em>”</em></blockquote><h3>Suppressing Organic Collaboration</h3><p>A publication, <strong><em>The Anatomy of Social Dynamics in Escape Rooms </em></strong>(2022), analyzed 40 self-organized, self-managed teams of size 4–5 individuals. A familiar phenomenon appeared when teams were left to solve a problem with minimal to no instruction.</p><p>There was a common event of teams instantly collaborating at the start and, minutes later, ending the collaboration. Neither the timebox nor the timebox police was needed. The teams knew what they needed to discuss and they started and stopped the initial interactions without provocation.</p><blockquote>“teams tend to start the game with a high amount of group interactions. This pattern is associated with teams ‘warming up’, familiarizing themselves with the environment, and discussing together a strategy. Such a number falls abruptly after the first 5 min, reflecting division of work and individual focus.”</blockquote><p>The teams that encountered problems had a pattern of meeting again 20 minutes later. Extended time collaborating was not an indicator of non-productivity, as implied by Scrum, but an indicator that team members are actively trying to unblock themselves.</p><blockquote>“Failed teams show a greater amount of group interactions around the 20-minute mark, associated with the emergence of potential early problems.”</blockquote><p>Successful teams also reconnected to re-align and to solution.</p><blockquote>“we were able to associate the peak in group interactions in successful teams at the 30-minute mark to the presence of productive halftime get-together, where members synthesize their knowledge, discuss achievements how to proceed.”</blockquote><p>In contrast to the Daily Scrum, a prescribed and synthetic-feeling planning ritual, self-organizing teams had little issue facilitating the meeting and agenda they actually needed, and did it organically.</p><h3>Teams Pivot Away From Prescribed Planning Events</h3><p>A publication <strong><em>Investigating Daily Team Meetings in Agile Software Projects</em></strong> studied teams that followed the three project management questions common in the Daily Scrum:</p><ul><li>What did you do?</li><li>What will you do?</li><li>What impedes you?</li></ul><p>Despite the imposition of the three questions, the investigation found that teams self-corrected the event, spending less time on the three questions than more useful topics</p><blockquote>“The literature has usually described daily meetings as a place for answering the three Scrum questions. However, we found that this category only accounted for 24% of the statements at the meeting. From this point, we understand that, while the meeting was said to focus on answering the three Scrum questions, most of the meeting was spent on other types of discussion.”</blockquote><p>Teams gravitated to problem-solving, a pattern akin to the team at Borland that inspired the Daily Scrum.</p><blockquote>“Because we found that the teams spent most of the meeting on problem-focused communication, we argue that the daily meeting was mostly about making operational decisions.”</blockquote><p>Empircally the project management focus of the Daily Scrum does not serve the people doing the work. It is through discussing problems and solutions that facilitates the alignment around what work currently needs to be done.</p><blockquote>“The percentage of statements at meetings spent on the coordination of tasks was surprisingly small (7%) given that one ostensible goal of the daily meetings was to coordinate activities for the next 24 hours. This finding indicates that daily meetings in agile software projects are not the primary meetings for coordinating tasks.”</blockquote><p>In Scrum, Scrum Masters are explicitly given the accountability of keeping Scrum events within a timebox. Does this keep the event productive? It kept it interrupted.</p><blockquote>“We observed that several longer discussions were cut short by the Scrum Master when he asked the team members to hold off on long discussions. We also observed that the Scrum Master frequently asked someone to speak. We believe that these requests made the Scrum Master more of a leader than a facilitator of the meeting and that it contradicted the self-organizing nature the meeting could have had if the teammembers themselves had decided that the next person could speak.”</blockquote><p>The publication contrasted how team members prioritized higher-value communication, such as solving impediments, over lower-value communication, such as planning.</p><blockquote>“Our analysis showed that team members often discussed obstacles that they faced before they talked about what they were going to do. In contrast, the Scrum literature indicates that the reverse should occur. Apparently, the team members perceived it more important to discuss obstacles than future work”</blockquote><h3>The Unproductive Agenda</h3><p>The problems of the Daily Scrum teach a lesson: if the agenda of an event has no value, it does not matter how much of, or how on time, that agenda is fulfilled. It is because of this that the timebox is a vain attempt at facilitating productivity.</p><p>The timebox actually facilitates a culture of complicity in the continuous cycle of mediocrity that accompanies the Daily Scrum. Facilitators figure, a timebox cuts the losses of an unproductive event, therefore it is okay for the event to be unproductive. Because of the perpetuation of the unproductive Daily Scrum the next day teams aren’t stopping the bleeding; they are reopening the wound.</p><p>Facilitating a non-productive non-adaptive daily event, such as the Daily Scrum, is not a stepping stone to a productive event. The ending the Daily Scrum is the stepping stone to a productive event.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5c5cc789a35" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Scrum Master Accountability Problem]]></title>
            <link>https://rigidity.medium.com/the-scrum-master-contradict-5e2ab5e6e1d1?source=rss-f6f70a8ca7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e2ab5e6e1d1</guid>
            <dc:creator><![CDATA[Ben Butler]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 21:54:58 GMT</pubDate>
            <atom:updated>2026-01-22T01:01:50.449Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How Does a Scrum Master Actually Participate on a Team?</strong></p><p>Have you ever wondered how a Scrum Master is supposed to participate as a team member? Does a Scrum Master work side-by-side with the team, contributing directly? Or do they operate more from behind the scenes, acting as a coach? How exactly does a Scrum Master remove impediments, and what kinds of impediments are they responsible for? Are they expected to resolve technical issues themselves or to find someone else who can?</p><p>If a team is truly self-managing, what does the Scrum Master actually <em>do</em>? Are they exempt from contributing to work that the rest of the team is responsible for? Or should they step in and help in other areas when needed?</p><p>These questions aren’t merely theoretical, nor are they something each team can easily resolve on its own. They stem from a deeper issue: Scrum attempts to merge two fundamentally different — and often incompatible — leadership philosophies into a single role.</p><p>The first philosophy comes from the <strong>Hypertext Organization</strong>. In this model, leaders do not participate directly as team members. Instead, they create an environment, provide intentionally ambiguous goals, and allow teams to organize themselves to solve it. It’s similar to an escape room: the team may not fully understand the solution at first, but through collaboration and experimentation, they figure it out together. Leadership focuses on shaping the environment rather than engaging in the work. Beyond setting context and constraints, leaders have minimal direct involvement.</p><p>The second philosophy originates from the <strong>Toyota Production System</strong>. Here, leaders act as servant leaders in a very literal sense. The people doing the work understand best where inefficiencies and friction exist in the system they work with. When a team member identifies a problem, they escalate it to the leader, who then takes personal responsibility for resolving it. This may include going into a workshop and inventing new tools for the team. In this model, leadership is deeply hands-on and accountable for improving how work gets done, and doesn’t hesitate to get on the floor to participate side by side with the rest of the team.</p><p>These two leadership styles — Hypertext Organization and Toyota Production System — are not just different; they are fundamentally incompatible. One emphasizes distance and autonomy. The other emphasizes direct involvement and responsibility.</p><p>This tension helps explain why, after more than 30 years, teams still struggle to define what a Scrum Master should actually do. Scrum attempts to blend these two philosophies into a single role, creating ambiguity about whether the Scrum Master should be mostly absent or deeply involved.</p><p>Below are some of the key differences between the Hypertext Organization and the Toyota Production System.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/931/1*AzdMAUqTpd65QwBqqgP2pQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e2ab5e6e1d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Story Points Do Not Depict Risk, Uncertainty, Capacity…]]></title>
            <link>https://rigidity.medium.com/what-experts-wont-tell-you-about-story-points-0c8852d291f4?source=rss-f6f70a8ca7------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c8852d291f4</guid>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[story-points]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ben Butler]]></dc:creator>
            <pubDate>Sun, 09 Mar 2025 09:34:55 GMT</pubDate>
            <atom:updated>2026-02-01T22:17:47.210Z</atom:updated>
            <content:encoded><![CDATA[<p>Experts allege that story points are a single unit representing various characteristics:</p><ul><li>Amount of work</li><li>Complexity</li><li>Risk</li><li>Uncertainty</li><li>Capacity</li><li>Velocity</li></ul><p>If it represents so much, how is there so much miscommunication and disappointment in story points? Let’s find out.</p><h4><strong>Story Points, originally, <em>were </em>only about time</strong></h4><p>There is a myth that story points are not about time. For those who created them, they were.</p><p>Story points came from an observation by a team of developers that, on average, their work took three days relative to their estimates. Originally called “ideal days,” the team changed the term to “story points” to encrypt the communication of estimates from non-developers, in particular project managers.</p><h4>Story Points did not have a fixed conversion to days</h4><p>To calculate the number of days, Story Points were multiplied by a variable called the “load factor”. It represented the ratio of actuals to estimates. If historical data was different, the load factor was different.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*-D9YDrjtgyVLjFVDDfALyg.png" /></figure><h4><strong>Story Points do not contain uncertainty</strong></h4><p>Certainty is represented by standard deviation. Lower certainty has higher standard deviation. Higher certainty has lower standard deviation. Story points do not communicate standard deviation, and likewise do not communicate uncertainty</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LpAe754EsT2NF-v53qs6Nw.png" /></figure><h4><strong>Story Points do not contain risk</strong></h4><p>Risk is represented by probability. For the range of time it takes to complete a piece of work, communicating a lower estimate is tied to a higher risk of not completing it within the estimate. Likewise, communicating a higher estimate is tied to a lower risk of completing within the estimate. The higher the estimate, the lower the risk. Story Points do not communicate risk probability and, likewise, do not communicate risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zFXC9-n2IOlvFkMhZIPpoA.png" /></figure><h4>Story points do not contain complexity</h4><p>Complexity affects the shape of the estimate. The less aligned an estimate is with normality, the more complex it is. Story points do not communicate normality, and likewise do not communicate complexity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1QdYRXNZ4Fw861WTdsgf0A.png" /></figure><h4>Story points don’t measure capacity</h4><p>The less certain an estimate is, the larger the spread is between velocity and capacity. Story points tend to represent historical averages(velocity), not historical variability(capacity)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*ylFuKk9BRDUBwc4hD49QjQ.png" /></figure><h4>Story Points cannot align teams around an estimate</h4><p>While experts pretend that story points communicate complexity, uncertainty, risk, and capacity, it represents none of those. That makes it nearly impossible to know what a team is aligning around, if anything, when using story points.</p><h3>How To Story Point Less Badly</h3><p>For the majority of estimates, use a relative “<strong>Three-point estimation</strong>”.</p><ul><li>Points to represent how low an effort may be</li><li>Points for the likely effort</li><li>Points for the how high of an effort may be</li></ul><p>Now the team can start aligning honestly about the risk, uncertainty, capacity, velocity, or anything else story points were meant to represent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c8852d291f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dataweave vs Liquid Syntax]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Here I am going to contrast the syntax of Dataweave.</p><p class="medium-feed-link"><a href="https://rigidity.medium.com/dataweave-vs-liquid-syntax-4dd4dca29f98?source=rss-f6f70a8ca7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://rigidity.medium.com/dataweave-vs-liquid-syntax-4dd4dca29f98?source=rss-f6f70a8ca7------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dd4dca29f98</guid>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[dataweave]]></category>
            <category><![CDATA[integration]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Ben Butler]]></dc:creator>
            <pubDate>Tue, 17 Sep 2024 02:13:56 GMT</pubDate>
            <atom:updated>2024-09-17T02:13:56.659Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why Story Points Fail: Thought Experiment]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://rigidity.medium.com/why-story-points-fail-thought-experiment-9902e62372df?source=rss-f6f70a8ca7------2"><img src="https://cdn-images-1.medium.com/max/2600/1*GAJEf32lu2ya_akhwBPn9w.jpeg" width="6000"></a></p><p class="medium-feed-snippet">Scenario: A Scrum Master is facilitating a team-building event. One of the activities is to teach the team how to estimate. The Scrum&#x2026;</p><p class="medium-feed-link"><a href="https://rigidity.medium.com/why-story-points-fail-thought-experiment-9902e62372df?source=rss-f6f70a8ca7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://rigidity.medium.com/why-story-points-fail-thought-experiment-9902e62372df?source=rss-f6f70a8ca7------2</link>
            <guid isPermaLink="false">https://medium.com/p/9902e62372df</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[story-points]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Ben Butler]]></dc:creator>
            <pubDate>Wed, 14 Aug 2024 04:01:26 GMT</pubDate>
            <atom:updated>2024-08-14T04:06:04.544Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Transform Complex Data like a Boss in Salesforce]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Salesforce now has a data transformation language. This reduces the bloat and drudgery of trying to transform data in Apex and use a&#x2026;</p><p class="medium-feed-link"><a href="https://rigidity.medium.com/transform-complex-data-like-a-boss-in-salesforce-d7b0be901b53?source=rss-f6f70a8ca7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://rigidity.medium.com/transform-complex-data-like-a-boss-in-salesforce-d7b0be901b53?source=rss-f6f70a8ca7------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7b0be901b53</guid>
            <category><![CDATA[salesforce-admin]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[dataweave]]></category>
            <category><![CDATA[salesforce-apex]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Ben Butler]]></dc:creator>
            <pubDate>Thu, 11 Jul 2024 03:29:33 GMT</pubDate>
            <atom:updated>2024-07-11T03:29:33.860Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What Happened to Servant Leadership in Scrum]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://rigidity.medium.com/developers-why-scrum-servant-leadership-fails-you-6fb262b51586?source=rss-f6f70a8ca7------2"><img src="https://cdn-images-1.medium.com/max/600/1*646ZGCLsiMMzN3Aqv7rzEg.png" width="600"></a></p><p class="medium-feed-snippet">How Servant Leadership Could Be</p><p class="medium-feed-link"><a href="https://rigidity.medium.com/developers-why-scrum-servant-leadership-fails-you-6fb262b51586?source=rss-f6f70a8ca7------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://rigidity.medium.com/developers-why-scrum-servant-leadership-fails-you-6fb262b51586?source=rss-f6f70a8ca7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fb262b51586</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ben Butler]]></dc:creator>
            <pubDate>Sat, 06 Jul 2024 06:18:17 GMT</pubDate>
            <atom:updated>2024-07-09T16:10:03.349Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Creator of Scrum: “Agile is not a product”]]></title>
            <link>https://rigidity.medium.com/creator-of-scrum-agile-is-not-a-product-9a8ae869a28f?source=rss-f6f70a8ca7------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a8ae869a28f</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[scaled-agile-framework]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Ben Butler]]></dc:creator>
            <pubDate>Fri, 11 Aug 2023 21:19:59 GMT</pubDate>
            <atom:updated>2023-08-11T21:20:20.105Z</atom:updated>
            <content:encoded><![CDATA[<p>Creator of Scrum: “Agile is not a product”</p><p>This <a href="http://weblog.raganwald.com/2004/08/agile-is-attitude-not-product.html">reposts</a> a message from the creator of Scrum, Ken Schwaber.</p><blockquote>At XP/AU 2004, I kept hearing the question of how to &quot;sell Agile to the executives.&quot; I also heard a lot of discussion about &quot;crossing the chasm,&quot; the book about the evolution of products from early adoption to mainstream to late adoption. I got a chance to talk about this with several other people (whose names I will only disclose under duress), and I had the following insight: Agile is not a product. Because it isn’t a product, we shouldn’t be<br>thinking about selling it, we shouldn’t be thinking about it crossing a chasm.</blockquote><blockquote>Thinking of Agile as a product is particularly damaging because it will cause Agile to have the same failure that CMM had when it was viewed as a saleable commodity, as a product. People believed that they could market it and make money from it. People who bought it thought that they could then install it, train people on it, and then they would be better. Bob Schatz from Primavera has often pointed out that bringing Agile in is the start of an extensive change process. Deciding on Agile is a commitment to an effort, not the purchase of a solution.</blockquote><blockquote>I’ve been concerned for a while about organizations having some<br>success with Agile and deciding to go &quot;Agile&quot; whole hog. Their comments reflect a belief that Agile is something that can be implemented, solving a problem, and then they can move on. More to the truth, Agile is a commitment to collaboration, empowerment, respecting each other, courage, flexibility, facing the truth, and trust. It is about people, not products and solutions. I think people who think they can buy an &quot;Agile&quot; product are going to be in for a rude shock.</blockquote><blockquote>I believe that Agile is part of a social revolution to help people learn together to collaboratively figure out how to work and live in an increasingly complex world. Agile is an attitude, not a product. Agile is spirituality, not a religion. We don’t have to sell it as a product. We don’t have to evangelize it. We simply (and with difficulty) have to live it. People will observe us and envy our joy at work, and quake in fear and be defeated by our productivity. For the old way of doing things doesn’t cut it anymore. The Agile way is the appropriate response to our complex times.</blockquote><blockquote>So, be wary, Our culture thinks of everything as a saleable product. It is the metaphor of out consumer society. We will fall back into thinking of Agile as a product over and over, and it will confuse our thinking. Whenever this happens to your neighbor, help them out.</blockquote><ul><li>Ken Schwaber</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a8ae869a28f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum Masters Do Development Too]]></title>
            <link>https://rigidity.medium.com/scrum-masters-do-development-2c6b48081290?source=rss-f6f70a8ca7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c6b48081290</guid>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum-master]]></category>
            <dc:creator><![CDATA[Ben Butler]]></dc:creator>
            <pubDate>Fri, 27 Jan 2023 01:18:14 GMT</pubDate>
            <atom:updated>2024-07-27T01:27:55.565Z</atom:updated>
            <content:encoded><![CDATA[<p>Organizations often have a misunderstanding that Scrum Master is a full time job. It was actually designed to be a half time job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ah2pj6coLAbnFppVDggiLA.png" /><figcaption>Creator of Scrum, Jeff Sutherland — <a href="https://lnkd.in/eDx7dbYr">https://lnkd.in/eDx7dbYr</a></figcaption></figure><p>For context it was meant to start as a half time job. An indicator of an effective Scrum team is maturity. As the team matures the responsibility of a Scrum Master progressively reduces. The job could be considered transient; temporarily needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pICUOfyMrTBJ_YZq1d2lKw.png" /><figcaption>Creator of Scrum, Ken Schwaber — <a href="https://www.scruminc.com/first-scrum-project-manager/">https://www.scruminc.com/first-scrum-project-manager/</a></figcaption></figure><p>An effective Scrum team mostly runs on automatic, being able to resolve its own impediments, facilitate its own events, and the business understands the expectations of Scrum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_64SYluNP9yAlXLVGTD7AA.png" /><figcaption>Creator of Agile, Bob Martin — <a href="https://youtu.be/hG4LH6P8Syk">https://youtu.be/hG4LH6P8Syk</a></figcaption></figure><p>The person accountable as a Scrum Master continues to work full time, just not on Scrum. As the amount of time a Scrum Master focuses on Scrum decreases the amount of work a Scrum Master focuses on development increases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wixZcK6oMclshWkpNVz3vw.png" /><figcaption>Creator of Scrum, Jeff Sutherland — <a href="https://qr.ae/proDao">https://qr.ae/proDao</a></figcaption></figure><p>At some point a Scrum Master essentially becomes a developer. Scrum Masters will be seen spending 80% of the the time doing development, maybe more as the Scrum team matures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yFed8RymuHChwzpuvq8Mqw.png" /><figcaption>Creaor of Scrum, Jeff Sutherland — <a href="https://www.scruminc.com/first-scrum-project-manager/">https://www.scruminc.com/first-scrum-project-manager/</a></figcaption></figure><p>Scrum Masters are not absolved of the responsibility of working on sprint items. As Scrum says, “The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.” This is a common misunderstanding with Scrum Masters who have a project management background which traditionally avoided contributing to development. In Scrum nobody on the team is prohibited from contributing to development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmmYJIw02BzCFj3wWZIcdQ.png" /><figcaption>Creator of Agile, Bob Martin — <a href="https://youtu.be/hG4LH6P8Syk">https://youtu.be/hG4LH6P8Syk</a></figcaption></figure><p>That is why Scrum Master should do development. It is not just an indicator of a team successfully using Scrum to deliver value, but is also an indicator of being a great Scrum Master.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xU9nG2-9VFMvEXW6K7tZXA.png" /><figcaption>Creator of Scrum, Jeff Sutherland — <a href="https://lnkd.in/eDx7dbYr">https://lnkd.in/eDx7dbYr</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c6b48081290" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>