<?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 Aria Omidvar on Medium]]></title>
        <description><![CDATA[Stories by Aria Omidvar on Medium]]></description>
        <link>https://medium.com/@omidvar.aria?source=rss-c98461c29fda------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PgxIoOn7FbNLbfnznKq_OQ.jpeg</url>
            <title>Stories by Aria Omidvar on Medium</title>
            <link>https://medium.com/@omidvar.aria?source=rss-c98461c29fda------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:25:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@omidvar.aria/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[Anti-SAFe: A List]]></title>
            <link>https://medium.com/@omidvar.aria/anti-safe-a-list-058d0fca9f7c?source=rss-c98461c29fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/058d0fca9f7c</guid>
            <category><![CDATA[scaled-agile-framework]]></category>
            <category><![CDATA[safe]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Aria Omidvar]]></dc:creator>
            <pubDate>Thu, 08 Jan 2026 10:25:35 GMT</pubDate>
            <atom:updated>2026-02-05T17:40:49.781Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2tWLNC5_k0DHqYJiqnHvBw.png" /><figcaption>Image source: <a href="https://www.britannica.com/science/What-Causes-Mirages"><strong>Mirage — optical illusion | Britannica</strong></a></figcaption></figure><p><a href="https://ronjeffries.com/xprog/articles/safe-good-but-not-good-enough/"><strong>SAFe — Good But Not Good Enough</strong></a>, 2014, Ron Jeffries</p><p><a href="https://thecynefin.co/safe-the-infantilism-of-management/"><strong>SAFe: the infantilism of management</strong></a>, 2014, <a href="https://www.linkedin.com/in/dave-snowden-2a93b/">Dave Snowden</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FzNvmjPzdqKc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DzNvmjPzdqKc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FzNvmjPzdqKc%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1db8b2a9b23d8c2784a8045adf6696b9/href">https://medium.com/media/1db8b2a9b23d8c2784a8045adf6696b9/href</a></iframe><p><a href="https://jeffgothelf.com/blog/safe-is-not-agile/"><strong>SAFe is Not Agile</strong></a>, 2021, <a href="https://www.linkedin.com/in/gothelf/">Jeff Gothelf</a></p><p><a href="https://scaledagiledevops.com/"><strong>Scaled Agile DevOps Maturity Framework — Enterprise DevOps transformation without the risk of culture change!</strong></a>, <a href="https://www.linkedin.com/in/bryan-finster/">Bryan Finster</a> et al.</p><p><a href="https://riseandfallofdevops.com/5-minute-devops-safe-isnt-6108f95bef23"><strong>SAFe Isn’t</strong></a>, 2022, <a href="https://www.linkedin.com/in/bryan-finster/">Bryan Finster</a></p><p><a href="https://www.infoq.com/articles/replace-process-dogma-engineering/"><strong>Agile Rehab: Replacing Process Dogma with Engineering to Achieve True Agility</strong></a>, 2023, <a href="https://www.linkedin.com/in/bryan-finster/">Bryan Finster</a></p><p><a href="https://safedelusion.com/"><strong>SAFe Delusion</strong></a>, 2025</p><p><a href="https://bdfinst.medium.com/5-minute-devops-why-safe-fails-to-deliver-cd-at-scale-1308f6a63591"><strong>Why SAFe Fails to Deliver CD at Scale</strong></a>, 2025, <a href="https://www.linkedin.com/in/bryan-finster/">Bryan Finster</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FX4-Y9oUlpkE%3Fstart%3D27%26feature%3Doembed%26start%3D27&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DX4-Y9oUlpkE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FX4-Y9oUlpkE%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e4de2ba7f1ed9d215daa943dc0ad7d04/href">https://medium.com/media/e4de2ba7f1ed9d215daa943dc0ad7d04/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fv7lDLEjyxW0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dv7lDLEjyxW0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fv7lDLEjyxW0%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/159833927f3cb319d38c3dbc2463f79a/href">https://medium.com/media/159833927f3cb319d38c3dbc2463f79a/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FX5NZwQZ6we4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DX5NZwQZ6we4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FX5NZwQZ6we4%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/da9bf23cbb888a94a9b4010079ce7c3f/href">https://medium.com/media/da9bf23cbb888a94a9b4010079ce7c3f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=058d0fca9f7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hitchhiker’s Guide to Hexiverse — Scrum Patterns]]></title>
            <link>https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-patterns-15062fc30656?source=rss-c98461c29fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/15062fc30656</guid>
            <category><![CDATA[christopher-alexander]]></category>
            <category><![CDATA[scrum-patterns]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Aria Omidvar]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 14:34:48 GMT</pubDate>
            <atom:updated>2026-02-12T12:57:03.829Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Hitchhiker’s Guide to Hexiverse — Scrum Patterns</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LaHDoe91YjVM39dehznxHQ.png" /><figcaption><strong>Scrum Patterns</strong> from <strong>Hexiverse</strong></figcaption></figure><p>In this article, I suggest a Hexi set for <a href="https://sites.google.com/a/scrumplop.org/published-patterns/home"><strong>Scrum Patterns</strong></a><strong> </strong>and expand on each Hexi. The corresponding Hexi set can be found <a href="https://miro.com/app/board/uXjVKv84GGU=/?moveToWidget=3458764607400651695&amp;cot=14"><strong>here</strong></a>.</p><h3>From Christopher Alexander to Scrum Patterns</h3><p><a href="https://en.wikipedia.org/wiki/Christopher_Alexander">Christopher Alexander</a>, the architect who might as well be called a philosopher, first influenced the pioneers of computer science through his book <a href="https://en.wikipedia.org/wiki/Notes_on_the_Synthesis_of_Form">Notes on the Synthesis of Form (1964)</a>.</p><p>Later, his book <a href="https://en.wikipedia.org/wiki/A_Pattern_Language">A Pattern Language (1977)</a> influenced the pioneers of object-oriented programming and Agile Software Development in several ways, including how we build software and even how we approach teamwork and organizations.</p><p>One of the earliest adaptations of his <em>patterns</em> concept for teamwork and organizations was James Coplien’s paper in 1995 [1], then Mike Beedle’s paper in 1997 [2], both of which paved the way for the first formalization of Scrum as a <em>pattern language</em> in a paper from 1998 [3].</p><p>What we recognize today as Scrum Patterns is the result of more than two decades of work by a passionate <a href="https://www.scrumplop.org/">community</a> and James Coplien as the Product Owner.</p><h3>This Hexi Set</h3><p>This guide integrates the Scrum Patterns into the Hexiverse. It is important to mention that I did not extract any of these patterns and merely mapped them one-to-one to Hexis. As for the description of each Hexi, I am quoting the original text directly as well.</p><p>My only contribution to this Hexi set is organizing the Hexis in a meaningful way and connecting them to other Hexis from other Hexi sets to my best knowledge.</p><p>I deeply hope that this Hexi set introduces Scrum Patterns to a wider range of Scrum practitioners and Agile enthusiasts. I encourage readers, learners, and users to follow the links to the original material for deeper insights into each Hexi/Pattern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Nzp7mmMiHiFhztCt4r3vg.png" /></figure><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/scrum-team"><strong>Scrum Team</strong></a></h4><blockquote>Form a team that has all the necessary competencies: the people who can make and deliver the product (a Development Team), a Product Owner who guides product direction, and a Scrum Master who facilitates learning.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/product-owner">Product Owner</a></h4><blockquote>Get a Product Owner to order the Product Backlog and take responsibility for the vision of the product, and for the value that emanates from the delivery of that vision.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team">Development Team</a></h4><blockquote>Building on Stable Teams, create a Development Team that rallies around a product inspired by the Product Owner’s Vision, to deliver successive increments of that product through the Value Stream to its end users.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/scrummaster">Scrum Master</a></h4><blockquote>Introduce a ScrumMaster that guides and leads the Product Owner, Development Team, and broader organization in understanding the Scrum framework, its principles, and values.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/cross-functional-team">Cross-Functional Team</a></h4><blockquote>Each Scrum Team should include all talent necessary to deliver Done functionality.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/self-organizing-team">Self-Organizing Team</a></h4><blockquote>The Development Team organizes itself to get its work Done. The Development Team is solely responsible for <strong>how</strong> it does its work.</blockquote><p>Related patterns: <strong>Self-Organizing Teams</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>], <strong>Self-Organizing Team</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/autonomous-team">Autonomous Team</a></h4><blockquote>The Scrum Team makes its <strong>decisions</strong> free from external control, and while it is an open system attentive to external considerations, the team charts its own <strong>direction</strong> according to its pursuit of value without undue external influence.</blockquote><p>Related patterns: <strong>Autonomy</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/small-teams">Small Teams</a></h4><blockquote>Use Small Teams of people working on serialized work rather than striving for false parallelism.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/stable-teams">Stable Teams</a></h4><blockquote>Keep teams stable and avoid shuffling people around between teams.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/collocated-team">Collocated Team</a></h4><blockquote>Collocate the team members, ideally in a room of their own, within talking distance.</blockquote><p>See also: <a href="https://guntherverheyen.com/2024/09/24/announcing-the-availability-of-the-4th-edition-of-scrum-a-pocket-guide/">Shared (visual) workspace</a></p><p>Related patterns: <strong>Team Space </strong>[<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/oyatsu-jinja">Snack Shrine</a></h4><blockquote>Create a Snack Shrine near the team area, with some candies, snacks, and drinks (coffee or tea).</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M1BDFO5YhPc7lp-MHzC-7w.png" /></figure><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint"><strong>Sprint</strong></a></h4><blockquote>Organize development around recurring, frequent, fixed-length, time-boxed intervals.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint/follow-the-moon">Follow the Moon</a></h4><blockquote>Define Sprints with beginning and ending boundaries falling on the new moon and full moon.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint-planning">Sprint Planning</a></h4><blockquote>A Sprint should produce a <strong>Potentially Shippable Product Increment</strong>. Yet simply pulling PBIs off the top of the Product Backlog does not necessarily result in work that creates the Greatest Value or work that fits into the Sprint’s time box to produce the product increment.</blockquote><blockquote>At the beginning of every Sprint the Scrum Team (or all the teams that together deliver a jointly developed product increment) meets to plan how it will <strong>create value</strong> during the Sprint. The team agrees to a <strong>Sprint Goal</strong> and creates a plan for <strong>what</strong> the Development Team will develop and <strong>how</strong> the team will develop it.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint-goal">Sprint Goal</a></h4><blockquote>The objective of a Sprint is to deliver value to the stakeholders. However, simply following a list of Sprint Backlog Items does not necessarily result in the creation of the greatest value possible.</blockquote><blockquote>The Scrum Team commits to a short statement of the <strong>value</strong> it intends to create during the Sprint. This becomes the <strong>focus</strong> of all work in the Sprint.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint-backlog">Sprint Backlog</a></h4><blockquote>In order to <strong>manage</strong> its progress during the Sprint, the Development Team needs to have a clear understanding of <strong>work</strong> remaining to achieve the Sprint Goal.</blockquote><blockquote>Create a <strong>work plan</strong> for everything that the team must accomplish to meet the Sprint Goal. The team usually subdivides this work into Sprint Backlog Items (SBIs).</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint-backlog/sprint-backlog-item">Sprint Backlog Item</a></h4><blockquote>A Product Backlog Item (PBI) does not define <strong>how</strong> to arrive at a solution or implementation, or how to deploy the solution.</blockquote><blockquote>Break down Product Backlog Items into <strong>work items</strong> and assemble them into a <strong>plan</strong> called a Sprint Backlog. Each work item is a Sprint Backlog Item (SBI).</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint-backlog/developer-ordered-work-plan">Developer-Ordered Work Plan</a></h4><blockquote>Let the Development Team members decide the best ordering of tasks to reach their forecast of delivering the Sprint Goal and full Sprint Backlog.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/production-episode">Production Episode</a></h4><blockquote>Team members do the best work, and most efficiently complete planned work, when they can work together <strong>without distractions</strong>.</blockquote><blockquote>Compartmentalize all market-facing <strong>product realization work</strong> in a time-boxed interval, with participation limited to the Development Team.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint/daily-scrum">Daily Scrum</a></h4><blockquote>The team makes progress in a Sprint by finishing Sprint Backlog Items, but given the complexity of the work, the characteristics, size, and quantity of tasks <strong>change</strong> frequently — sometimes minute by minute.</blockquote><blockquote>Have a short event every day to replan the Sprint, to <strong>optimize the chances</strong> first of meeting the <strong>Sprint Goal</strong> and second of completing all <strong>Sprint Backlog Items</strong>. Strictly time-box the meeting to keep focus on the daily plan and to avoid robbing time from development. Focus on the next day’s work but keep the remainder of the Sprint in mind.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint/daily-scrum/scrummaster-incognito">Scrum Master Incognito</a></h4><blockquote>At the Daily Scrum, the Development Team members address the Scrum Master instead of discussing issues with each other.</blockquote><blockquote>As the owner of the Scrum process, it is the Scrum Master’s job to ensure the team takes ownership of the Daily Scrum.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint-backlog/dependencies-first">Dependencies First</a></h4><blockquote>If critical dependencies remain halfway through the Sprint and the team is still discovering more, you risk failing the Sprint.</blockquote><blockquote>Make sure that all known dependencies are under control by mid-Sprint.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/illegitimus-non-interruptus">Illegitimus Non Interruptus</a></h4><blockquote><strong>Changing priorities</strong> or problems in the field often interrupt the work of Scrum Teams during a Sprint. Sales and marketing demands, combined with management interference, can cause chronic dysfunction in a team, repeated failure of Sprints, failure to meet release dates, and even company failure.</blockquote><blockquote>Explicitly <strong>allot time for interrupts</strong> and do not allow more work than fits within the allotment. If work exceeds the allotment, abort the Sprint.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/emergency-procedure">Stop the Line</a></h4><blockquote>Problems arise in the middle of a Sprint due to emergent requirements or unanticipated changes. By mid-Sprint, it may be obvious that the Development Team cannot complete the Sprint Backlog successfully. The team is high on the Sprint Burndown Chart and sees that it cannot achieve the Sprint Goal at the current rate of getting things done.</blockquote><blockquote>When high on the burndown, try a technique used routinely by pilots. When bad things happen, execute the Emergency Procedure designed specifically for the problem.</blockquote><blockquote>Scrum Emergency Procedure: (do only as much as necessary)<br>1- Change the way the team does the work. Do something different.<br>2- Get <strong>help</strong>, usually by offloading backlog to someone else.<br>3- Reduce <strong>scope</strong>.<br>4- Abort the Sprint and <strong>replan</strong>.<br>5- <strong>Inform</strong> management how the emergency affects release dates.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/definition-of-done">Definition of Done</a></h4><blockquote>Each team member may have a different <strong>understanding of “work completed”</strong> for the team’s deliverables.</blockquote><blockquote>All work done by the Scrum Team must adhere to criteria, <strong>agreed upon</strong> by the <strong>Development Team</strong> and the <strong>Product Owner</strong>, which collectively form the Definition of Done. If the work does not conform to Definition of Done, the work is then by definition not Done, and the team may not deliver the corresponding Product Backlog Item (PBI).</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/regular-product-increment">Product Increment</a></h4><blockquote>Every Sprint, the Scrum Team strives to deliver a Product Increment that is <strong>Done</strong>, <strong>usable</strong>, and potentially <strong>releasable</strong>. The team uses the Product Increment to <strong>validate</strong> if it has increased the <strong>value</strong> of the product, and to understand how the product actually <strong>performs</strong> in the market.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint-review">Sprint Review</a></h4><blockquote>End the Production Episode with an event to <strong>assess</strong> the status of the product and to <strong>learn</strong> about end-user <strong>needs</strong>, <strong>risks</strong>, <strong>opportunities</strong>, <strong>problems</strong>, and likely completion dates to ensure product is moving in the direction of Greatest Value.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ZgozLFeIYtLOXAiQfEyaQ.png" /></figure><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/notes-on-velocity">Velocity</a></h4><blockquote>A Development Team’s velocity is a (usually unitless) number that indicates the team’s capacity to complete potentially shippable work in a given Sprint. Velocity is intended to be a measure of the team’s efficiency: how much work the team completes per unit time, where Sprints are the units of time (e.g., two weeks).</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/information-radiator/sprint-burndown-chart">Sprint Burndown Chart</a></h4><blockquote>It is important that team members have <strong>timely</strong> access to information about their progress towards meeting their forecast, so that they can <strong>pivot</strong> immediately if necessary.</blockquote><blockquote>Create a graph that plots estimated work remaining in the Sprint against the amount of time remaining in the time box. Plot the <strong>Sprint’s progress</strong> as a trend line on the graph so that its slope gives an immediately obvious and intuitive indicator as to <strong>likelihood</strong> of the Development Team meeting its target.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/estimation-points/yesterday-s-weather">Yesterday’s Weather</a></h4><blockquote>In most cases, the number of Estimation Points completed in the last Sprint is a reliable predictor of how many Estimation Points of work the team will complete in the next Sprint.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/fixed-work">Fixed Work</a></h4><blockquote>Set aside periodic time-boxes for <strong>non-estimable work</strong> (such as the work to understand requirements as the team moves PBIs to Ready), outside the Production Episode budget, and complete as much of each kind of such work as time-boxing allows.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/vacation-pbi">Vacation PBI</a></h4><blockquote>Track planned Development Team member absences as Product Backlog Items (PBIs).</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/running-average-velocity">Running Average Velocity</a></h4><blockquote>Use a running average of the most recent Sprints to calculate the velocity of the next Sprint.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/estimation-points/updated-velocity">Updated Velocity</a></h4><blockquote>Recognize an updated velocity only if the team sustains a new level for <strong>three Sprints in a row</strong>.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/specialized-velocities">Specialized Velocities</a></h4><blockquote>Each specialized team estimates and develops items within its realm of specialization.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/aggregate-velocity">Aggregate Velocity</a></h4><blockquote>Have all teams estimate all PBIs together, to extend the scope of consensus to all Development Team members. Derive the Estimation Points baseline and scale from all teams together. The aggregate velocity is simply the sum of all teams’ velocities together.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NzqxZwzGB7dqTxkisYAWDA.png" /></figure><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/value-and-roi">Value &amp; ROI</a></h4><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/vision">Product Vision</a></h4><blockquote>The Vision is a description of how the product supports a <strong>desired future</strong> toward which an envisioned future Product Organization advances.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/release-plan/product-roadmap">Product Roadmap</a></h4><blockquote>The Product Owner is confident about a general product <strong>direction</strong> and might even be confident of the <strong>destination</strong>. Even so, there are <strong>many paths</strong> to reach a given market position, level of profitability, market penetration, and other product objectives.</blockquote><blockquote>The Roadmap presents options in two dimensions. The Product Roadmap outlines <strong>alternatives</strong>, and the opportunity to collectively make <strong>decisions</strong> at well-defined decision points: do we go right or left here? The Product Backlog is today’s best guess of the path we will take through the Product Roadmap. The Roadmap may evolve to reflect changes to the business strategy.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog">Product Backlog</a></h4><blockquote>For each product, create a single <strong>ordered list</strong> called the Product Backlog — a list of Product Increment contributions called Product Backlog Items (PBIs), arranged in their expected <strong>delivery order</strong>.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/product-backlog-item">Product Backlog Item</a></h4><blockquote>Create distinct specifications of changes and additions to the product, called Product Backlog Items (PBIs), that together form the Product Backlog.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/refined-product-backlog">Refined Product Backlog</a></h4><blockquote>The Scrum Team should meet frequently to properly order the Product Backlog and to break down the most imminent large PBIs into smaller ones.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/granularity-gradient">Granularity Gradient</a></h4><blockquote>Break down the earliest PBIs into Small Items of half a Sprint or less of work for an individual (about 10 percent of the total Sprint work) each. The team should break down later PBIs so that their size is proportional to their depth in the Product Backlog. A PBI that lies more than four or five Sprints in the future may be arbitrarily large and may be little more than a whim of what the feature should do.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/small-items">Small Items</a></h4><blockquote>Break work down into Small Items that are steps to deliver the big ideas, so the Development Team can master its understanding of each small item individually.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/fixed-date-pbi">Fixed-Date PBI</a></h4><blockquote>The Product Owner moves each Product Backlog Item blocked by a hard schedule dependency (such as deliveries from third-party partners) to a backlog position that corresponds to a date when it becomes ready for a Sprint (e.g., the supplier’s scheduled delivery date). The Product Owner marks the PBI with the expected resolution date for the dependency.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/enabling-specification">Enabling Specification</a></h4><blockquote>An Enabling Specification is a specification <strong>rich enough</strong> that someone reasonably skilled in the discipline can implement a solution without substantial subsequent clarification with people outside the Scrum Team.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/roi-ordered-backlog">ROI-Ordered Backlog</a></h4><blockquote>The Product Owner orders PBIs in a way that generates the largest long-term ROI.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/high-value-first">High Value First</a></h4><blockquote>Build the high value, most essential Product Backlog Items first.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/greatest-value">Greatest Value</a></h4><blockquote>The team finds itself not being able to rise above local optimizations and short-term thinking. When teams assess overall value by adding the value from relatively independent contributing efforts, they can too easily to optimize the parts at the expense of the whole.</blockquote><blockquote>Create the greatest overall value at the greatest scale and scope within the enterprise’s span of influence, and continuously strive to <strong>expand</strong> that scope. Manage work locally with a view to the Whole, using effective engagement and feedback, to eliminate local optimizations.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/set-based-design">Set-Based Design</a></h4><blockquote>There may be many possible solutions to a complex problem. It is often impossible to predict which is best.</blockquote><blockquote>Develop many options <strong>in parallel</strong>, fixing only the critical constraints up front.</blockquote><p>Related patterns: <strong>Set-based Development</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>], <strong>Set-based Development</strong> [Lean Software Development], <strong>Redundancy</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">XP</a>]</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/release-plan">Release Plan</a></h4><blockquote>The Product Owner needs to be able to communicate to stakeholders when the next release is coming out and which Product Backlog Items the release contains.</blockquote><blockquote>Create an initial Product Backlog together with the Development Teams that communicates by which <strong>sequence of Increments</strong> you plan to realize the Vision and maximize value.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/release-plan/release-range">Release Range</a></h4><blockquote>Stakeholders (e.g., managers or customers) tend to treat any single delivery date as definitive, and they tend to treat definitive feature lists as commitments.</blockquote><blockquote>Make pessimistic and optimistic estimates for release dates based on Product Backlog Item estimates and a range of historic team velocities.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/change-for-free">Change for Free</a></h4><blockquote>Fix the price and the scope, and make a contractual agreement to commit to the top 80 percent of the PBIs, ordered according to their value to the client. The vendor might exceed that 80 percent target if it can complete the work within the contracted cost. Offer clients the option of exchanging an emergent requirement for any existing PBI of equal (or lower) value to them, as long as the development cost of the new item is no more than the cost of the original.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/money-for-nothing">Money For Nothing</a></h4><blockquote>Stop development when the <strong>cost</strong> of continuing exceeds the <strong>benefit</strong> that the client enterprise will receive from the development.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-wake">Product Wake</a></h4><blockquote>At the end of its life, give a product a <strong>decent burial</strong>.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/estimation-points/pigs-estimate">Pigs Estimate</a></h4><blockquote>Let the people who are committed to do the actual work do the estimation.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/estimation-points">Estimation Points</a></h4><blockquote>Use <strong>unitless numbers</strong> for effort estimation. Use <strong>relative estimation</strong>, starting with the Estimation Points for some simple work item that everyone understands well as a baseline for the rest.</blockquote><p>See also:</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/product-backlog/definition-of-ready">Definition of Ready</a></h4><blockquote>Each Product Backlog Item must meet at least the following criteria before the Development Team can take it as a candidate for the work on the Sprint Backlog during Sprint Planning:<br>1- The work is immediately actionable by the team.<br>2- The planned deliverable has value.<br>3- The Product Owner and the Development Team have discussed it.<br>4- The Development Team has estimated it.<br>5- It is testable, and the Product Owner has specified tests for it.<br>6- The Scrum Team has sized the pieces appropriately (see Small Items).</blockquote><blockquote>A Product Backlog is “Ready” if it has enough Product Backlog Items at its top, meeting these criteria, to fill a Sprint.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sXiAHDiXZ-hnZUEUUpcVcA.png" /></figure><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/kaizen-and-kaikaku">Kaizen &amp; Kaikaku</a></h4><p>Improvement…<br><strong>Kaizen</strong>: continuous, incremental, gradual<br><strong>Kaikaku</strong>: radical, extreme, often initiated by the management</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/kaizen-pulse">Kaizen Pulse</a></h4><blockquote>Alternate periods of controlled velocity with spikes of process improvement.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint/sprint-retrospective">Sprint Retrospective</a></h4><blockquote>Over time, without explicit attention, processes and discipline tend to decay. Making isolated process changes without due focus feeds entropy, but without periodic change the team misses opportunities to increase value.</blockquote><blockquote>At the end of each Sprint, have an event where the Scrum Team can assess how it performed its work during the Sprint.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/retrospective-pattern-language/scrumming-the-scrum">Scrumming the Scrum</a></h4><blockquote>Identify the single most important <strong>impediment</strong> at the Sprint Retrospective and remove it before the end of the next Sprint.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/pop-the-happy-bubble">Pop the Happy Bubble</a></h4><blockquote>Teams can get into a state where they are <strong>satisfied</strong> with the improvements they have made. However, this allows <strong>dysfunctions</strong> to persist. It is like a bubble of happiness surrounds them and insulates them from <strong>unpleasant but true</strong> information.</blockquote><blockquote>Jolt the team into awareness of its situation: force the team to confront its happy-bubble-ness by <strong>showing</strong> them important deficiencies. Then, together with the team, plan actions to improve. Create a <strong>culture</strong> in the team of <strong>relentless, continuous self-examination and improvement</strong>.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/unlinked-patterns/involve-the-managers">Involve the Managers</a></h4><blockquote>Sustain a <strong>management function</strong> that can act from a position of power to initiate, and take responsibility for, <strong>radical changes</strong> in the organization, and deal with <strong>impediments</strong> that may be too weighty for the ScrumMaster or Product Owner in the Scrum Team.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-dhrQ4qdFSS0lz55o54Ig.png" /></figure><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/a-scaling-sequence">A Scaling Sequence</a></h4><blockquote>Scaling legitimately occurs under just one circumstance: when the <strong>product grows organically</strong> to the point where the demand for new features outstrips even a high-performing Scrum Team’s <strong>capacity to deliver</strong> in a timely fashion.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/product-owner-team">Product Owner Team</a></h4><blockquote>The Product Owner has more to do than a single person can handle well.</blockquote><blockquote>Create a Product Owner Team, led by the Chief Product Owner, whose members together carry out product ownership.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/mitosis">Mitosis</a></h4><blockquote>One should grow a Scrum Team in an incremental, piecemeal fashion, but eventually the team just becomes too large to remain efficient.</blockquote><blockquote>Differentiate a single large Development Team into two small teams after it gradually grows to the point of inefficiency — about seven people in the old team.</blockquote><p>Related patterns: <strong>Grow &amp; Split</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/conway-s-law">Conway’s Law</a></h4><blockquote>Organize the workforce into Small Teams of more or less five people, partitioned according to the most important concerns for the creation of value by the enterprise. Supplement this structure with a small number of <strong>cross-cutting structures</strong> for secondary but important concerns, never forgetting that these structures are only optimizations in what is otherwise <strong>an open environment of unconstrained cooperation</strong>.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/metascrum">Meta Scrum</a></h4><blockquote>Create a MetaScrum as a forum where the entire enterprise can align behind the Product Owners’ backlogs at every level of Scrum in the organization.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/organizational-sprint-pulse">Organizational Sprint Pulse</a></h4><blockquote>The Scrum Team and the rest of the organization are out-of-step, causing either <strong>waiting time</strong> or Sprint <strong>interruptions</strong>.</blockquote><blockquote><strong>Synchronize</strong> the rhythms of the Scrum Teams’ Sprints and the rhythms of the surrounding organization.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/value-areas">Value Areas</a></h4><blockquote>When the business cannot serve a growing number of customer segments with separate products, but rather needs to develop a single product that serves all markets, in many cases a single Scrum Team cannot quickly develop the necessary deep understanding of all those customer segments.</blockquote><blockquote>Scale your product along Value Areas. A Value Area is a <strong>valuable product part</strong> that addresses the needs of a <strong>customer segment</strong> but which has no useful value or identity apart from its inclusion in the product.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/value-stream-fork">Value Stream Fork</a></h4><blockquote>Grow a product’s functionality — along with its supporting development organization — to the point where at least two of the product’s Value Streams have distinct delivery cadences, rates of feature change, market ergonomics, or business contexts that suggest that there should be more than one product identity. <strong>Split</strong> the product into multiple products corresponding to the dominant Value Streams. Each product will have its own Product Backlog and Product Owner.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/scrum-of-scrums">Scrum of Scrums</a></h4><blockquote>When <strong>multiple teams</strong> work independently of each other they tend to focus myopically on their own concerns and lose sight of any <strong>common goals</strong>.</blockquote><blockquote>Give the right and the responsibility to collaborate on delivering common goals identified by the Product Owner to the Development Teams themselves. Permit the teams to figure out the best way to coordinate their efforts.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XpBRdso5gQbsVHZHl6wK4g.png" /></figure><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/the-mist">The Mist</a></h4><blockquote>An individual, or a collective mind of several individuals, together create an <strong>environment</strong> where the necessary pre-work and evaluation can establish the primordial soup from which <strong>Scrum teams emerge</strong>.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/rhythms-patterns-of-time">Rhythms</a></h4><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/product-pride">Product Pride</a></h4><blockquote>Team members need to know <strong>their work matters</strong> and have a say in <strong>how</strong> it’s done.</blockquote><blockquote>Create a climate that enables <strong>Autonomy</strong>, <strong>Mastery</strong>, and <strong>Purpose</strong>.</blockquote><p>Related patterns: <strong>RAMPS</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-modern-synthesis-b1e3b61ba3c1">Modern Synthesis</a>]</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/fertile-soil">Fertile Soil</a></h4><blockquote>It is the moment-by-moment <strong>interactions</strong> of people working together on a product that build and sustain product organizations. Interaction qualities both reflect and define organization qualities.</blockquote><blockquote>Demonstrate the values of <strong>Commitment</strong>, <strong>Focus</strong>, <strong>Openness</strong>, <strong>Respect</strong> and <strong>Courage</strong> in your day-to-day behaviors and interactions.</blockquote><p>Related patterns: <strong>Scrum Values</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>], <strong>Golden Rules</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/norms-of-conduct">Norms of Conduct</a></h4><blockquote>The Scrum Team agrees to norms of conduct (expectations about acceptable behaviors) to enable it to grow into high performance.</blockquote><p>Related patterns: <strong>Working Agreement</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/remove-the-shade">Remove the Shade</a></h4><blockquote>You notice that team members always postpone decisions and important work until one especially skilled Development Team member is present, but as the Scrum Master you want all team members to perform optimally according to their abilities.</blockquote><blockquote>Remove the Hero from the team so the rest of the team can grow, like flowers getting light after a big tree falls in the storm.</blockquote><p>Related patterns: <strong>Fluid Mobs</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/team-sprint">Team Sprint</a></h4><blockquote>Development Team members come up with ideas for PBIs that never make it into the Sprint as new higher-value items are constantly pouring in from the other stakeholders. The team gets frustrated as its PBIs won’t ever make it into a Sprint.</blockquote><blockquote>The Product Owner organizes a Team Sprint every fifth or tenth Sprint or as best suits the organization. In this Sprint, the Development Team can choose whatever PBIs it wants to include in the Sprint.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-team/swarming--one-piece-continuous-flow">Swarming</a></h4><blockquote>Focus maximum team effort on one item in the Product Backlog and complete all known work as soon as possible. Whoever takes this item is Captain of the team. Everyone must help the Captain if they can and no one can interrupt the Captain. As soon as the Captain is Done, whoever takes responsibility for the next backlog item is Captain.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/good-housekeeping">Clean House</a></h4><blockquote>Where there’s a mess you lose time and energy finding where and what to start on.</blockquote><blockquote>Maintain a completely clean <strong>product and work environment</strong> continuously, or clean at the end of <strong>each day</strong>.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/whack-the-mole">Whack the Mole</a></h4><blockquote>There is always a tension between advancing product <strong>functionality</strong> and raising product <strong>quality</strong>.</blockquote><blockquote><strong>Immediately resolve</strong> product problems, big and small, as they arise.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/responsive-deployment">Responsive Deployment</a></h4><blockquote>Working in rhythm is good, but so is smoothing out flow and reducing the inventory of items waiting for the team to deliver them to the market.</blockquote><blockquote><strong>Release</strong> selected Product Backlog Items to the market as they become <strong>Done</strong> and as the Product Owner approves them in the course of the Production Episode.</blockquote><p>Related patterns: CI/CD</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/release-plan/release-staging-layers">Release Staging Layers</a></h4><blockquote>Stakeholder feedback is crucial to agile development and to ongoing improvement and growth of the product, but it may be <strong>costly</strong> and <strong>risky</strong> to ship every release to the whole market.</blockquote><blockquote>Identify a <strong>gradient of markets</strong> for releases, ranging from beta testers to full public release, and release every Sprint to some constituency suitable to the product increment maturity and to market conditions.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/information-radiator">Information Radiator</a></h4><blockquote>Collaboratively maintain physical artifacts that keep information visible to all stakeholders.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/visible-status">Visible Status</a></h4><blockquote>Create a status overview that demands action when outside acceptable tolerance.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/information-radiator/scrum-board">Scrum Board</a></h4><blockquote>Create a Scrum Board that represents the Sprint Backlog and its evolution during the Sprint. The Development Team maintains it, controls it, and owns it. Post it where all Development Team members have easy access to it as an Information Radiator.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/small-red-phone">Small Red Phone</a></h4><blockquote>Issue a red cellular phone, with its own number, to each critical staff member, to be used to reach these key players only in critical situations. Likely targets for such a phone include the Product Owner and the ScrumMaster.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/leading-team">Leading Team</a></h4><blockquote>A <strong>new business opportunity</strong> arises and you need significantly more development capacity, more than you can develop incrementally.</blockquote><blockquote>Add an <strong>existing high-performing Development Team</strong> to work on the business opportunity to learn fast about its development risks and business potential.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/birds-of-a-feather">Birds of a Feather</a></h4><blockquote>Core competencies are a crucial element of enterprise value that cuts across development organization boundaries.</blockquote><blockquote>Create ad-hoc “birds of a feather” groups for each area of significant enterprise core <strong>competency</strong> or developer <strong>interest</strong>, where interested parties can trade notes on technologies, domain knowledge, and processes that are key to <strong>enterprise advancement</strong>.</blockquote><p>See also: <a href="https://en.wikipedia.org/wiki/Community_of_practice"><strong>Community of Practice</strong></a>, <a href="https://en.wikipedia.org/wiki/Community_of_interest"><strong>Community of Interest</strong></a></p><p>Related patterns: <strong>Guild</strong> [Spotify Model]</p><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/the-spirit-of-the-game">The Spirit of the Game</a></h4><blockquote>Written rules might give concrete guidance for how to work together, but spirit is part of <strong>culture</strong> that guides <strong>interactions</strong> and may be discerned only when ignored or violated.3</blockquote><blockquote>When using Scrum, the product community must focus on explicitly creating a <strong>culture</strong> in the organization where people know and follow the <strong>spirit of Scrum</strong>.</blockquote><h4><a href="https://sites.google.com/a/scrumplop.org/published-patterns/product-organization-pattern-language/development-partnership">Development Partnership</a></h4><blockquote>Create a partnership between clients and vendors that <strong>breaks down walls</strong> between the organizations. The initial agreement makes the rules of engagement clear, and these rules should include consideration for collocated development, equitable risk sharing, and ongoing adjustment to the definition of the deliverable, with a vision of a continued long-term engagement after the initial business goals are met.</blockquote><h3>Your Feedback</h3><p>If you have comments or suggestions, please do not hesitate to express them here in the comments or message me directly on <a href="https://www.linkedin.com/in/aria-omidvar/">LinkedIn</a>. I welcome all kinds of commentary, ideas, and chats on the topic.</p><p>[1] <a href="https://web.archive.org/web/20220718073804/https://3aec1b23-a-eadc3f87-s-sites.googlegroups.com/a/gertrudandcope.com/info/Publications/Patterns/Process/PLoPD1/aboutDoc/ProcessPatterns.pdf?attachauth=ANoY7cp5BGkx8haKt6Wu6k5LGJFc_lFNTqxGQ9vFEhi2RwG8XqNlQ6GYV7mZkKTB64FZAleXlLyVeXKhBIKoO6I2F-cqQJ5bTdvTWnNtVcLK5-20UUnkSmYvx0FyvuCDvNHl3156rYhqP0fcHNfP9dcjDi1kCNYxX_juL7q3AEv-AB1h8ficoNoMxx7ZEC8FqZuzoFkE-_QhOXcqQgNLguUUrD-8znhe3_g2FdXBQ9CF-hnKPwlm0kvkhYxd_pNBEsngZeB4zjx-gvIO50_x5ex_RlGdMmg9uJY_s0lwQeWuEr495A7KDLE%3D&amp;attredirects=0"><strong>A generative development-process pattern language</strong></a>, 1995, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a><br>[2] <a href="https://hillside.net/plop/plop97/Proceedings/beedle.pdf"><strong>cOOherentBPR — A pattern language to build agile organizations</strong></a>, 1997, <a href="https://en.wikipedia.org/wiki/Mike_Beedle">Mike Beedle</a><br>[3] <a href="https://www.researchgate.net/publication/2464945_SCRUM_An_extension_pattern_language_for_hyperproductive_software_development"><strong>SCRUM: An extension pattern language for hyperproductive software development</strong></a>, 1998, <a href="https://en.wikipedia.org/wiki/Mike_Beedle">Mike Beedle</a>, <a href="https://www.linkedin.com/in/martine-devos-771879/">Martine Devos</a>, Yonat Sharon, <a href="https://en.wikipedia.org/wiki/Ken_Schwaber">Ken Schwaber</a>, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a></p><h3>Scrum Patterns Literature</h3><ul><li><a href="https://www.researchgate.net/publication/2464945_SCRUM_An_extension_pattern_language_for_hyperproductive_software_development"><strong>SCRUM: An extension pattern language for hyperproductive software development</strong></a>, 1998, <a href="https://en.wikipedia.org/wiki/Mike_Beedle">Mike Beedle</a>, <a href="https://www.linkedin.com/in/martine-devos-771879/">Martine Devos</a>, Yonat Sharon, <a href="https://en.wikipedia.org/wiki/Ken_Schwaber">Ken Schwaber</a>, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a></li><li><a href="https://www.scruminc.com/wp-content/uploads/2014/05/teamsthatfinishearlyacceleratefaster.pdf"><strong>Teams that Finish Early Accelerate Faster: A Pattern Language for High Performing Scrum Teams</strong></a>, 2014, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a>, <a href="https://www.linkedin.com/in/neil-harrison-900879/">Neil Harrison</a>, <a href="https://www.linkedin.com/in/joel-riddle/">Joel Riddle</a></li><li><a href="https://pragprog.com/titles/jcscrum/a-scrum-book/"><strong>A Scrum Book: The Spirit of the Game</strong></a>, 2019, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a>, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a>, <a href="https://www.scrumplop.org/">The Scrum Patterns Group</a></li></ul><h3>More Patterns Literature</h3><ul><li><a href="https://web.archive.org/web/20220718073804/https://3aec1b23-a-eadc3f87-s-sites.googlegroups.com/a/gertrudandcope.com/info/Publications/Patterns/Process/PLoPD1/aboutDoc/ProcessPatterns.pdf?attachauth=ANoY7cp5BGkx8haKt6Wu6k5LGJFc_lFNTqxGQ9vFEhi2RwG8XqNlQ6GYV7mZkKTB64FZAleXlLyVeXKhBIKoO6I2F-cqQJ5bTdvTWnNtVcLK5-20UUnkSmYvx0FyvuCDvNHl3156rYhqP0fcHNfP9dcjDi1kCNYxX_juL7q3AEv-AB1h8ficoNoMxx7ZEC8FqZuzoFkE-_QhOXcqQgNLguUUrD-8znhe3_g2FdXBQ9CF-hnKPwlm0kvkhYxd_pNBEsngZeB4zjx-gvIO50_x5ex_RlGdMmg9uJY_s0lwQeWuEr495A7KDLE%3D&amp;attredirects=0"><strong>A generative development-process pattern language</strong></a>, 1994, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a></li><li><a href="https://c2.com/ppr/episodes.html"><strong>EPISODES: A Pattern Language of Competitive Development</strong></a>, 1995, <a href="https://en.wikipedia.org/wiki/Ward_Cunningham">Ward Cunningham</a></li><li><a href="https://hillside.net/plop/plop97/Proceedings/beedle.pdf"><strong>cOOherentBPR — A pattern language to build agile organizations</strong></a>, 1997, <a href="https://en.wikipedia.org/wiki/Mike_Beedle">Mike Beedle</a></li><li><a href="https://drive.google.com/file/d/10grvt6jXMWbb1by8Y6tlBlBo9Sfjy_Ih/view"><strong>Patterns in Software Development</strong></a>, 2003 Cutter Consortium, <a href="https://www.linkedin.com/in/joshuakerievsky/">Joshua Kerievsky</a>, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a>, <a href="https://www.linkedin.com/in/alshalloway/">Alan Shalloway</a>, <a href="https://www.linkedin.com/in/dirkriehle/">Dirk Riehle</a>, <a href="https://www.linkedin.com/in/steveberczuk/">Steve Berczuk</a>, <a href="https://www.linkedin.com/in/lindarising/">Linda Rising</a>, <a href="https://www.linkedin.com/in/estherderby/">Esther Derby</a></li><li><a href="https://drive.google.com/file/d/1wxqsCgJIUDzxvS0U6ECMxUMCqS6n9jD6/view"><strong>Organizational Patterns</strong></a>, 2005 Cutter Consortium, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a>, <a href="https://www.linkedin.com/in/neil-harrison-900879/">Neil Harrison</a>, <a href="https://www.linkedin.com/in/gertrudbjornvig/">Gertrud Bjørnvig</a></li><li><a href="https://www.oreilly.com/library/view/fearless-change-patterns/0201741571/"><strong>Fearless Change</strong></a>, 2004, <a href="https://www.linkedin.com/in/lindarising/">Linda Rising</a>, <a href="https://www.linkedin.com/in/mary-lynn-manns-b592a8/">Mary Lynn Manns</a></li><li><a href="https://books.google.de/books/about/Organizational_Patterns_of_Agile_Softwar.html?id=6K5QAAAAMAAJ"><strong>Organizational Patterns of Agile Software Development</strong></a>, 2005, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a></li><li><a href="https://www.oreilly.com/library/view/more-fearless-change/9780133966534/"><strong>More Fearless Change</strong></a>, 2015, <a href="https://www.linkedin.com/in/lindarising/">Linda Rising</a>, <a href="https://www.linkedin.com/in/mary-lynn-manns-b592a8/">Mary Lynn Manns</a></li></ul><h3>Videos</h3><ul><li><a href="https://www.youtube.com/watch?v=ZUCZYHSD8dg"><strong>Joshua Kerievsky explains Patterns &amp; Pattern Languages</strong></a></li><li><a href="https://www.youtube.com/watch?v=z_QzdKci6OY"><strong>Christopher Alexander: Patterns in Architecture (OOPSLA 1996)</strong></a></li><li><a href="https://www.youtube.com/watch?v=LYsl19xEvzM"><strong>Patterns: The New Defacto Scrum Standard</strong></a>, 2013, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a></li><li><a href="https://www.youtube.com/watch?v=NSMrGZNdfOg"><strong>Scrum Patterns</strong></a>, 2020 Agile Bratislava, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a></li><li><a href="https://www.youtube.com/watch?v=2k1Oj-mQKnE"><strong>Scrum Patterns</strong></a>, 2020, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a></li><li><a href="https://www.youtube.com/watch?v=eURv3rBJMXI"><strong>Masterclass: Scrum Patterns</strong></a>, 2024, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15062fc30656" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life Is Too Short To Be a Scrum Master]]></title>
            <link>https://medium.com/@omidvar.aria/life-is-too-short-to-be-a-scrum-master-d2532df2df53?source=rss-c98461c29fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2532df2df53</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[change-agent]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[agile-coach]]></category>
            <dc:creator><![CDATA[Aria Omidvar]]></dc:creator>
            <pubDate>Mon, 01 Dec 2025 07:58:27 GMT</pubDate>
            <atom:updated>2026-03-10T16:52:47.669Z</atom:updated>
            <content:encoded><![CDATA[<p>Inside, I feel at peace with my decision, but strangely, when I try explaining it to others, feelings of frustration and failure bubble up. I suppose I am still processing it, even though I have made up my mind to no longer work as a Scrum Master, Agile Coach, or any other similar role.</p><h3>A Failure of Sorts</h3><p>The first feeling I have regarding this change in professional course is one of failure. I have taken a few unrelated paths in my professional life, but the last years have been relatively coherent. I transitioned from Computational Linguist to Software Developer to Scrum Master, and then to the more method-agnostic variant of it, called Agile Coach. However, I ultimately came to prefer the title Agile Practitioner. I fell in love with the practice of Agile, Lean, and all the new approaches that had emerged as a response to the needs of the modern world of work. I was fascinated with the field and felt like a kid in an amusement park who wanted to try and learn everything. I felt rejuvenated and on a mission. I had a pretty steep development curve too, and felt like I had finally found my calling.<br>Now, after roughly 7 years, I see that phase has come to an end. Do not mistake me. This is not a requiem. I feel as alive as I have ever felt. The path ahead is just as exciting, if not more. This essay is my personal reflection on how I arrived at this point, in addition to being a follow-up to <a href="https://medium.com/@omidvar.aria/an-agile-practitioners-professional-development-journey-part-1-the-chronology-1e0845091cc5">my essay from April 2024</a>. I hope other fellow practitioners find something useful in this one as well.</p><h3>A Curious Case</h3><p>In all industries and fields of work that I am aware of, the more competent you become, the more sought after you will be. Well, not in our industry. This was the first red flag I noticed about two years ago. In my own experience and from what I have heard from peers, most employers look for less experienced SMs and ACs so that they can put them in a box, hand them a checklist, and kindly ask them to do what they are told. I have heard and read all the fairytales about the modern workplaces that want true agility and put people first, blah blah blah. All the evidence that I have shows me that at least 90% of these claims are nothing but marketing and empty hypes. The other rare situations are also only temporary and limited to a small part of the organization.<br>Just imagine a Civil Engineer, a Mechanical Engineer, a Medical Doctor, a teacher, or any other professional who does something that relies on their knowledge, experience, and expertise. How on earth would they become less desired as a workforce when they develop, learn, and grow more?<br>I have an idea how.</p><h3>Battle on All Fronts</h3><p>For a good while, I had the illusion that the old-school approach to management was the problem and that I was the champion of the poor Developers and powerless teams. Imagine a knight in full armor on a horse defending the weak, the oppressed. My knowledge, skills, experience, and expertise were my weapons, armor, and ride. I had one goal: to enlighten the misled, to show them a better way to treat the commoners and gain even more profit while doing so.<br>I could not be more wrong. It was quite a bitter reckoning that I was in battle on all fronts. Managers, Middle Managers, Engineering Managers, Product Owners, and even my most beloved Developers. Every once in a blue moon, someone would express appreciation for how I was helping them or how a particular method I had applied blew their mind. But, truth be told, I was misunderstood and excluded by and from most circles. I was an outsider to all parties, and I have heard the exact same observation from virtually all fellow SMs and ACs.</p><h4>Management by Numbers</h4><p>Where should I start? Let’s start with the most obvious one: the old-school, Tayloristic, deterministic-minded management. I have lost count of how often I have come across this one personally or in others’ descriptions of their circumstances. Of course, none of these managers would admit that about themselves. I have had firsthand experience with ones who even called whatever they were doing Agile. Ron Jeffries beautifully called this <a href="https://ronjeffries.com/categories/dark-agile/">Dark Agile</a>. The truth is that what they were doing was, in Deming’s words, management by numbers, which is really, if you peel it until you reach its core, management by deflection of responsibility.<br>These managers want evidence, basically some numbers, to justify any effort. The first impression is that “if you can’t measure it, you can’t manage it,” but when you look at its heart, the evidence, the numbers they are asking for are not for themselves. They are for their superiors. This way, if the overall results are not appealing to the big bosses, these managers can show them the numbers and say, “Here, see for yourself. I have reduced costs this much. The failure can’t be mine. I’ve done everything I could, and the ‘evidence’ confirms that.”<br>Most, if not all, of the big decisions that I have seen in my career were made by extremely oversimplified first-order arguments that did not go beyond a simple cost-benefit analysis, where all higher-order costs were neglected and much of the perceived benefits were mere wishes.<br>Why did they hire Agile Practitioners, you might ask? These managers hire Agile Practitioners because they see it as a trendy, cute way to get things organized and monitored, measure productivity, and claim the “we are Agile” badge. That is a direct consequence of Agile becoming synonymous with Good and the opposite of Evil. No one wants to be Not Agile, and everyone goes to ridiculous lengths to fake having earned it.</p><h4>Beware of Their Turfs</h4><p>Then come our own Engineering Managers and Product Owners. These can be the best allies of an Agile Practitioner to drive real change and make significant improvements within the boundaries of teams, across teams, and even the larger organization. But of course, that would happen if you are not conquering their territories and reducing their political power. Let’s face it, if a PO is already owning the product, and assigning and monitoring the work like a good old Project Manager, why would he welcome your presence and your efforts in making the team self-organizing and empowered? For the benefit of the organization and business? He would, of course, if that was his priority. But evidently, it is not. Staying relevant, needed, and depended on are much stronger drivers of our professional behavior than the collective win.</p><h4>Comfortable in Fear</h4><p>And to my biggest surprise, even many developers, I would say most developers, are not interested in self-driving collaborative work. And when they do show some interest, it only goes so far to get some slightly better results, to get out of the hole they are stuck in. All efforts stop there. The worst cases are when teams insist that Agile approaches to work are yet another trick from the oppressive management, fooling them into working harder and monitoring their every step. In their defense, they do have a point. There is such a thing as Dark Agile. However, that also closes the door to any well-intended effort to create a healthier, more collaborative, self-leading, team-oriented work.</p><h4>Transformation Theater</h4><p>This one should blow anyone’s mind. It did mine. Even Transformation efforts are run by managers who, at the end of the day, want to show some clean and happy statistics to the big bosses, so every attempt at actually transforming anything is killed at inception by the very agents of change. So much of what is called Agile Transformation is nothing but a theater, a game of make-belief; a very lucrative one, nonetheless.<br>It is simple math. There is a budget for the Transformation, and it is much easier not to truly change anything but show superficial improvements that keep the money coming. A few years and thousands of Euros later, the Transformation is killed and replaced by another fad offered by other charlatans, and in the meantime, everyone wins. The agents of change create make-belief evidence of their achievements. Managers brag about bringing the enterprise to modern ways of working and bringing home that sweet “we are Agile” badge. Marketing milks this cow like any other. Everyone gets something out of this theater, and by the time it is over, there will be another theater to set up.</p><h4>At the Heart of the Matter</h4><p>The sad truth that no one dares verbalize is that everyone is insecure. Everyone’s first and strongest driver is fear; fear of becoming redundant, fear of losing influence, fear of losing the sweet income, fear of leaving one’s comfort zone and stepping into the unknown, fear of greatness and trading it for the comfort of mediocrity.<br>Agile, Lean, and all the newer approaches are not fighting against any institution. They are fighting against our very own nature, not our best angels, nevertheless the very human nature. For this reason and this reason alone, all such approaches are doomed to fail to deliver repeatable, sustainable results.</p><h4>Too Little, Too Short</h4><p>These battles on all fronts may sound like I am demonizing everyone and claiming that no one ever understood, appreciated, or supported my work. Not at all. I have had the absolute pleasure of working with brilliant managers, product people, and software people who not only understood and supported my work and the work of others in my position but even became mentor figures to me.<br>But there is a caveat. All of these fair winds were very limited in their domain of influence and the time they lasted. At best, we could do some good work in a little bubble until it burst. Sometimes the domain was larger, but someone with a heftier title would come along and break everything we had built. I wish these were exceptions, but my years in the trade and everything I hear from my peers tell me that these are the norm.</p><h3>To Each His Own</h3><p>Regardless of how this essay is perceived, I do not intend to make a point that no one should stay in the role of Scrum Master or Agile Coach, that no one should shift to Agile Delivery Manager or Agile Project Manager, or that no one should try showing their worth.<br>On the contrary, I root for all those who are still trying to make a difference, who are trying to show their value, or to redefine their role so it fits the demands of the existing organizations. This essay reflects my journey, my development, and my path. It is a very personal view, a very personal experience, and a very personal decision.<br>However, having talked to a few fellow practitioners, I know that my experiences and reflections are not unique, and my guess is that many find themselves in similar situations, yet not many speak out. My sanity was restored when I found out that so many others around me are having similar experiences. I hope these words help others figure out that they are not alone and that it is not they who need fixing.</p><h3>If Only</h3><p>To dig deep in my soul and take these thoughts out was not easy or comfortable, but I felt I owed it to myself and to others who are on the same path or are considering it. Even though I have talked with several experienced practitioners and I know that their thoughts and feelings are very similar to mine, I can not claim that this is how everyone feels. So, I encourage everyone who has worked in similar fields to share their thoughts in their own words. I believe the result will be shocking and enlightening. This has been in the shadows for too long and deserves to be brought to light.</p><h3>Making Enemies Happy</h3><p>There is an expression in my mother tongue, Farsi, that literally translates to <em>making enemies happy</em>. It means you have said or done something that has made your enemies happy in the eyes of your kind, your allies.<br>I know much of what I have expressed in this article makes many who are not fond of Scrum happy. They might even take this as a testimony of Scrum’s failure. They could not be more wrong.<br>First of all, I do not consider myself belonging to any tribe, be it Scrum or Agile. I have expressed my views on that in another article. Hence, I see no allies or enemies. But still, the saying makes a point.<br>Some of these happy people are those who consider themselves agilists but of different flavors than Scrum. All my points hold true for them as well. The fault is not in the method but in the raw nature of humans and organizations.<br>Some of the happy people may consider themselves of entirely different tribes, such as Lean, Product Management, or Leadership. I have more than sufficient evidence that the practitioners and coaches in their tribes have virtually identical problems. Once again, human nature and the nature of organizations are the same for them.<br>The point is, if you are reading this article and you are still smiling, you have not understood it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2532df2df53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hitchhiker’s Guide to Hexiverse — Software Teaming]]></title>
            <link>https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7?source=rss-c98461c29fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/21a574ba46e7</guid>
            <category><![CDATA[mob-programming]]></category>
            <category><![CDATA[ensemble-programming]]></category>
            <category><![CDATA[extreme-programming]]></category>
            <category><![CDATA[software-teaming]]></category>
            <category><![CDATA[lean-software-development]]></category>
            <dc:creator><![CDATA[Aria Omidvar]]></dc:creator>
            <pubDate>Mon, 24 Nov 2025 14:07:35 GMT</pubDate>
            <atom:updated>2026-02-12T12:52:30.510Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Hitchhiker’s Guide to Hexiverse — Software Teaming</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YdN5l1mGF0YGx7o5sO1dnA.png" /><figcaption><strong>Software Teaming</strong> from <strong>Hexiverse</strong></figcaption></figure><p>In this article, I suggest a Hexi set for <strong>Software Teaming (Mob Programming)</strong> and expand on each Hexi. The corresponding Hexi set can be found <a href="https://miro.com/app/board/uXjVKv84GGU=/?moveToWidget=3458764607401738923&amp;cot=14"><strong>here</strong></a>.</p><p>This Hexi set is mainly based on the experience reports by <strong>Woody Zuill</strong> [1], <strong>Jason Kerney</strong> [2], <strong>Aaron Griffith</strong> [3], <strong>Chris Lucian</strong> [4], the book by Woody and <strong>Kevin Meadows</strong> [5], and Woody&#39;s talks on YouTube.</p><h3>Foreword</h3><p>When researching for this guide, I focused on <em>the original Mob</em> where Mob Programming emerged. When I was developing the Hexi set, I noticed that the result may fall into the same trap that the famous Spotify whitepaper [6] did, so I consciously avoided presenting a frozen picture of what Mob Programming <em>is</em> and instead focused on its organic development.</p><h3>One Meaning, Many Names</h3><p>Woody first referred to this approach in 2012 as <strong>Whole-Team Programming</strong>.<br>He was also already using the name <strong>Mob Programming</strong> for a <em>Coding Dojo</em> style that he was running around the same time. He had borrowed that name from a paper [7] presented in Extreme Programming Perspectives [8]. When people approached him to ask about the new approach to teamwork he was advocating, they often called it <em>Mob Programming</em> instead, and he went with the flow.<br>Later, as a reference to Amy Edmondson’s <em>teaming</em> concept [9], he preferred <strong>Software Teaming</strong>.</p><p><strong>Ensemble Programming</strong> is yet another name for the same concept.</p><p>As for Woody, he does not care what it is called, but rather what it is.</p><p>For the sake of familiarity, I stick with Mob Programming or MP for short.</p><h3>Original Sources</h3><p>This Hexi set is merely an attempt to integrate Software Teaming into the Hexiverse and can only carry a glimpse of the wisdom I have learned from Woody in his online events, the wonderful book he co-authored with Kevin, and the 4 original experience reports.</p><p>The book is rich with practical advice drawn from real-world experience, and the reports are detailed and invaluable as resources. I can only hope this guide and its corresponding Hexi set to introduce MP as it deserves and integrate it into the Hexiverse. However, this cannot replace any of the sources listed at the end of this guide.</p><h3>The Structure and Organization of This Hexi Set</h3><p>There was a certain narrative in the original resources [1][2][3][4][5] that caught my attention. It was a narrative of <em>origin stories</em>, artisanry, and natural &amp; organic emergence. The result of those evolutions and mutations is what we recognize as Mob Programming. And although MP looks <em>radical</em> when seen in its mature form, it looks <em>inevitable</em> when seen through its emergent development.</p><p>Because of this narrative, I avoid the usual <em>roles-events-artifacts</em> or <em>values-principles-practices</em> structures. I may change that in the future, but for the time being, I try organizing this guide in the image of its origin story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xSDV45dMh5_LF4MVCanZA.png" /></figure><h3>Software Teaming</h3><p><strong>Software Teaming</strong> is exactly what the name suggests:</p><blockquote>All the brilliant minds working together<br>on the same thing<br>at the same time<br>in the same space<br>at the same computer.<em> [5]</em></blockquote><p>This might sound too simplistic, too inefficient, and totally unintuitive. What follows will help understand why this overly simple-looking approach is not only <em>efficient</em> but also <em>effective</em> and an antidote to many dysfunctions in software teams and organizations.</p><h3>Self-Organizing Team</h3><blockquote>The team doing the work can best determine <strong>how</strong> to do that work.<em> [5]</em></blockquote><p>Here, <em>self-organization</em> is synonymous with <em>autonomy on the how.</em></p><p>Self-organization seems to be the root of everything that became possible in the original MP team. They could choose how to do what was expected of them to be done.</p><p>Related patterns: <strong>Self-Organizing Teams</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h3>Support &amp; Trust</h3><p>Self-organization goes only so far if it is not complemented with <em>support &amp; trust</em> from higher management and the larger organization.</p><p>Related patterns: <strong>Support &amp; Trust</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h3>Continuous Improvement</h3><p>At first, I only had Retrospectives in this Hexi set, but the more I read, the more convinced I became that they had a strong spirit of continuous improvement. And although continuous improvement was often manifested in their Retrospectives, the way they approached <em>retrospecting</em> was only a result of their <strong>radical continuous improvement mindset</strong>.</p><p>Related patterns: <strong>Continuous Improvement</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>], <strong>Improvement</strong>, <strong>Reflection</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">XP</a>]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hmnhzPkdTJI_dplGzy7JQg.png" /></figure><h3>Retrospectives &amp; Retrospecting</h3><p>Similarly, at first, I only had Retrospectives, but the accounts directed me to <em>a continuous attitude</em> toward Retrospectives manifested in their <strong>JIT Retros</strong> and <strong>Micro Retros</strong>. In other words, they turned the <strong>Retrospective</strong> <em>event</em> into a <strong>Retrospecting</strong> <em>attitude</em>/<em>habit</em>.</p><h4>Bi-weekly, Weekly, and Daily Retrospectives</h4><p>The team started with bi-weekly Retros, then increased their frequency to weekly and eventually daily.</p><h4>Just-in-Time and Micro Retrospectives</h4><p>They also held <strong>JIT Retrospectives</strong> for capturing good things and addressing areas for improvement, and very short Retros that I call <strong>Micro Retros</strong> after shorter activities that were nevertheless worthy of reflection and improvement.</p><p>It is important to note that when a team collaborates in a <em>teaming</em> formation, the density of the collaboration provides enough content to reflect on after just one day or even after an intensive <em>teamwork</em>. Toward the other end of the collaboration spectrum, teams that do more <em>taskwork</em> rather than <em>teamwork</em>, AKA the <em>Scatter-Gather</em> pattern, can afford to reflect on their collaboration after one or two weeks.</p><p>As for Retro formats, they mention the famous <em>Lean Coffee</em> format and the awesome <strong>Turn Up the Good</strong> format.</p><p>See also: <a href="https://www.industriallogic.com/blog/scatter-gather/"><strong>Scatter-Gather</strong></a>, <a href="https://leancoffee.org/"><strong>Lean Coffee</strong></a></p><p>Related patterns: <strong>Sprint Retrospective</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>]</p><h3>Turn Up the Good</h3><p><strong>Turn Up the Good</strong> is a daily Retrospective at the end of the day, focused on <strong>what worked well</strong> so we can do <strong>more of that</strong>.</p><p>The first time I heard of Turn Up the Good, it blew my mind. I always took pride in mastering Retrospectives and knowing them top to bottom, and inside and out. I was mistaken. As opposed to most Retrospectives that focus on what needs improvement, Turn Up the Good focuses on what is going well and then tries to amplify those strengths. Its approach to improvement reminds me of <a href="https://en.wikipedia.org/wiki/Positive_psychology">Positive Psychology</a>’s approach to improving humans’ mental well-being.</p><h3>Exploration &amp; Experimentation</h3><p>Along with Continuous Improvement, <strong>radical Exploration &amp; Experimentation</strong> seems to be an omnipresent characteristic of the original MP team. Much of what later became the patterns of MP is the result of these explorations and experiments.</p><h4>Gradual Introduction &amp; Adoption</h4><p>Software Teaming is not an intentionally designed approach to teamwork. It grew organically and slowly out of Coding Dojos. Most of the patterns that emerged took considerable time. The authors advise taking things slowly and without force. For example, holding weekly or daily Coding Dojos with optional attendance is a good starting point.</p><h3>Continuous Collective Learning &amp; Practice</h3><blockquote>Software Teaming emerged out of an environment where we focused on turning up the good of <strong>learning for the entire team</strong>. <em>[5]</em></blockquote><p><strong>Learning and Practice</strong>: While theoretical learning is beneficial, learning complemented by practice or even learning through practice has greater value and transfers more effectively to practical scenarios.</p><p><strong>Collective Learning &amp; Practice</strong>: While learning &amp; practicing individually is beneficial, learning &amp; practicing collectively has even greater value because it develops not only technical skills but also <em>team and collaboration skills</em>, which in turn transfer more effectively to practical team scenarios.</p><p><strong>Continuous Collective Learning &amp; Practice</strong>: To make learning a part of the team’s DNA, it needs to become a <em>habit</em>. Teams can set aside time for their collective learning &amp; practice. <strong>Morning Learning Hour</strong> and <strong>Coding Dojos</strong> are manifestations of such a team habit.</p><p>Related: <em>Learn As You Earn</em>, <em>Amplified Learning</em></p><p>See also: <a href="https://en.wikipedia.org/wiki/On-the-job_training"><strong>On-the-Job Training</strong></a></p><h3><strong>Coding Dojos</strong></h3><p>Woody was first introduced to <strong>Coding Dojos</strong> by <a href="https://www.linkedin.com/in/llewellynfalco"><strong>Llewellyn Falco</strong></a> and incorporated it into his coaching. When Woody and his team were given a particularly challenging task, they decided to apply the same style of development to this real-world scenario. As a result, Software Teaming emerged as an approach to teamwork. Nevertheless, they kept their habit of Coding Dojos.</p><p>Their Coding Dojos were 3 hours <strong>every Friday</strong> with <strong>no obligation to join</strong>, and following the <strong>Driver/Navigator</strong> model.</p><p>Coding Dojos bear many direct and indirect fruits. On the surface, teammates <strong>learn</strong> from each other’s knowledge and skills the same way that two developers learn in <em>Pair Programming</em>.</p><p>Related patterns: <strong>Pair Programming</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">XP</a>]</p><h3>Morning Learning Hour</h3><blockquote>During our work, <strong>peripheral questions</strong> would arise.<br>We decided to try holding <strong>an hour-long learning session each morning</strong> to cover these questions.<em> [5]</em></blockquote><p>This is a practice that I have not seen anywhere else, yet it makes absolute sense. I believe the <em>teaming</em> behavior makes this not only possible but also necessary.</p><h3>Team Conference Visits</h3><p>The original Mob made a habit of attending conferences related to their work 2–3 times a year. Participating as a team served them both as a <strong>learning</strong> opportunity and as a <strong>team-building</strong> one.</p><h3>Safe to Learn</h3><blockquote>make it easy and comfortable for everyone to work <strong>without fear of feeling exposed</strong>.<em> [5]</em></blockquote><p>As valuable as Collective Learning &amp; Practice is, it comes with challenges. For example, it is very difficult for most developers to code in front of others. It exposes our lack of skills and knowledge. Hence, it takes a great deal of <strong>courage</strong> to overcome that fear. It also demands a higher degree of <strong>understanding</strong>, <strong>empathy</strong>, and <strong>respect</strong> from others to make it safe for each other to learn.</p><p>Every challenge is an opportunity for growth, and this one is not an exception. Individuals who engage in Collective Learning &amp; Practice demonstrate <strong>vulnerability</strong>, practice <strong>empathy</strong> and <strong>respect</strong>, and inevitably, develop a deep level of <strong>trust</strong> that is hard to achieve otherwise.</p><p>See also: <a href="https://en.wikipedia.org/wiki/Psychological_safety"><strong>Psychological Safety</strong></a></p><p>Related patterns: <strong>Safety</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-modern-synthesis-b1e3b61ba3c1">Modern Synthesis</a>]</p><h3>Golden Rules: Kindness, Consideration, Respect</h3><blockquote><strong>Kindness</strong>: Act in a kindly way. Be <strong>warm-hearted</strong>, <strong>gentle</strong>, and <strong>polite</strong>. Display a <strong>pleasant disposition</strong> to others. Show <strong>concern</strong> for others.</blockquote><blockquote><strong>Consideration</strong>: Consider your team members’ <strong>ideas</strong>. To do this, we need to be able to <strong>listen</strong>. To listen requires <strong>humility</strong>. We also need to consider each others’ <strong>feelings</strong>.</blockquote><blockquote><strong>Respect</strong>: Respect is like a diplomatic protocol. It’s about allowing others to keep their <strong>self-esteem</strong>. We can <strong>disagree</strong> and still be <strong>respectful</strong>.</blockquote><blockquote>Put simply: <strong>treat others the way they would like to be treated.</strong><em> [5]</em></blockquote><p>When trying to make their environment <strong>safe to learn</strong>, the team agreed on what I call the <strong>golden rules</strong> of <strong>kindness</strong>, <strong>consideration</strong>, and <strong>respect</strong>.</p><p>What I like most about the <em>golden rules</em> is that they go much deeper and farther than the common “nice” or even “politeness”. Nice and polite, although sufficient for general social interactions with strangers, fall short in the context of <em>teamwork</em>, <em>collaboration</em>, and <em>inter-dependence</em>. In teamwork, teammates need to hold each other to certain standards and <em>challenge</em> each other for growth and the greater good. This is where the golden rules become essential.</p><p>Related patterns: <strong>Respect</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">XP</a>], <strong>Respect</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>], <strong>Community of Kindness &amp; Creativity</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-modern-synthesis-b1e3b61ba3c1">Modern Synthesis</a>]</p><h3>Driver/Navigator Model</h3><blockquote>For an idea to go from someone’s head into the computer, it must go through someone else’s hands. — Llewellyn Falco</blockquote><p>I was hesitant to include Driver/Navigator in the Hexi set, but due to its central role in their Mobbing style, I decided to include it.</p><p><strong>Randomized Time-boxed Rotations</strong>: For their Driver/Navigator style, they generate a <strong>randomized list</strong> of team members every morning.</p><p><strong>Automated Driver Rotations</strong>: A software announces the next driver at the end of each rotation.</p><p><strong>Even Navigation</strong>: Just as Driving is evenly distributed among the team, Navigation is also expected to be evenly distributed.</p><h3>Team Space</h3><p>Software Teaming, due to its particular dynamics, relies on the whole team being in the <strong>same room</strong> or remote call. To a lesser degree, the same characteristic has been suggested in Extreme Programming and Scrum.</p><p>After the COVID pandemic, many teams noticed they could recreate their <em>Team Space</em> virtually. Team spaces can be extended beyond the collaborative space and tools to include artifacts such as the <em>Team Agreement</em>.</p><p>Software Teaming [5] is filled with practical advice on the physical or remote setup, ergonomic considerations, and hygiene factors.</p><h4>Individual &amp; Pairing Workstations</h4><p>Individuals and pairs can split from the Mob and work in workstations dedicated to solo work or pair programming.</p><p>The possibility of getting distance from the interaction-dense environment of Mobs is essential for <strong>introverts</strong>. Aaron Griffith’s paper [3] is testimony to this.</p><p>Related patterns: <strong>Sit Together</strong>, <strong>Informative Workspace</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">XP</a>], <strong>Colocated Team</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>]</p><h3>Team Working Agreement</h3><p>Team Agreement is one of the most recurring patterns of good teams. What it contains depends on what the team sees as necessary to have an explicit mutual understanding and agreement on. In the case of Woody’s team, <em>Kindness, Consideration, and Respect</em> were the result of discovering and establishing their Team Agreement.</p><p>Team Agreements are living artifacts and subject to revision and continuous improvement.</p><h3>Team Rhythm</h3><p>A natural result of Software Teaming is that the whole team synchronizes their <strong>working hours and breaks</strong>. Woody’s team developed a <strong>daily rhythm</strong> of <strong>Morning Learning Hour</strong>, <strong>Team Lunch Break</strong> with a walk, and a <strong>Retrospective</strong> at the end of each day.</p><p>What <em>habits and rhythm</em> each team develops can be unique to them, but I can imagine many teams develop similar habits in their <em>Daily and Weekly Rhythms</em>.</p><h3>Team Cognition</h3><p>In Jason Kerney’s paper [2], he reports an observation that the Mob developed a <strong>Collective Memory &amp; Knowledge</strong>. He also points out a related emergent phenomenon: different individuals in the mob develop complementary focus areas so that their <strong>Collective Attention</strong> covers all topics and areas.</p><p>See also: <a href="https://flowguides.org/guide.php#d66"><strong>Developing Cognitions</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oFtWWV9bRT2gW-ZP3XWmkQ.png" /></figure><h3>Micro-Iterations + Micro-Increments + Single WIP + <strong>Thin-Slicing + No Estimates + JIT Backlog Processing</strong></h3><p><strong>Micro-iterations</strong> are iterations where the team develops a new functionality or a meaningful part of a functionality in <strong>a day or two</strong>.</p><p>Every Micro-iteration results in a <strong>Micro-increment</strong>; a thin layer, increment, on top of the existing software.</p><p>When a Mob does Micro-iterations, there will be only a <strong>Single Work item in Progress</strong> at any given time.</p><p>A Micro-increment is only possible when the team cuts a very <strong>thin slice</strong> of the work ahead in order to deliver it in the next day or two.</p><p>Woody suggests slicing stories as thin as: <em>“Distinct, recognizable, understandable, cohesive (belongs together); a potentially valuable chunk of stuff. So it can be decoupled, worked on, deployed, and provided feedback.”</em></p><p>One result of Micro-iterations and Thin-slicing is that there are <strong>no estimates</strong> needed because there are no longer periods of time to plan for. In other words, the need for <em>planning</em> is eliminated, hence the need for <em>estimation</em> is eliminated as well.</p><p>Another result is that the team can do <strong>Just-in-Time Backlog Processing</strong>, where they <strong>prioritize</strong> and <strong>refine</strong> work items only when needed.</p><p>This may sound unfamiliar and radical. However, similar approaches have been suggested and practiced by Ron Jeffries, GeePaw Hill (<strong>Pull &amp; Swarm</strong>), and Alistair Cockburn (<strong>Elephant Carpaccio</strong>).</p><p>Related patterns: <strong>MMMSS</strong>, <strong>Pull &amp; Swarm</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-modern-synthesis-b1e3b61ba3c1">Modern Synthesis</a>], <strong>Micro-Increments</strong>, <strong>Thin-Slicing</strong>, <strong>#NoEstimates</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-whole-parts-steps-915fb44eafa9">Whole-Parts-Steps</a>]</p><h3>Roles</h3><p>The Driver/Navigator model brings about the 3 primary roles of <strong>Driver</strong>, <strong>Navigator</strong>, and <strong>Mobbers</strong>.</p><p>Some other temporary and emergent roles are <strong>Researcher</strong>, <strong>Sponsor</strong>, <strong>Rear Admiral</strong>, <strong>Automationist</strong>, <strong>The Nose</strong>, and <strong>Archivist</strong>. [10]</p><p><strong>Partners</strong> are similar to Product Owners or Business Experts.</p><p>In the case of the original team, Woody had the role of a <strong>(Technical) Agile Coach</strong>, although after the team matured, Woody left the company, and the teams did not have a permanent AC role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JAbUjU7pDY8YsgFzj08nsg.png" /></figure><h3>Behavioral Patterns</h3><p>As the original Mob was coming to be, certain behavioral patterns emerged as well. Below are the ones I could distinguish from the sources. Some of these are <em>team behaviors,</em> and some are <em>individual</em> ones.</p><h4>Hosting Mob</h4><p>Sometimes a Mob hosts other individuals or even entire teams for a period of time. This is similar to the <em>Swarming</em> pattern, but for teams instead of individuals.</p><h4><strong>Devil’s Advocate</strong></h4><p>Team members are encouraged to hold contradictory positions. [10] This is a sign of healthy teams.</p><p>See also: <a href="https://flowguides.org/guide.php#d610"><strong>Red Teaming</strong></a></p><h4><strong>Do Both</strong></h4><p>Encourages the team not to choose between two possible paths and instead try both and choose which one to pick later. [10] This is similar to <strong>Set-Based Development</strong>, only for a set of two.</p><h4><strong>Stop the Work Authority</strong></h4><p>Everyone on the team can raise a red flag and stop the work. This is similar to the <strong>Andon</strong> system in Toyota.</p><h3>Technical Practices</h3><p><strong>Test-Driven Development</strong>, <strong>Unit Testing</strong>, <strong>Continuous Integration</strong>, <strong>Continuous Delivery</strong>, and <strong>MVP</strong>s are some of the technical practices that the original Mob relied on.</p><p>To my surprise, I even found an example of <strong>Set-Based Development</strong> in their experience reports, where they describe working on several solutions to the same problem to have a better understanding of possibilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cahZXO9F7mgj6c6qysINuA.png" /></figure><h3>Mob of Mobs</h3><p>In his experience report, Chris Lucian explains in great detail the process of scaling MP for an entire software organization, including their preparations, the gradual approach, the challenges they faced, and the lessons learned.</p><p>I wanted to call this Team of Mobs at first, but I noticed that, interestingly, even when at scale, they have highly collaborative behaviors, the same way that they do in each Mob. So, I chose Mob of Mobs (MoM) instead.</p><p>See also: <a href="https://flowguides.org/guide.php#d611"><strong>Multiteam Systems</strong></a></p><h3>In-House Training</h3><p>As a preparation for the scaling process, some technical topics that were known to be essential for MP were provided in the form of training for the new hires.</p><h3>Technical Leaders</h3><blockquote>As the teams were growing, we discovered that we had naturally emerging technical leaders.</blockquote><blockquote>Technical leaders should be navigating less and teaching more… reinforced technical excellence within the team and allowed the senior developers to build up their teammates.<em> [4]</em></blockquote><h3>MoM Working Agreement</h3><p>Similar to a Working Agreement for teams, a Team of Teams (ToT), or in this case, a Mob of Mobs (MoM), benefits greatly from establishing a Working Agreement as well.</p><p>All Working Agreements are living documents, of which the generation process is more important than the resulting shared document. They are always subject to change and revision.</p><h3>Monthly MoM Retrospectives</h3><p>A monthly Retrospective for the MoM to improve their cross-Mob collaboration and their overall performance as a MoM.</p><h3>Flat MoM</h3><p>When growing the MoM in Hunter Industries, Chris Lucian opted for a flat organization with him as the sole leader of the organization. To make this happen, he had to distribute much of the management responsibility across the MoM.</p><h3>Distributed Management</h3><p>When distributing the management tasks, they tried two approaches: a fluid <strong>Management Mob</strong> that would take on the responsibility, and a <strong>Management Tasks Kanban</strong> that contained all that needed to be done.</p><h3>Servant Leader</h3><blockquote>my role as the director is to <strong>provide</strong> everything the team needs to be successful in both a <strong>technical</strong> and <strong>psychological</strong> sense.<br>I try and <strong>influence the system</strong> only in ways that <strong>support</strong> the overall <strong>direction</strong> of the team.<em> [4]</em></blockquote><p>There are different leadership approaches/styles, and each one is fitting to a certain context. In any given real-world scenario, we have a blend of contexts that calls for a blend of different leadership approaches. Chris’s description of his engagement with the Mobs and the larger organization makes it clear that his prominent leadership style is <strong>Servant Leadership</strong>.</p><p>See also: <a href="https://en.wikipedia.org/wiki/Servant_leadership"><strong>Servant Leadership</strong></a>, <a href="https://www.intentbasedleadership.com/"><strong>Intent-Based Leadership</strong></a></p><h3>People Skills</h3><p>In his role, Chris tried to enable the Mobs by developing <strong>Communicating</strong>, <strong>Coaching</strong>, <strong>Teaching</strong>, and <strong>Managing</strong> skills.</p><p>The first time I learned that leaders are responsible for the <em>development</em> of their direct reports was from Marty Cagan’s books. His emphasis on coaching Product Managers by their Product Leader was eye-opening and yet missing from most of the environments I have seen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Jln1Bv2Ma-ZUtO3cvpWkg.png" /></figure><h3>Behavioral Patterns</h3><h4>Grow &amp; Split</h4><blockquote>A Mob is too big only when someone in the Mob is <strong>not contributing or learning</strong>.<em> [3][4]</em></blockquote><p>This seems to be an organic process, where the Mob grows to a degree that some members notice their presence in the Mob is no longer serving its purpose; hence, they split and form their own Mob around a <em>stream of work</em>.</p><h4>Break the Silo</h4><p>This is a <em>behavioral pattern</em> of MoM when they notice that some knowledge is siloed in certain Mobs, so in order to break the silo, they exchange members with those deprived of that knowledge.</p><h4>Fluid Mobs</h4><p>Members flow between Mobs as long as each Mob remains large enough and contains sufficient skills and knowledge to be productive and thriving.</p><h4>Built-in Disorder</h4><p>The ability to function smoothly in the absence of any team member became an aspiration of the MoM. Think of it as the ability to let anyone take a vacation at any time without prior <em>planning and preparation</em>. One manifestation of that aspiration is that no one stays on the same project longer than two years.</p><p>This approach is similar to Chaos Engineering in software, which tests and eventually improves resilience by introducing <em>intentional disorder</em>.</p><p>See also: <a href="https://en.wikipedia.org/wiki/Chaos_engineering"><strong>Chaos Engineering</strong></a></p><h4>Negotiated Composition</h4><p>This is another behavioral pattern where the Mob composition for each project is negotiated along with the minimum number of developers per project. This is similar to <strong>Self-Selecting Teams</strong>.</p><h4>Divergent Cultures</h4><blockquote>The culture of the different project teams also began to diverge from the beginning… there is a personality spectrum that has surfaced within the different teams.<em> [4]</em></blockquote><p>Chris Lucian’s description of his observation reminded me of a similar point made in Wardley Mapping.</p><p>In <a href="https://learnwardleymapping.com/book/">Wardley Mapping</a>, <a href="https://www.linkedin.com/in/simonwardley/">Simon Wardley</a> makes an intelligent case for different cultures of different teams and organizations at different stages of the development of a product.</p><h3>Technical Practices</h3><p>After scaling from one Mob to MoM, they noticed the need for a common language across Mobs. <strong>Behavior-Driven Development</strong> provided that. Similarly, <strong>Integration Tests</strong> and <strong>Automated Testing</strong> enabled the MoM to maintain the integrity of their software across Mobs.</p><h3>Some Thoughts</h3><p>The deeper I look into Mob Programming, the more I see it as one of the best and purest manifestations of Agile and Lean values, principles, and practices. It feels as if it is a mutation of XP and Scrum to their truest forms and a reincarnation of Toyota in the domain of software product development.</p><p>As described in Woody and his team’s writings, they realized Lean and Agile values, principles, and practices, and broke new ground while doing so.</p><p>In their writings, I find examples of <strong>Set-based Development</strong> and <strong>Andon </strong>mechanism, while they achieved true <strong>one-piece flow</strong> and embodied <strong>continuous improvement</strong> like no other example I can think of.</p><p>Their Mob Programming is literally the Scrum formation, the whole team moving forward as one.</p><p>Their approach to <em>teamwork</em> redefines teamwork and sets the standard higher than I had seen before.</p><h3>One Last Word</h3><p>I am fascinated by Mob Programming and deeply influenced by Woody Zuill. This guide and its corresponding Hexi set are only a token of my admiration for Woody and the pioneering Mob Programmers. I only hope to have captured MP’s spirit without damaging its essence.</p><p>As for readers of this guide and users of this set, please take them only as one possible understanding, an opinionated view, a suggestion, and an introduction to the wonderful world of MP. Do your own research, and as always, never outsource your <em>critical thinking</em> to anyone else.</p><h3>Your Feedback</h3><p>If you have comments or suggestions, please do not hesitate to express them here in the comments or message me directly on <a href="https://www.linkedin.com/in/aria-omidvar/">LinkedIn</a>. I welcome all kinds of commentary, ideas, and chats on the topic.</p><h3>Special Thanks</h3><p>I am grateful to <a href="https://www.linkedin.com/in/rebeccaw1/"><strong>Rebecca Wirfs-Brock</strong></a> and <a href="https://www.linkedin.com/in/austin-chadwick-3a58151a4/"><strong>Austin Chadwick</strong></a> for their invaluable feedback on this guide.</p><p>[1] <a href="https://www.agilealliance.org/wp-content/uploads/2015/12/ExperienceReport.2014.Zuill_.pdf"><strong>Mob Programming — A Whole Team Approach</strong></a>, 2014, <a href="https://www.linkedin.com/in/woodyzuill/">Woody Zuill</a><br>[2] <a href="https://agilealliance.org/wp-content/uploads/2017/01/Mob-Programming-My-first-team.pdf"><strong>Mob Programming — My First Team</strong></a>, 2015, <a href="https://www.linkedin.com/in/jasonkerney/">Jason Kerney</a><br>[3] <a href="https://www.agilealliance.org/wp-content/uploads/2017/01/Mob_Programming_for-the-Introverted.pdf"><strong>Mob Programming for the Introverted</strong></a>, 2016, <a href="https://www.linkedin.com/in/aaron-griffith-1b365416/">Aaron Griffith</a><br>[4] <a href="https://www.agilealliance.org/wp-content/uploads/2017/02/GrowingTheMob.pdf"><strong>Growing the Mob</strong></a>, 2017, <a href="https://www.linkedin.com/in/chris-lucian/">Chris Lucian</a><br>[5] <a href="https://softwareteaming.com/"><strong>Software Teaming</strong></a>, 2022, <a href="https://www.linkedin.com/in/woodyzuill/">Woody Zuill</a>, <a href="https://www.linkedin.com/in/jkmeadows/">Kevin Meadows</a><br>[6] <a href="https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf"><strong>Scaling Agile @ Spotify</strong></a>, 2012, <a href="https://www.linkedin.com/in/hkniberg/">Henrik Kniberg</a>, <a href="https://www.linkedin.com/in/aivarsson/">Anders Ivarsson</a><br>[7] <strong>Chapter 28: Mob Programming and the Transition to XP</strong>, 2003, <a href="https://www.linkedin.com/in/moseshohman/">Moses Hohman</a>, <a href="https://www.linkedin.com/in/andy-slocum-4796204/">Andrew Slocum</a><br>[8] <a href="https://books.google.de/books/about/Extreme_Programming_Perspectives.html?id=ZqNQAAAAMAAJ&amp;redir_esc=y"><strong>Extreme Programming Perspectives</strong></a>, 2003, <a href="https://www.linkedin.com/in/michele-marchesi-9b35151/">Michele Marchesi</a>, <a href="https://www.linkedin.com/in/giancarlosucci/">Giancarlo Succi</a>, <a href="https://www.linkedin.com/in/don-wells-93a7585/">Don Wells</a>, <a href="https://www.linkedin.com/in/laurieawilliams/">Laurie Williams</a><br>[9] <a href="https://books.google.de/books/about/Teaming.html?id=5dZYEAAAQBAJ"><strong>Teaming</strong></a>, 2012, <a href="https://en.wikipedia.org/wiki/Amy_Edmondson">Amy Edmondson</a><br>[10] <a href="https://www.youtube.com/watch?v=Z5x5nYXBpis"><strong>What Mob Programming is NOT</strong></a>, 2024, <a href="https://www.linkedin.com/in/austin-chadwick-3a58151a4/">Austin Chadwick</a></p><h3>Literature</h3><p>The original experience reports from the pioneering team at <em>Hunter Industries, Inc.:</em></p><ul><li><a href="https://agilealliance.org/resources/experience-reports/mob-programming-agile2014/"><strong>Mob Programming — A Whole Team Approach</strong></a>, 2014, <a href="https://www.linkedin.com/in/woodyzuill/">Woody Zuill</a></li><li><a href="https://agilealliance.org/resources/experience-reports/mob-programming-my-first-team/"><strong>Mob Programming — My First Team</strong></a>, 2015, <a href="https://www.linkedin.com/in/jasonkerney/">Jason Kerney</a></li><li><a href="https://agilealliance.org/resources/experience-reports/mob-programming-for-the-introverted/"><strong>Mob Programming for the Introverted</strong></a>, 2016, <a href="https://www.linkedin.com/in/aaron-griffith-1b365416/">Aaron Griffith</a></li><li><a href="https://agilealliance.org/resources/experience-reports/growing-the-mob/"><strong>Growing the Mob</strong></a>, 2017, <a href="https://www.linkedin.com/in/chris-lucian/">Chris Lucian</a></li></ul><p>More experience reports by other teams:</p><ul><li><a href="https://agilealliance.org/resources/experience-reports/the-surprisingly-inclusive-benefits-of-mob-programming/"><strong>The Surprisingly Inclusive Benefits of Mob Programming</strong></a>, 2018, <a href="https://www.linkedin.com/in/sal-freudenberg-3ba149329/">Sal Freudenberg</a>, <a href="https://www.linkedin.com/in/mattwynne/">Matt Wynne</a></li><li><a href="https://agilealliance.org/resources/experience-reports/experimenting-with-mob-programming/"><strong>Experimenting with Mob-Programming</strong></a>, 2018, Amr Noaman Abdel Hamid</li><li><a href="https://agilealliance.org/resources/experience-reports/harvesting-mob-programming-patterns-observing-how-we-work/"><strong>Harvesting Mob Programming Patterns</strong></a>, 2019, Michael Keeling, Joe Runde</li><li><a href="https://agilealliance.org/resources/experience-reports/joining-the-mob-at-clearlink/"><strong>Joining the Mob at Clearlink</strong></a>, 2019, Torrey Powell, Craig Anslow</li><li><a href="https://agilealliance.org/resources/experience-reports/one-year-of-remote-mob-programming/"><strong>One Year of Remote Mob Programming</strong></a>, 2021, <a href="https://www.linkedin.com/in/jonathan-m-turner/">Jonathan Turner</a></li></ul><p>Articles on Mob Programming or related topics:</p><ul><li><a href="https://mobprogramming.org/"><strong>MobProgramming.org</strong></a></li><li>Woody Zuill’s <a href="https://zuill.us/WoodyZuill/"><strong>Life, Liberty, and the Pursuit of Agility</strong></a></li><li>Modern Agile’s <a href="https://modernagile.org/#cheatsheets"><strong>Ensemble Programming</strong></a> Cheat Sheet</li></ul><p>Starting from 2018, books on the topic were authored:</p><ul><li><a href="https://pragprog.com/titles/mpmob/code-with-the-wisdom-of-the-crowd/"><strong>Code with the Wisdom of the Crowd</strong></a>, 2018, <a href="http://markpearl.co.za/">Mark Pearl</a></li><li><a href="https://www.mobprogrammingguidebook.com/"><strong>The Mob Programming Guidebook</strong></a>, 2018, <a href="https://maaretp.com/">Maaret Pyhäjärvi</a>, <a href="https://www.linkedin.com/in/llewellynfalco">Llewellyn Falco</a></li><li><a href="https://www.remotemobprogramming.org/"><strong>Remote Mob Programming</strong></a>, 2020, <a href="https://twitter.com/simonharrer">Simon Harrer</a>, <a href="https://twitter.com/jochen_christ">Jochen Christ</a>, <a href="https://twitter.com/Waterback">Martin Huber</a></li><li><a href="https://ensembleprogramming.xyz/"><strong>Ensemble Programming Guidebook</strong></a>, 2021, <a href="https://maaretp.com/">Maaret Pyhäjärvi</a></li><li><a href="https://softwareteaming.com/"><strong>Software Teaming</strong></a>, 2021, 2022, <a href="https://www.linkedin.com/in/woodyzuill/">Woody Zuill</a>, <a href="https://www.linkedin.com/in/jkmeadows/">Kevin Meadows</a></li></ul><p>Related books:</p><ul><li><a href="https://leanpub.com/codingdojohandbook"><strong>The Coding Dojo Handbook</strong></a>, 2013, <a href="https://www.linkedin.com/in/emilybache/">Emily Bache</a></li></ul><h3>Videos</h3><ul><li>Woody Zuill’s <a href="https://www.youtube.com/watch?v=p_pvslS4gEI"><strong>A Day of Mob Programming</strong></a>, 2012</li><li>Mark Pearl’s <a href="https://www.youtube.com/watch?v=Ev7uus12HRY"><strong>Mob Programming Time Lapse</strong></a>, 2015</li><li><a href="https://www.youtube.com/watch?v=dVqUcNKVbYg"><strong>Multi-Team Mob Programming Time Lapse</strong></a>, 2016</li><li>Austin Chadwick’s <a href="https://www.youtube.com/watch?v=Z5x5nYXBpis"><strong>What Mob Programming is NOT</strong></a>, 2024</li><li><a href="https://www.linkedin.com/in/chris-lucian/">Chris Lucian</a> and <a href="https://www.linkedin.com/in/austin-chadwick-3a58151a4/">Austin Chadwick</a>’s <a href="https://www.youtube.com/@mobmentalityshow"><strong>Mob Mentality Show</strong></a></li><li><a href="https://www.linkedin.com/in/woodyzuill/">Woody Zuill</a>’s talks <a href="https://www.youtube.com/playlist?list=PLMytyWxm7htcm6cAbtRjK-k_5PeZ7F-TT"><strong>on YouTube</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21a574ba46e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hitchhiker’s Guide to Hexiverse — Modern Synthesis]]></title>
            <link>https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-modern-synthesis-b1e3b61ba3c1?source=rss-c98461c29fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1e3b61ba3c1</guid>
            <category><![CDATA[extreme-programming]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Aria Omidvar]]></dc:creator>
            <pubDate>Mon, 10 Nov 2025 19:25:57 GMT</pubDate>
            <atom:updated>2026-03-10T09:02:09.723Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Hitchhiker’s Guide to Hexiverse — Modern Synthesis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JT5D46NN2HFl8SMJ_a8-PQ.png" /><figcaption><strong>Modern Synthesis</strong> from <strong>Hexiverse</strong></figcaption></figure><p>In this article, I suggest a Hexi set for <strong>Modern Synthesis</strong> and expand on each Hexi. The corresponding Hexi set can be found <a href="https://miro.com/app/board/uXjVKv84GGU=/?moveToWidget=3458764645867138701&amp;cot=14"><strong>here</strong></a>.</p><h3>Seek the Source</h3><p>This Hexi set is based on <a href="https://www.geepawhill.org/"><strong>Michael “GeePaw” Hill</strong></a>’s work and approach to software development, teamwork, and leading change. Everything is based on his articles, podcast, and talks available on his website and YouTube.</p><p>I hope the Hexi set and this companion guide help as an introduction to GeePaw’s approach and to integrate his wonderful wisdom into the Hexiverse. However, what I have included in this guide is but a glimpse of his wit and wisdom. I highly recommend readers and users to follow the links and consume his full content at the source. <a href="https://www.geepawhill.org/tag/podcast/"><strong>PawCast</strong></a>, his podcast, is simply a gem.</p><h3>Not a Methodology</h3><blockquote>Hence the endless flood of brand-name software development “methodologies”, which exist in more than just our trade, I feel sure, but are absolutely ubiquitous in the geek trade.<br>Oh. Did I mention my own brand-name methodology, System Utilizing Complex Knowledge-Efficient Reasoning, or SUCKER?<br>Call now, operators are standing by.</blockquote><p>As you can clearly see, Modern Synthesis is not a methodology. If I dare to define it, I would say it is what GeePaw has learned throughout his decades in the <em>trade</em> and promotes as helpful ways and suggestions for others to consider.</p><p>Read further: <a href="https://www.geepawhill.org/2024/02/23/optimize-for-our-humans/"><strong>Optimize for Our Humans</strong></a>, <a href="https://www.geepawhill.org/2021/04/27/on-agile-methods/"><strong>On Agile Methods</strong></a></p><h3>Inter-related &amp; Fractal</h3><p>Many of the concepts and practices mentioned here are related to one another, and their <em>interplay</em> is essential. Taking one or two pieces out and adopting or applying them in isolation may bring some partial gains only.</p><p>Another characteristic of Modern Synthesis’s elements is the <em>fractality</em> of some of its concepts; that they apply to several orders of subjects. This is less visible in this guide but hard to miss in GeePaw’s articles, podcasts, and talks.</p><h3>Community of Kindness &amp; Creativity</h3><p>GeePaw states that in his attempt to reframe the trade, one of his goals is the <em>“</em><strong><em>development of community </em></strong><em>— active, dynamic, mutually beneficial, and healthy relationships between human beings”</em>.</p><p><strong>Community</strong> is a long-lost concept in our modern workplace. In recent years, there has been a return to it mainly through the concept of <em>Community of Practice</em>, but most such adoptions are more often than not half-hearted and shallow.</p><p><strong>Kindness</strong> is yet another forgotten value. The all-encompassing, vague, and often empty <em>“nice”</em> has replaced it.</p><p><strong>Creativity</strong> is also not exactly associated with software development. It is mistaken to belong to designers and artistic work in general.</p><p>GeePaw’s <strong>Community of Kindness &amp; Creativity</strong> is a much-needed return to the forgotten <em>human</em> and <em>social</em> aspects of knowledge work.</p><p>See also: <strong>Golden Rules</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h3>Mentorship</h3><blockquote>Making <strong>mentoring</strong> and <strong>being mentored</strong> the dominant occupation of our trade.</blockquote><p><strong>Mentorship</strong> is yet another lost art in our industry, and most knowledge work. A look at the job ads reveals a lot. We often seek ready-made, cooked, baked, and seasoned professionals who will boost the performance of our organizations upon their arrival. We do not evaluate individuals on their contributions to the development of their peers, and we do not hire with mentorship in mind.</p><p>GeePaw’s bold intention of turning mentorship into the <em>dominant occupation of our trade</em> is as painfully needed as it sounds idealistic.</p><p>Related patterns: <strong>Continuous Collective Learning &amp; Practice</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h3>Whole Person</h3><p>Normalizing the <strong>Whole Geek</strong> or <strong>Whole Maker</strong>.</p><blockquote>By “<strong>geek</strong>”, I mean one who is highly <strong>creative</strong>, highly <strong>technical</strong>, and highly desirous of being both. In particular, “geek” is not a synonym for “coder”, but for “<strong>maker</strong>”.<br>None of the people I know are just one thing. All of them are many things. When I say “<strong>bring the whole geek</strong>”, what I am saying is that makers make best when they can bring to bear many of the things they are, not just one.</blockquote><p>This notion is also drawing more attention in recent years, particularly due to the momentum of the <a href="https://en.wikipedia.org/wiki/Frithjof_Bergmann#New_Work">New Work</a> movement, but we are still miles away from comprehending it, let alone actualizing it.</p><p>Read further: <a href="https://www.geepawhill.org/category/the-whole-geek/"><strong>The Whole Geek</strong> Series</a></p><h3>RAMPS</h3><p><strong>Rhythm-Autonomy-Mastery-Purpose-Safety (RAMPS)</strong> is a concept formalized by GeePaw that interprets Dan Pink’s <a href="https://en.wikipedia.org/wiki/Drive:_The_Surprising_Truth_About_What_Motivates_Us">Drive</a> in the context of software development and extends it further.</p><p>Read further: <a href="https://www.geepawhill.org/series/ramps/"><strong>RAMPS</strong> Series</a></p><p>Related patterns: <strong>Motivated Individuals</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h4><strong>Rhythm</strong></h4><blockquote>Sequences of alternating <strong>tension</strong> and <strong>release</strong>.<br>Getting a good distribution of <strong>“feels good”</strong> over time through cultivating <strong>awareness</strong>, <strong>openness</strong>, <strong>variety</strong>, <strong>human judgment</strong>, and <strong>experimentation</strong>.</blockquote><p>I find GeePaw’s <strong>Rhythm</strong> more nuanced than other notions pointing in the same direction, such as <em>Sustainable Pace</em>.</p><p>Related patterns: <strong>Sustainable Pace</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h4><strong>Autonomy</strong></h4><blockquote>Layout and interaction of obligation and activity.<br>Freedom to move in whatever way possible to get the job done. Comes with a <strong>trade-off</strong> that sometimes the agent will go off-road.<br>It’s the most <strong>overlooked</strong>. It <strong>drives</strong> the others of RMPS.<br>Essential in <strong>complex adaptive systems/environments</strong>.<br>Crucial for <strong>creativity</strong> and <strong>technicality</strong>.</blockquote><p>Related patterns: <strong>Self-Organizing Teams</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h4><strong>Mastery</strong></h4><blockquote>Centered around <strong>growth</strong>.<br>The feeling that my work is helping me grow.<br><strong>Growth</strong> is the most important thing rather than reaching absolute <strong>mastery</strong>.</blockquote><p>Related patterns: <strong>Continuous Collective Learning &amp; Practice</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4><strong>Purpose</strong></h4><blockquote>Value of <strong>service</strong><br>Service to a valued <strong>greater</strong>.<br>Gets us through the feels-bad phases of work.</blockquote><h4><strong>Safety</strong></h4><blockquote>Safety is the delicate, nuanced dance between who “I” am and who “we” are.<br>The feeling of being <strong>accepted</strong>, <strong>valued</strong>, and of <strong>belonging</strong>.<br>What I think and feel matters to these people.</blockquote><p>See also: <a href="https://en.wikipedia.org/wiki/Psychological_safety"><strong>Psychological Safety</strong></a></p><p>Related patterns: <strong>Safe to Learn</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h3>Leading Change</h3><p>GeePaw’s fundamental strategies for <em>leading change</em>:</p><ul><li>Take <strong>many more much smaller steps<br></strong>Further explained below</li><li><strong>Optimize for the humans</strong><br>We will never get the change we want if it isn’t fitted to our humans.</li><li><strong>Make Change Normal<br></strong>See Development as Change below</li></ul><p>Read further: <a href="https://www.geepawhill.org/series/leading-technical-change/"><strong>Leading Technical Change</strong> Series</a></p><h3>Change Harvesting</h3><p>A self-feeding cycle of making a <strong>change</strong>, harvesting its <strong>value</strong>, and using that value to make the <strong>next change</strong>.</p><p>The five aspects of Change Harvesting listed below extend and reinforce each other.</p><h4><strong>Human</strong></h4><p>rather than <em>procedural</em></p><p>We will never get the change we want if it isn’t fitted to our humans.</p><ul><li>fostering <strong>direct peer-to-peer social interactions</strong></li><li><strong>Comprehensible</strong></li><li><strong>Doable</strong> today and <strong>Done</strong> tomorrow</li></ul><p>Read more: <a href="https://www.geepawhill.org/2024/02/23/optimize-for-our-humans/"><strong>Optimize for Our Humans</strong></a></p><h4><strong>Local</strong></h4><p>rather than <em>global</em></p><p>Local and near to our <strong>minds</strong>, <strong>situation</strong>, <strong>ability</strong>, and <strong>now</strong>. In other words, the <strong>smallest, nearest</strong> change with a <strong>detectable outcome</strong>.</p><h4><strong>Oriented</strong></h4><p>rather than <em>precise </em>/<em> aimed</em></p><p>It does not need to be perfectly aligned as long as it is not going backward (in relation to the global goals).</p><p>With a <em>bias for action</em>: First act, then look.</p><h4><strong>Taken</strong></h4><p>rather than <em>given</em></p><p>Working with what is already there</p><ul><li>from the <strong>inside</strong> rather than dictated</li><li>starts with the <strong>current state</strong></li><li>gradual &amp; sustainable</li></ul><p>Related patterns: <strong>Gradual Introduction &amp; Adoption</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4><strong>Iterative</strong></h4><p>rather than <em>final</em></p><ul><li>change, inspect, adapt (next change)</li><li>emphasizes <strong>changeability</strong></li></ul><p>User Stories, TDD, Refactoring, and Pair Programming manifest these five characteristics.</p><p>These characteristics apply to change on the software level as well as the team and organizational level (fractal).</p><h3>Rework Avoidance Theory (RAT)</h3><p>RAT is based on the <strong>illusion of efficiency</strong>. The <em>illusion of efficiency</em> suggests that the <strong>efficient</strong> way to create the software is a <strong>straight path</strong> with a <strong>clear endpoint</strong> from which we can work our way <em>backward</em> to where we are and break down the path into straight, <strong>predictable steps</strong>, resulting in the <strong>shortest distance</strong> possible.</p><p>RAT focuses solely on the <em>endpoint</em>, resulting in <strong>late validation</strong> and a <strong>longer time-to-market</strong> without any <strong>return-on-investment</strong> until final delivery. It is also prone to <strong><em>feature gluttony</em></strong> and <strong><em>gold plating</em></strong>.</p><p>The same hyper-rational, deterministic thinking behind RAT makes other assumptions, such as:</p><ul><li>Dividing the work based on <em>expertise</em>.</li><li>Ignoring <em>human nature</em>.<br>Humans need repetition!</li><li>Assuming a <strong>linear relation</strong> between the <strong>size</strong> of the <strong>effort</strong> and its <strong>difficulty</strong>. Whereas the larger the effort, the <em>larger-er</em> the difficulty!</li></ul><p>Read further: <a href="https://www.geepawhill.org/2020/07/17/the-rat-rework-avoidance-theory/"><strong>Rework Avoidance Theory</strong></a></p><p>Related patterns: <strong>Welcoming Change, Early &amp; Continuous Delivery of Value</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h3>Development as Change</h3><p>As a direct result of abandoning the <em>efficient path</em> explained in RAT, <strong>developing software</strong> can be reframed as <strong>changing software</strong>. This seems obvious and natural, yet going so far as to reframe development as change, changes how we think of and perceive everything in software development and product development in general.</p><p><strong>Control</strong>: You can not change what you do not <strong>own</strong>.</p><p><strong>Expression</strong>: You can not change what you do not <strong>understand</strong>.</p><p><strong>Confirmation</strong>: [INCOMPLETE]</p><p>Useful <strong>heuristics</strong> for change:</p><ul><li><strong>bias for action</strong></li><li>sort for <strong>step size</strong> over <strong>value differential</strong></li><li>create <strong>experiences</strong>, not <strong>arguments</strong>: show how the change improves things rather than arguing for it</li></ul><h3>Many More Much Smaller Steps (MMMSS)</h3><p>It is an antidote to Rework Avoidance.</p><p>Steps need to be:</p><ul><li><strong>Small</strong> enough</li><li><strong>Shippable</strong> on completion</li><li>Not to make things worse</li></ul><p>Assumes the actual change to be <strong>non-geometric</strong> and <strong>non-platonic</strong>.</p><p>Small steps have inherent intrinsic values such as <strong>reversability</strong>, <strong>interruptibility</strong>, <strong>steerability</strong>, <strong>grokkability</strong>, <strong>energizing rhythm</strong>, and <strong>target parallelism</strong>.</p><p>MMMSS has a <strong>fractal</strong> characteristic and can be applied to change at different levels: code, person, process, team, organization, trade, world.</p><p>Read further: <a href="https://www.geepawhill.org/series/many-more-much-smaller-steps/"><strong>Many More Much Smaller Steps</strong> Series</a></p><p>Related patterns: <strong>Micro-Increments</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-whole-parts-steps-915fb44eafa9">Whole-Parts-Steps</a>]</p><h3>Pull &amp; Swarm</h3><p>Pull a story, slice it thin, the whole team <strong>swarms</strong> on it (solos / pairs / mob), and <strong>ship</strong> it in less than <strong>two days</strong>.</p><p>These two-team-day steps do not necessarily need to deliver anything <strong>valuable</strong> to the customer as long as they are delivering <strong>value</strong>. Small steps have an inherent <strong>intrinsic value</strong> (explained above) even when they do not result in immediate <strong>extrinsic value</strong>.</p><p>Related patterns: <strong>Thin-Slicing</strong>, <strong>Micro-increments</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-whole-parts-steps-915fb44eafa9">Whole-Parts-Steps</a>]</p><h3>Other Practices</h3><p><strong>TDD</strong> with <strong>Micro-tests</strong>: from test to finish under an hour.</p><p><strong>Refactoring</strong>, <strong>CI/CD</strong> with <strong>Trunk-Based Development</strong></p><p><strong>Swarming</strong>, <strong>Pair Programming</strong>, <strong>Mob Programming</strong>, <strong>Retrospectives</strong></p><p>Related patterns: <strong>Technical Excellence</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h4>Tooling</h4><blockquote>Give me six hours to chop down a tree and I will spend the first four sharpening the axe.</blockquote><p>As suggested in this age-old wisdom, having the proper tool can make a significant difference in how teams develop.</p><h3>Last Word</h3><p>It is hard to get a crisp image of what Modern Synthesis is because it feels like it lacks <em>structure</em> and <em>formalization</em>. It feels <em>raw</em>, <em>organic</em>, <em>natural</em>; it feels <em>wild</em> in its best sense. I embrace Modern Synthesis’s lack of <em>symmetry</em> and <em>order</em>. Things that look too symmetrical and orderly often lack <em>real-world</em> application.</p><h3>Your Feedback</h3><p>If you have comments or suggestions, please do not hesitate to express them here in the comments or message me directly on <a href="https://www.linkedin.com/in/aria-omidvar/">LinkedIn</a>. I welcome all kinds of commentary, ideas, and chats on the topic.</p><h3>All &amp; Everything GeePaw</h3><ul><li><a href="https://www.geepawhill.org/"><strong>GeePawHill.org</strong></a></li></ul><h3>Videos</h3><ul><li><a href="https://www.youtube.com/watch?v=Z7q6YX8n920"><strong>Changing Changing Software</strong></a>, 2020, Beauty in Code Conference</li><li><a href="https://www.youtube.com/watch?v=WYK4kbrmm84"><strong>More Smaller Steps</strong></a>, 2020, Jersey City Java User Group</li><li><a href="https://www.youtube.com/watch?v=9HMd4n9jnJ8"><strong>This Doesn’t Add Up: Failing at Change, and How to Try Different, Not Harder</strong></a>, 2021, Emerging Technologies for the Enterprise Conference</li><li><a href="https://www.youtube.com/watch?v=1mOs1_pvS9A"><strong>Want More Value Faster? Take Many More Much Smaller Steps</strong></a>, 2021, TDD Conference</li><li><a href="https://www.youtube.com/watch?v=FLusbyBpugs"><strong>Take Many More Much Smaller Steps</strong></a>, 2021, PMI Washington DC Chapter</li></ul><h3>Courses</h3><ul><li><a href="https://www.geepawhill.org/courses/leading-technical-change/"><strong>Leading Technical Change</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1e3b61ba3c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hitchhiker’s Guide to Hexiverse — Whole-Parts-Steps]]></title>
            <link>https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-whole-parts-steps-915fb44eafa9?source=rss-c98461c29fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/915fb44eafa9</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[estimations]]></category>
            <category><![CDATA[use-cases]]></category>
            <category><![CDATA[user-story-mapping]]></category>
            <dc:creator><![CDATA[Aria Omidvar]]></dc:creator>
            <pubDate>Thu, 30 Oct 2025 10:39:22 GMT</pubDate>
            <atom:updated>2026-02-12T12:57:47.857Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Hitchhiker’s Guide to Hexiverse — Whole-Parts-Steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eERPmRVyKjnG22V622EAdQ.png" /><figcaption><strong>Whole-Parts-Steps</strong> from <strong>Hexiverse</strong></figcaption></figure><p>In this article, I suggest a Hexi set for a collection of practices and techniques I came to call <strong>Whole-Parts-Steps</strong>. The corresponding Hexi set can be found <a href="https://miro.com/app/board/uXjVKv84GGU=/?moveToWidget=3458764616505192660&amp;cot=14"><strong>here</strong></a>.</p><h3>Whole-Parts-Steps</h3><p>This Hexi set focuses on something that does not have a name, is used by all teams, Agile or else, in one way or another, and is the least detected or addressed source of pain of nearly all teams I have seen or worked with. What is our next thing to do? How do we break it down into doable chunks? How do we deliver them? When trying to answer these questions, we often think in terms of <em>stories</em>, <em>estimation</em>, and <em>iteration</em>. They are interrelated and definitely part of the answer, but treating them is only treating the symptoms.</p><p>The main objective of <em>Whole-Parts-Steps</em> is to provide teams with tools to <em>comprehend</em> the larger picture and the <em>why</em> of their efforts, <em>identify</em> <em>what </em>needs to be done, and <em>deliver</em> it in small increments. <em>Whole-Parts-Steps</em> could very well be the linchpin of all the methods and practices at the team level.</p><p><strong>User Story Maps</strong> and <strong>Use Cases</strong> are powerful tools for drawing the <em>big picture</em> of the product, while <strong>Product Backlogs</strong> are still the most common. <strong>User Stories</strong> and its derivatives are suited for identifying <em>discrete pieces of work</em> that eventually fill the big picture. <strong>Increments</strong> and <strong>Micro-Increments</strong> are two approaches to delivering <em>valuable slices</em> (read pieces) of the product as early as possible.</p><h3>WHOLE</h3><blockquote>What are we building?</blockquote><blockquote>Who are we building for?</blockquote><blockquote>What problems are we trying to solve?</blockquote><p><strong>User Story Mapping</strong> is a wonderful way to understand who the users are, what their needs are, and what a solution to their needs can look like. A somewhat similar method is <strong>Use Cases</strong>.</p><p>Both USMs and UCs provide a comfortable level of <strong>abstraction</strong> needed for a <strong>meaningful big picture</strong>. They are <strong>user-facing</strong> and <strong>user-centric.</strong> They are <strong>persistent</strong> and have a long lifespan, although subject to revision and change.</p><h3>User Story Maps</h3><p>User Story Mapping and User Story Maps are often attributed to <a href="https://www.linkedin.com/in/productdesigncoach/">Jeff Patton</a>. He claims to have coined the name but believes that other practitioners have been using very similar techniques, so he prefers to call it a <em>pattern</em> that he too stumbled on rather than his own creation.</p><p>USMs explore the user’s <strong>journey through the product</strong> by building a two-dimensional model. In simpler words, USMs tell the <strong>story</strong> of what people <strong>do</strong> with the software.</p><p>Because of its structure with two dimensions, a USM provides a comprehensible, large picture for everyone. Its collaborative generation process also guarantees effective discovery of users’ needs and pains.</p><p>To understand USMs and their advantages over Product Backlogs, read <a href="https://jpattonassociates.com/the-new-backlog/"><strong>The New User Story Backlog is a Map</strong></a>.<br>For a quick start, check out Jeff Patton’s <a href="https://jpattonassociates.com/story-mapping/"><strong>User Story Mapping Resources</strong></a>.</p><h3>Use Cases</h3><p><a href="https://en.wikipedia.org/wiki/Use_case"><strong>Use Cases</strong></a> originate from <a href="https://en.wikipedia.org/wiki/Ivar_Jacobson">Ivar Jacobson</a>, one of the pioneers of Software Engineering. Others have further developed UCs, including Agile’s own <a href="https://en.wikipedia.org/wiki/Alistair_Cockburn">Alistair Cockburn</a>. Due to their association with <em>heavyweight methods</em>, UCs fell out of favor among Agile circles. Nevertheless, UCs are a powerful tool for understanding <strong>who</strong> will use a product and <strong>how</strong> they will use it. They shift the focus to what the <strong>users</strong> need to <strong>do</strong> as opposed to starting with what needs to be built. They are perfect for <strong>discovery</strong> but also useful for <strong>design</strong> and <strong>validation</strong> (testing).</p><p>UCs provide a methodical approach to explore and capture all the ways of <strong>using</strong> a system to achieve a particular <strong>goal</strong> of a particular <strong>actor</strong>. A UC may contain a collection of <strong>scenarios of use</strong> that are folded together in a certain way that tells a <strong>story</strong>, which is easy to read. It contains multiple <strong>cases</strong> based on successes or failures (happy scenario and alternative scenarios), along with <strong>surrounding logic</strong> like business rules and quality attributes, plus <strong>preconditions</strong>, <strong>postconditions</strong>, and <strong>exceptions</strong>.</p><p>UCs are best <strong>not very detailed</strong>, so everyone around the organization bothers to read them. As a result, they can <strong>unify</strong> the whole organization in the effort.</p><p>UCs can be used for slicing the whole effort into meaningful, useful parts to be developed. For instance, the first obvious slice is the <em>happy scenario</em>.</p><p>See also: <a href="https://wiki.c2.com/?UseCase"><strong>Use Case</strong></a>, <a href="https://en.wikipedia.org/wiki/Behavior-driven_development"><strong>Behavior-Driven Development (BDD)</strong></a>, <a href="https://en.wikipedia.org/wiki/Test_case_(software)"><strong>Test Case</strong></a>, <a href="https://en.wikipedia.org/wiki/Acceptance_testing"><strong>Acceptance Testing</strong></a></p><h3>Product Backlog</h3><p><a href="https://en.wikipedia.org/wiki/Product_backlog"><strong>Product Backlogs</strong></a> are the most widely used and the seemingly simplest of the tools helping us grasp the whole of a product or project. PBLs’ simplicity makes them the most preferred tool for prioritizing work.</p><p>See also: <a href="https://www.scrum.org/resources/ordered-not-prioritized"><strong>Ordered Not Prioritized</strong></a></p><h3>PARTS</h3><blockquote>What is our next step in solving the users’ needs?</blockquote><blockquote>What piece of work should we do next?</blockquote><p>These questions are often addressed by the <strong>Product Backlog</strong>. The topmost <strong>Product Backlog Items</strong> on the PBL have the highest priority. PBIs are often <strong>User Stories</strong>.</p><h3>User Stories</h3><blockquote>“Tell me the stories of what the system will do. Write down the name of the story and a paragraph or two.”</blockquote><blockquote>— Kent Beck</blockquote><p><a href="https://en.wikipedia.org/wiki/User_story"><strong>User Stories</strong></a> is a lightweight, communicative method that enables a conversation between the users of the product and its creators. In this conversation, their needs, ideas, and opinions are discussed so the creators know <em>what</em> needs to be built and <em>why</em>.</p><p>Originally, USs were a solution to a problem the original Extreme Programmers were facing in the C3 project. However, the practice remained popular and was interpreted in different ways for different purposes. The paper format with a brief text on it to ignite a conversation with the on-site customer is rarely practiced anymore. On the other hand, <a href="https://en.wikipedia.org/wiki/Mike_Cohn">Mike Cohn</a>’s version of USs, with its renowned <em>“As a &lt; type of user &gt;, I want &lt; some goal &gt; so that &lt; some reason &gt;”</em> format, became the most popular one.</p><p>USs are <strong>detailed</strong>, <strong>implementation-centric</strong>, and have a <strong>limited lifecycle</strong>.</p><p>Related patterns: <strong>Stories</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">HGIH — XP</a>]</p><p>See also: <a href="https://wiki.c2.com/?UserStory"><strong>User Story</strong></a>, <a href="https://wiki.c2.com/?UserStoryAndUseCaseComparison"><strong>User Story And Use Case Comparison</strong></a>, <a href="https://ronjeffries.com/xprog/articles/expcardconversationconfirmation/"><strong>Card Conversation Confirmation</strong></a>, <a href="https://ronjeffries.com/articles/019-01ff/3cs-revisited/"><strong>Three-C’s Revisited</strong></a>, <a href="https://ronjeffries.com/articles/019-01ff/stories-3cs-yet-again/"><strong>Stories and the Three C’s — Revisited Yet Again</strong></a>, <a href="https://ronjeffries.com/xprog/blog/how-should-user-stories-be-written/"><strong>How should user stories be written?</strong></a></p><h3>Other Pieces of Work</h3><p>Sometimes teams need to define pieces of work that need to be done but do not quite fit the above-mentioned format. These can be <strong>bug fixes</strong>, <strong>performance improvements</strong>, <strong>technical requirements</strong> like creating a monitoring system, upgrading source code, or many other examples that are not features or directly and obviously impacting the users. For these pieces of work, any format that satisfies the needs of teams can be created.</p><p>See also: <a href="https://www.mountaingoatsoftware.com/blog/spikes"><strong>Spikes</strong></a></p><h3>STEPS</h3><blockquote>In what manner do we develop and deliver this next piece of work?</blockquote><p>Once we figure out <em>what piece of work we should do next</em>, the second challenge appears: <em>how do we deliver it?</em> Or more precisely, <em>how can we deliver this earlier in the smallest yet valuable pieces?</em></p><p>Scrum suggests <em>Sprints</em> of 1 to 4 weeks, and XP suggests weekly <em>Cycles</em>. For these 1 to 4-week <em>iterations</em>, the work needs to be <em>estimated</em> to be delivered within that timeframe. Estimates have an inherent difficulty: the larger the work, the less accurately they can be estimated.</p><p>Some practitioners, including <strong>Ron Jeffries</strong> &amp; <strong>Chet Hendrickson</strong>, <strong>Woody Zuill</strong>, <strong>Mike “GeePaw” Hill</strong>, and <strong>Alistair Cockburn</strong>, suggest <em>micro-increments</em>. These are very thin slices of work that can be delivered optimally in one day and no longer than two days. These micro-increments remove the need for <em>estimation</em> and replace it with the practice of <em>thin slicing</em>.</p><h3>Increments</h3><p>After capturing the big picture and defining the smaller parts, it is time to develop <strong>a portion of the whole</strong> and deliver it to the customer, so we can learn how well we have understood their needs as well as our own production capabilities.</p><p>Agile methods like Extreme Programming and Scrum follow the <strong>iterative</strong> approach. Each <strong>iteration</strong> must result in at least one <strong>increment</strong>. These iterations can be 1 week to 1 month long. These days, most teams follow a two-week iteration cycle.</p><p>Related patterns: <strong>Increment</strong>, <strong>Definition of Done</strong>, <strong>Sprint</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">HGIH — Scrum</a>], <strong>Weekly Cycle</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">HGIH — XP</a>]</p><h4>Planning &amp; Estimation</h4><p>One of the results of these iterations is that teams need to plan what they aim to deliver within that iteration. Such <strong>planning</strong> often relies on <strong>estimation</strong>, where PBIs are estimated for effort and assigned to the upcoming iteration. There are alternative methods to estimation, like <strong>same-sizing</strong>. Estimation remains a controversial subject and a place of heated disputes. And right-sizing has not gained favor.</p><p>Iteration planning and estimation techniques are widely explored and have many references and guides. In this guide, I focus on micro-increments since I find them undervalued and a wonderful solution to the problems that many teams face.</p><p>Related patterns: <strong>Sprint Planning</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">HGIH — Scrum</a>]</p><p>See also: <a href="https://ronjeffries.com/articles/019-01ff/story-points/Index.html"><strong>Story Points Revisited</strong></a></p><h3>Micro-Increments</h3><p>An alternative approach to the conventional 1-or-2-week iterations and the planning and estimation that come with them is very small iterations, or <strong>micro-iterations</strong> that result in very small increments or <strong>micro-increments</strong>.</p><p>The idea behind micro-increments is that the concept of iterative development can be applied to each iteration as well. This is like applying iterative development in a fractal manner.</p><p>Anyone in their right mind would ask, <em>“But why?!”</em>. Essentially, micro-increments shorten the feedback loop. They enable earlier feedback from the development process, solution viability, and stakeholders, even if on a smaller piece of functionality.</p><h4>Thin-slicing</h4><p>Micro-increments eliminate the need for <em>planning</em> and <em>estimation</em> by shortening iterations to a maximum of two days, but require teams to develop a new skill: Thin-slicing. A thin slice is a slice of the work that can be done optimally in less than a day, or in less than two days at most.</p><p>There are videos and articles where <strong>Ron Jeffries</strong> and <strong>Chet Hendrickson</strong> describe how they do one-day iterations resulting in micro-increments.</p><p><strong>Woody Zuill</strong> advocates a similar approach in <strong>Software Teaming</strong> (AKA Mob Programming and Ensemble Programming), casually called <em>“Thinnest Slices: A distinct, recognizable, understandable, cohesive (belong together), and potentially valuable chunk of stuff that can be decoupled, worked on, deployed, and provided feedback.”</em></p><p><strong>Mike “GeePaw” Hill</strong> has a method he calls <a href="https://www.geepawhill.org/series/many-more-much-smaller-steps/"><strong>Many More Much Smaller Steps (MMMSS)</strong></a>, which is the best formalization of micro-increments I have seen so far. For the execution of these micro-iterations, he suggests a technique called <a href="https://www.geepawhill.org/2020/06/26/pull-swarm/"><strong>Pull &amp; Swarm</strong></a> that gets pretty close to Software Teaming.</p><p>Alistair Cockburn‘s <strong>Elephant Carpaccio</strong> is an exercise for teams to practice thin-slicing and micro-increments.</p><p>See also: <a href="https://ronjeffries.com/xprog/articles/getting-small-stories/"><strong>Getting Small Stories</strong></a>, <a href="https://ronjeffries.com/articles/015-jul/slicing/"><strong>Slicing Estimation Trimming</strong></a>, <a href="https://xp123.com/invest-in-good-stories-and-smart-tasks/"><strong>INVEST in Good Stories and SMART Tasks</strong></a>, <a href="https://www.mountaingoatsoftware.com/blog/five-simple-but-powerful-ways-to-split-user-stories"><strong>Spike, Paths, Interfaces, Data, Rules (SPIDR)</strong></a>, <a href="https://www.mountaingoatsoftware.com/blog/five-story-splitting-mistakes-and-how-to-stop-making-them"><strong>Five Story-Splitting Mistakes</strong></a>, <a href="https://neilkillick.medium.com/my-slicing-heuristic-concept-explained-810ee70b311e"><strong>Slicing Heuristic Concept Explained</strong></a>, <a href="https://www.geepawhill.org/2020/07/17/the-rat-rework-avoidance-theory/"><strong>Rework Avoidance Theory (RAT)</strong></a></p><h4>#NoEstimates</h4><p>The root of micro-increments is somewhat inseparable from the #NoEstimates movement initiated by Woody Zuill and championed by Neil Killick, Vasco Duarte, and others. Keep in mind that the individual approaches to NoEstimates differ from each other and sometimes by a great distance. Nevertheless, the contents on the topic are impossible to ignore.</p><p>See also: Woody Zuill’s <a href="https://zuill.us/WoodyZuill/beyond-estimates/"><strong>articles</strong></a>, Ron Jeffries’s <a href="https://ronjeffries.com/categories/all-articles/index.html"><strong>articles</strong></a>, Vasco Duarte’s <a href="https://softwaredevelopmenttoday.com/noestimates/"><strong>resources on #NoEstimates</strong></a>, Neil Killick’s <a href="https://neilkillick.medium.com/"><strong>Medium articles</strong></a>, Allen Holub’s <a href="https://holub.com/noestimates-an-introduction/"><strong>#NoEstimates, An Introduction.</strong></a></p><h3>Micro-increments and Teaming</h3><p>In the previous section, I claimed that teams that switch from <strong>increments</strong> to <strong>micro-increments</strong> need to learn <strong>thin-slicing</strong>. Although it is true, it is not always sufficient. Most Agile (read Scrum) teams follow a <strong>Scatter-Gather</strong> pattern that has a lower grade of collaboration. Scatter-Gather is possible with 2-week iterations, but is nearly impossible with 1-to-2-day micro-iterations. With micro-iterations, higher degrees of collaboration are needed for the work to go from start to finish within a day or two. This often means <strong>pair programming</strong>, <strong>swarming</strong>, <strong>mob programming</strong>, or a blend of all.</p><p>See also: Tim Ottinger’s <a href="https://www.industriallogic.com/blog/scatter-gather/"><strong>Scatter-Gather</strong></a>, GeePaw Hill’s <a href="https://www.geepawhill.org/2020/06/26/pull-swarm/"><strong>Pull &amp; Swarm</strong></a></p><h3>Increments, Micro-increments, and Kanban</h3><p>In the above sections, I coupled increments with iterations and micro-increments with micro-iterations. However, increments or micro-increments do not need to be delivered iteratively. They can also be delivered through a <strong>continuous flow of value</strong>, often attributed to <strong>Kanban</strong>, but also a characteristic of <strong>Lean Software Development</strong>.</p><h3>Your Feedback</h3><p>If you have comments or suggestions, please do not hesitate to express them here in the comments or message me directly on <a href="https://www.linkedin.com/in/aria-omidvar/">LinkedIn</a>. I welcome all kinds of commentary, ideas, and chats on the topic.</p><h3>Literature</h3><ul><li><a href="https://books.google.de/books/about/Writing_Effective_Use_Cases.html?id=TUZsAQAAQBAJ"><strong>Writing Effective Use Cases</strong></a>, 2000, <a href="https://en.wikipedia.org/wiki/Alistair_Cockburn">Alistair Cockburn</a></li><li><a href="https://www.oreilly.com/library/view/patterns-for-effective/0201721848/"><strong>Patterns for Effective Use Cases</strong></a>, 2002, <a href="https://www.linkedin.com/in/steveadolph/">Steve Adolph</a>, <a href="https://www.linkedin.com/in/paul-bramble-46b2a7/">Paul Bramble</a>, with <a href="https://en.wikipedia.org/wiki/Alistair_Cockburn">Alistair Cockburn</a>, <a href="https://www.linkedin.com/in/andypols/">Andy Pols</a></li><li><a href="https://www.oreilly.com/library/view/use-case-modeling/0201709139/"><strong>Use Case Modeling</strong></a>, 2002, <a href="https://www.linkedin.com/in/kurt-bittner-882b203/">Kurt Bittner</a>, <a href="https://www.linkedin.com/in/ian-spence-agile1/">Ian Spence</a></li><li><a href="https://www.oreilly.com/library/view/aspect-oriented-software-development/0321268881/"><strong>Aspect-Oriented Software Development With Use Cases</strong></a>, 2004, <a href="https://en.wikipedia.org/wiki/Ivar_Jacobson">Ivar Jacobson</a></li><li><a href="https://www.oreilly.com/library/view/user-stories-applied/0321205685/"><strong>User Stories Applied</strong></a>, 2004, <a href="https://en.wikipedia.org/wiki/Mike_Cohn">Mike Cohn</a></li><li><a href="https://www.oreilly.com/library/view/agile-estimating-and/9780137126347/"><strong>Agile Estimating and Planning</strong></a>, 2005, <a href="https://en.wikipedia.org/wiki/Mike_Cohn">Mike Cohn</a></li><li><a href="https://www.oreilly.com/library/view/user-story-mapping/9781491904893/"><strong>User Story Mapping</strong></a>, 2014, <a href="https://www.linkedin.com/in/productdesigncoach/">Jeff Patton</a></li><li><a href="https://fiftyquickideas.com/fifty-quick-ideas-to-improve-your-user-stories/"><strong>Fifty Quick Ideas To Improve Your User Stories</strong></a>, 2014, <a href="https://www.linkedin.com/in/gojko/">Gojko Adzic</a>, <a href="https://www.linkedin.com/in/davidevansagilecoach/">David Evans</a></li><li><a href="https://softwareteaming.com/"><strong>Software Teaming</strong></a>, 2021, 2022, <a href="https://www.linkedin.com/in/woodyzuill/">Woody Zuill</a>, <a href="https://www.linkedin.com/in/jkmeadows/">Kevin Meadows</a></li><li><a href="https://slicingwork.com/"><strong>The Art of Slicing Work</strong></a>, 2024, <a href="https://www.linkedin.com/in/antonskornyakov/">Anton Skornyakov</a></li><li><a href="https://books.google.de/books/about/Unifying_User_Stories_Use_Cases_Story_Ma.html?id=Ybm00AEACAAJ"><strong>Unifying User Stories, Use Cases, Story Maps</strong></a>, 2024, <a href="https://en.wikipedia.org/wiki/Alistair_Cockburn">Alistair Cockburn</a></li><li><a href="https://books.google.de/books/about/The_Mini_Book_on_Use_Cases.html?id=oWV40QEACAAJ"><strong>The Mini-Book on Use Cases</strong></a>, 2025, <a href="https://en.wikipedia.org/wiki/Alistair_Cockburn">Alistair Cockburn</a></li><li><strong>The Book on Fine-grained Incremental Development</strong>, 2026?, <a href="https://en.wikipedia.org/wiki/Alistair_Cockburn">Alistair Cockburn</a></li></ul><h3>Videos</h3><ul><li>Ivar Jacobson<br>with Alistair Cockburn <a href="https://www.youtube.com/watch?v=QqKcuXB8PDo"><strong>on Use Cases</strong></a><strong><br></strong>with Ian Spence, and Mike Cohn <a href="https://www.youtube.com/watch?v=yT3FLPR8OFU"><strong>on Use Cases and User Stories</strong></a><strong><br></strong>with Ian Spence, and Jeff Patton <a href="https://www.youtube.com/watch?v=Y2Rs9rGVwGY"><strong>on Use Cases and User Story Maps</strong></a></li><li>Mike Cohn: <a href="https://www.youtube.com/watch?v=6q5-cVeNjCE"><strong>An Introduction to User Stories</strong></a></li><li>Ron Jeffries &amp; Chet Hendrickson on <a href="https://www.youtube.com/watch?v=UwYbSBUrotU"><strong>Thin-Slicing &amp; Micro-Increments</strong></a></li><li>Mike “GeePaw” Hill on <a href="https://www.youtube.com/watch?v=dI06ef8z2qo"><strong>Many More Much Smaller Steps (MMMSS)</strong></a></li><li>Dave Farley’s<br><a href="https://www.youtube.com/watch?v=kKbQ2-dXsmE"><strong>User Requirements That Constantly Change</strong></a><strong><br></strong><a href="https://www.youtube.com/watch?v=KP0U3I-f9-Y"><strong>Requirement Specification vs User Stories</strong></a><br><a href="https://www.youtube.com/watch?v=MECG5MPy_cc"><strong>A Practical Guide to User Stories &amp; Requirements</strong></a><br><a href="https://www.youtube.com/watch?v=_gteHp-ZR9k"><strong>User Stories Shouldn’t Be Too Big</strong></a><strong><br></strong><a href="https://www.youtube.com/watch?v=0HMsh459h5c"><strong>5 Common Mistakes In User Stories</strong></a></li></ul><h3>Resources</h3><ul><li>Jeff Patton’s <a href="https://jpattonassociates.com/story-mapping/"><strong>User Story Mapping Resources</strong></a></li><li>Ivar Jacobson International’s <a href="https://www.ivarjacobson.com/publications/books/use-case-30-ebook"><strong>Use Case 3.0</strong></a> Guidebook</li><li>The Humanizing Work’s <a href="https://www.humanizingwork.com/the-humanizing-work-guide-to-splitting-user-stories/"><strong>Guide to Splitting User Stories</strong></a></li><li>Mike Cohn’s <a href="https://www.mountaingoatsoftware.com/agile/new-to-agile-or-scrum"><strong>Introduction to Agile</strong></a> Guide<strong><br></strong>has useful sections on <a href="https://www.mountaingoatsoftware.com/agile/user-stories">User Stories</a>, <a href="https://www.mountaingoatsoftware.com/agile/agile-planning">Planning</a>, <a href="https://www.mountaingoatsoftware.com/agile/agile-estimation-estimating-with-story-points">Estimation</a>, and more</li><li>Ivar Jacobson International’s <a href="https://www.ivarjacobson.com/files/story_mapping_card_pack_-_ecards_v1.0.0.pdf"><strong>Story Mapping Essence Cards</strong></a></li><li>Ivar Jacobson International’s <a href="https://www.ivarjacobson.com/files/user_story_card_deck_-_ecards.pdf"><strong>User Story Essence Cards</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=915fb44eafa9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hitchhiker’s Guide to Hexiverse — Kanban]]></title>
            <link>https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-kanban-f526e0d37976?source=rss-c98461c29fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/f526e0d37976</guid>
            <category><![CDATA[lean-software-development]]></category>
            <category><![CDATA[kanban-system]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[flow-metrics]]></category>
            <category><![CDATA[kanban]]></category>
            <dc:creator><![CDATA[Aria Omidvar]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 15:59:21 GMT</pubDate>
            <atom:updated>2026-02-12T12:53:49.462Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Hitchhiker’s Guide to Hexiverse — Kanban</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D4EsQJdFCwNTvyIOiRFYdg.png" /><figcaption><strong>Kanban</strong> from <strong>Hexiverse</strong></figcaption></figure><p>In this article, I suggest a Hexi set for <a href="https://en.wikipedia.org/wiki/Kanban_(development)"><strong>Kanban</strong></a> and expand on each Hexi. The corresponding Hexi set can be found <a href="https://miro.com/app/board/uXjVKv84GGU=/?moveToWidget=3458764643783327768&amp;cot=14"><strong>here</strong></a>.</p><h3>Background</h3><p>Kanban is a familiar name among Agile and Lean practitioners. It is sometimes used as an alternative to Scrum and sometimes in combination with it. In general, the <em>continuous flow</em> that Kanban achieves is an alternative to <em>iterations</em> used by Agile methods like Extreme Programming and Scrum.</p><p>Originally, <a href="https://en.wikipedia.org/wiki/Kanban">kanban</a> is a component of the Toyota Production System (TPS) that enables Just-in-Time (JIT) production. <a href="https://en.wikipedia.org/wiki/Lean_software_development">Lean Software Development</a> is an adoption of Toyota/Lean principles and practices for the domain of software (product) development, pioneered by Mary and Tom Poppendieck. The <a href="https://en.wikipedia.org/wiki/Kanban_(development)">Kanban</a> method, as it is known in the realm of software development, mainly originated on a team at Corbis in 2006 [1]. Compared to LSD, Kanban is only one component that focuses on managing and improving the flow of value.</p><h3>Kanban Hexified</h3><p>For the development of this Hexi set, I rely on the Kanban Guide [2]. Many sentences and phrases are taken directly from the Kanban Guide, but for simplicity, I do not visualize them as quotes. What I have added based on my own opinions is clearly separate and distinguishable.</p><h3>Kanban System</h3><h4><a href="https://kanbanguides.org/the-kanban-guide/2025.5/#defining-and-visualizing-the-workflow">Workflow Definition &amp; Visualization</a></h4><p><strong>Definition of Workflow (DoW)</strong>: The explicit shared understanding of flow among Kanban system members within their context.</p><ul><li><strong>Work Item</strong>: A definition of the individual units of value that are moving through the workflow.</li><li><strong>Started and Finished</strong>: A definition for <em>when</em> work items are started and finished within the workflow.</li><li><strong>States</strong>: One or more defined states that the work items flow through between <em>Started</em> and <em>Finished</em>.<em><br></em>Any work items between a <em>Started</em> and a <em>Finished</em> are considered work in progress (WIP).</li><li><strong>WIP Control Agreement</strong>: A definition of how WIP will be controlled.</li><li><strong>Policies</strong>: Explicit policies about how work items can flow through each state.</li><li><strong>Service Level Expectation (SLE)</strong>: A forecast of how long it should take a work item to flow from <em>Started</em> to <em>Finished</em>.</li></ul><p>The visualization of a DoW is a <strong>Kanban board</strong> that contains all of the items above.</p><h4><a href="https://kanbanguides.org/the-kanban-guide/2025.5/#actively-managing-items-in-a-workflow">Workflow Management</a></h4><p>Active management of items in a workflow can take several forms, including but not limited to the following:</p><ul><li>Controlling WIP</li><li>Ensuring work items do not age unnecessarily, using the SLE as a reference</li><li>Unblocking blocked work</li></ul><h4><a href="https://kanbanguides.org/the-kanban-guide/2025.5/#improving-the-workflow">Workflow Improvement</a></h4><p>to achieve a better balance of effectiveness, efficiency, and predictability</p><h3>Flow Metrics</h3><h4>Work in Progress (WIP)</h4><p>The number of work items started but not finished.</p><h4>Work Item Age (WIA)</h4><p>The elapsed time between when a work item started and the current date.</p><h4>Cycle Time</h4><p>The elapsed time between when a work item started and when a work item finished.</p><h4>Throughput</h4><p>The number of work items finished per unit of time.</p><p>For a more comprehensive look at Flow/Lean metrics, please see <a href="https://nigelthurlow.com/all-about-lean-metrics/">All About Lean Metrics</a>.</p><h3>Continuous Flow vs Iterations vs Micro-iterations</h3><p>Kanban enables a <strong>continuous flow</strong> of work and value, meaning that a piece of value can be delivered as soon as it is ready. It also means that the next piece of work (read value) can be picked immediately afterward. This eliminates <em>iterations</em> and their pre-requisites: <em>estimation</em> and <em>planning</em>. Backlog Refinement is also replaced by <strong>Just-in-Time (JIT) Backlog Item Refinement</strong>. On the other side, it adds the <strong>WIP management</strong>.</p><p>In his video <a href="https://www.youtube.com/watch?v=fjeVFxL9MQA"><strong>Agile vs Kanban</strong></a>, Dave Farley makes a solid case for Kanban as an alternative approach to iterative development. He also explains how teams can benefit from some of the elements of iterations, along with a continuous flow created by Kanban.</p><p>Another approach that is used on the fringes is <strong>Micro-iterations</strong>. These iterations are 1 to 2 days long and deliver a very <strong>thin slice</strong> of value or a <strong>micro-increment</strong>. Micro-iterations, too, eliminate <em>planning</em> and <em>estimation</em>. For more on Micro-iterations, see <a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-whole-parts-steps-915fb44eafa9"><strong>Whole-Parts-Steps</strong></a>.</p><h3>Lean Metrics in Product Development</h3><p>In manufacturing, the same product is <em>produced</em> over and over. In product development, however, we are always <em>developing</em> (read <em>building</em> or <em>creating</em>) a product, and none of the pieces of work are alike. The same difference in nature makes the use and utility of <em>Lean metrics</em> different in product development.</p><p>In manufacturing, the repetitive nature of work enables <em>predictability</em>. As a result, <em>measurement</em> is not only possible but also essential for <em>improvement</em>. When applied to product development, however, predictability highly depends on the context, and even then, it can never be as precise as in manufacturing.</p><p>The more exploratory the nature of the work at hand, the lower the predictability. For instance, when a product is just being born, or is still custom-made for particular customers, it is highly unpredictable. When the product grows to become a standard product (AKA productized), its unpredictability lowers, but still not so much. When the <em>Discovery</em> of the product normalizes and becomes minor compared to its <em>Delivery</em>, then its further development becomes somewhat predictable. When the product is well established and the changes become of the improvement kind, the development is predictable enough to make good use of Lean metrics. In conclusion, Lean metrics are less applicable in the earlier evolution stages of a product and more applicable in the later stages.</p><p>For a better understanding of these phases, please see Wardley Maps’ <a href="https://www.wardleymaps.com/glossary/evolution-stages">evolution stages</a>.</p><h3>Your Feedback</h3><p>If you have comments or suggestions, please do not hesitate to express them here in the comments or message me directly on <a href="https://www.linkedin.com/in/aria-omidvar/">LinkedIn</a>. I welcome all kinds of commentary, ideas, and chats on the topic.</p><p>[1] <a href="https://www.youtube.com/watch?v=RKdzh0CUwuY"><strong>The Secret History of Kanban</strong></a>, 2020, <a href="https://www.linkedin.com/in/danielvacanti/">Daniel Vacanti</a><br>[2] <a href="https://kanbanguides.org/the-kanban-guide/2025.5/"><strong>The Kanban Guide</strong></a></p><h3>Lean and Kanban for Software Literature</h3><p>Lean and Kanban have become very popular approaches and now have many valuable books. The ones listed below are significant due to their precedence and influence.</p><ul><li><a href="https://www.oreilly.com/library/view/lean-software-development/0321150783/"><strong>Lean Software Development</strong></a>, 2003, <a href="https://www.leanessays.com/">Mary</a> &amp; <a href="https://www.poppsphoto.com/">Tom</a> Poppendieck</li><li><a href="https://www.oreilly.com/library/view/implementing-lean-software/0321437381/title.html"><strong>Implementing Lean Software Development</strong></a>, 2006, <a href="https://www.leanessays.com/">Mary</a> &amp; <a href="https://www.poppsphoto.com/">Tom</a> Poppendieck</li><li><a href="https://www.oreilly.com/library/view/leading-lean-software/9780321699633/"><strong>Leading Lean Software Development</strong></a>, 2009, <a href="https://www.leanessays.com/">Mary</a> &amp; <a href="https://www.poppsphoto.com/">Tom</a> Poppendieck</li><li><a href="https://www.oreilly.com/library/view/lean-agile-software-development/9780321648013/"><strong>Lean-Agile Software Development</strong></a>, 2009, <a href="https://www.linkedin.com/in/alshalloway/">Alan Shalloway</a>, <a href="https://www.linkedin.com/in/guybeaver/">Guy Beaver</a>, <a href="https://www.linkedin.com/in/jim-trott/">James Trott</a></li><li><a href="https://books.google.de/books/about/Scrumban_Essays_on_Kanban_Systems_for_Le.html?id=SQFdAgAAQBAJ"><strong>Scrumban</strong></a>, 2009, <a href="https://www.linkedin.com/in/coreyladas/">Corey Ladas</a></li><li><a href="https://www.infoq.com/minibooks/kanban-scrum-minibook/"><strong>Kanban and Scrum</strong></a>, 2010, <a href="https://www.linkedin.com/in/hkniberg/">Henrik Kniberg</a>, <a href="https://www.linkedin.com/in/mattiasskarin/">Mattias Skarin</a></li><li><a href="https://books.google.de/books/about/Kanban.html?id=RJ0VUkfUWZkC"><strong>Kanban</strong></a>, 2010, <a href="https://www.linkedin.com/in/agilemanagement/">David Anderson</a></li><li><a href="https://www.personalkanban.com/"><strong>Personal Kanban</strong></a>, 2011, <a href="https://www.linkedin.com/in/jimbenson/">Jim Benson</a>, Tonianne DeMaria Barry</li><li><a href="https://pragprog.com/titles/hklean/lean-from-the-trenches/"><strong>Lean from the Trenches</strong></a>, 2011, <a href="https://www.linkedin.com/in/hkniberg/">Henrik Kniberg</a></li><li><a href="https://books.google.de/books/about/Lessons_in_Agile_Management.html?id=vSJ8MAEACAAJ"><strong>Lessons in Agile Management</strong></a>, 2012, <a href="https://www.linkedin.com/in/agilemanagement/">David Anderson</a></li><li><a href="https://www.goodreads.com/book/show/16208052-stop-starting-start-finishing"><strong>Stop Starting, Start Finishing!</strong></a>, 2012, <a href="https://www.linkedin.com/in/arne-roock-ph-d-33b7062a/">Arne Roock</a>, Claudia Leschik</li><li><a href="https://books.google.de/books/about/Why_Limit_WIP_We_are_Drowning_in_Work.html?id=mbgFoQEACAAJ"><strong>Why Limit WIP</strong></a>, 2014, <a href="https://www.linkedin.com/in/jimbenson/">Jim Benson</a></li><li><a href="https://actionableagile.com/books/aamfp/"><strong>Actionable Agile Metrics for Predictability</strong></a>, 2015, <a href="https://www.linkedin.com/in/danielvacanti/">Daniel Vacanti</a></li><li><a href="https://pragprog.com/titles/mskanban/real-world-kanban/"><strong>Real-World Kanban</strong></a>, 2015, 2025, <a href="https://www.linkedin.com/in/mattiasskarin/">Mattias Skarin</a></li><li><a href="https://www.oreilly.com/library/view/agile-project-management/9780735698963/"><strong>Agile Project Management with Kanban</strong></a>, 2015, <a href="https://www.linkedin.com/in/ericbrechner/">Eric Brechner</a></li><li><a href="https://leanpub.com/practicalkanban"><strong>Practical Kanban</strong></a>, 2017, <a href="https://www.linkedin.com/in/klausleopold/">Klaus Leopold</a></li></ul><h3>Videos</h3><ul><li><a href="https://www.youtube.com/playlist?list=PLMytyWxm7htf8hVgCWfJBOcrCA6mqFY3G"><strong>Eric Brechner on Project Management with Kanban</strong></a><strong><br></strong>Eric’s demonstration of Kanban in his talks is particularly helpful.</li><li><a href="https://www.youtube.com/playlist?list=PLMytyWxm7htf8hVgCWfJBOcrCA6mqFY3G"><strong>Eric Brechner on Project Management with Kanban</strong></a><strong><br></strong>Eric’s demonstration of Kanban in his talks is particularly helpful.</li></ul><h3>Resources</h3><ul><li>Ivar Jacobson International’s <a href="https://www.ivarjacobson.com/kanban-cards/"><strong>Kanban Essence</strong></a></li><li>Modern Agile’s <a href="https://modernagile.org/#cheatsheets"><strong>Accelerating Flow</strong></a> Cheat Sheet</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f526e0d37976" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hitchhiker’s Guide to Hexiverse — Scrum]]></title>
            <link>https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf?source=rss-c98461c29fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/794b282666cf</guid>
            <category><![CDATA[scrum-guide]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Aria Omidvar]]></dc:creator>
            <pubDate>Fri, 10 Oct 2025 15:16:49 GMT</pubDate>
            <atom:updated>2026-02-12T12:54:27.948Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Hitchhiker’s Guide to Hexiverse — Scrum</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jsJw9BUdXv5av5HflRcRqA.png" /><figcaption><strong>Scrum</strong> from <strong>Hexiverse</strong></figcaption></figure><p>In this article, I suggest a Hexi set for <a href="https://en.wikipedia.org/wiki/Scrum_(software_development)"><strong>Scrum</strong></a> and expand on each Hexi. The corresponding Hexi set can be found <a href="https://miro.com/app/board/uXjVKv84GGU=/?moveToWidget=3458764607401602898&amp;cot=14"><strong>here</strong></a>.</p><h3>The Official Scrum Hexi Kit</h3><p>Before presenting my Hexi set, I want to point out that Scrum.org is one of the very early joiners of the original Hexi ecosystem and already has an <a href="https://thecynefin.co/product/hexi-scrumorg/"><strong>official Hexi kit</strong></a>. I have not seen it personally, but for those serious about the Hexi approach, I highly recommend checking it out.</p><p>My Hexi adaptation of Scrum remains an independent version and has no relation to the official Kit.</p><h3>Scrum Hexified</h3><p>Contrary to the common belief, Scrum has evolved through time. For example, it is hard to believe now, but originally, Retrospectives were not a part of Scrum. Scrum Values were also added in 2013. The <em>Scrum patterns</em> collected in <a href="https://pragprog.com/titles/jcscrum/a-scrum-book/"><strong>A Scrum Book</strong></a> are also more comprehensive than the essential Scrum offered by the guide. The official terminology has had some minor changes as well.</p><p>There are a handful of practices that are associated with Scrum, where there is no official association. Alistair Cockburn beautifully comments on this phenomenon in his <a href="https://youtu.be/AuUadPoi35M"><strong>Core Scrum, Barnacles, Rumors and Hearsay</strong></a> talk.</p><p>This Hexi set is based on the structure of the 2020 Scrum Guide, with one difference that I blended <em>artifacts</em> and <em>events</em>.</p><h3>Scrum Theory</h3><h4><a href="https://scrumguides.org/scrum-guide.html#transparency">Transparency</a></h4><blockquote>The emergent <strong>process</strong> and <strong>work</strong> must be <strong>visible</strong> to those <strong>performing</strong> the work as well as those <strong>receiving</strong> the work.<em> [1]</em></blockquote><p>Related pattern: <a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-kanban-f526e0d37976"><strong>Workflow Definition &amp; Visualization</strong></a></p><h4><a href="https://scrumguides.org/scrum-guide.html#inspection">Inspection</a></h4><blockquote>The Scrum <strong>artifacts</strong> and the <strong>progress</strong> must be inspected <strong>frequently</strong> and <strong>diligently</strong> to detect potentially undesirable variances or problems.<em> [1]</em></blockquote><h4><a href="https://scrumguides.org/scrum-guide.html#adaptation">Adaptation</a></h4><blockquote>If any aspects of a <strong>process</strong> deviate outside acceptable limits or if the resulting <strong>product</strong> is unacceptable, the process being applied or the materials being produced must be <strong>adjusted</strong>.<em> [1]</em></blockquote><h3>Scrum Values</h3><blockquote><strong>Qualities</strong> that <strong>people</strong> using Scrum <strong>display</strong>.<em> [1]</em></blockquote><p>For this guide, I relied on the Scrum guide, but for a proper understanding of the values, I highly recommend Gunther Verheyen’s <a href="https://guntherverheyen.com/library/the-scrum-values/"><strong>The Scrum Values</strong></a> and Jeff Sutherland’s <a href="https://www.youtube.com/watch?v=Xu_X7KbtbV8"><strong>The 5 Scrum Values</strong></a>.</p><h4>Commitment</h4><blockquote>The Scrum Team <strong>commits</strong> to <strong>achieving its goals</strong> and to <strong>supporting each other</strong>.<em> [1]</em></blockquote><h4>Focus</h4><blockquote>Their primary <strong>focus</strong> is on the work of the <strong>Sprint</strong> to make the best possible progress toward these <strong>goals</strong>.<em> [1]</em></blockquote><h4>Openness</h4><blockquote>The Scrum Team and its stakeholders are <strong>open</strong> about the <strong>work</strong> and the <strong>challenges</strong>.<em> [1]</em></blockquote><h4>Respect</h4><blockquote>Scrum Team members <strong>respect each other</strong> to be capable, independent people, and <strong>are respected</strong> as such by the people with whom they work.<em> [1]</em></blockquote><p>Related pattern: <strong>Respect</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">HGIH — XP</a>]</p><h4>Courage</h4><blockquote>The Scrum Team members have the <strong>courage</strong> to do the right thing, to work on tough problems.<em> [1]</em></blockquote><p>Related pattern: <strong>Courage</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">HGIH — XP</a>]</p><h3>Scrum Team</h3><blockquote>a <strong>cohesive unit of professionals</strong> focused on <strong>one objective</strong> at a time, the Product Goal.<em> [1]</em></blockquote><p>Scrum Teams are…</p><ul><li><strong>cross-functional: </strong>they have all the skills necessary to create value each Sprint</li><li><strong>self-managing: </strong>they internally decide who does what, when, and how</li><li><strong>small enough </strong>to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people</li><li><strong>responsible for all product-related activities </strong>from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development [1]</li></ul><p>Related patterns: <strong>Self-Organizing Teams</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">HGIH — Manifesto</a>], <strong>Motivated Individuals</strong> [HGIH — Manifesto], <strong>Support &amp; Trust</strong> [HGIH — Manifesto], <strong>Sit Together</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">HGIH — XP</a>], <strong>Whole Team</strong> [HGIH — XP], <strong>Diversity</strong> [HGIH — XP], <strong>Team Continuity</strong> [HGIH — XP]</p><h4><a href="https://scrumguides.org/scrum-guide.html#developers">Developers</a></h4><blockquote>the people in the Scrum Team.<em> [1]</em></blockquote><h4><a href="https://scrumguides.org/scrum-guide.html#product-owner">Product Owner</a></h4><blockquote>accountable for <strong>maximizing the value of the product</strong>.<em> [1]</em></blockquote><p>Related pattern: <strong>Real Customer Involvement</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">HGIH — XP</a>]</p><h4><a href="https://scrumguides.org/scrum-guide.html#scrum-master">Scrum Master</a></h4><blockquote>accountable for <strong>establishing Scrum</strong> as defined in the Scrum Guide.<em> [1]</em></blockquote><p><strong>XP Coach</strong> is a similar role, but it is not a part of the formal XP.</p><h3>Scrum Events</h3><h4><a href="https://scrumguides.org/scrum-guide.html#the-sprint">Sprint</a></h4><blockquote>enables <strong>predictability</strong> by ensuring <strong>inspection</strong> and <strong>adaptation</strong> of progress toward a Product Goal at least every calendar month.<em> [1]</em></blockquote><p>The name <em>Sprint</em> has been questioned and challenged over the years, as it suggests speed. Kevlin Henney has beautifully written on the topic in his article <a href="https://kevlinhenney.medium.com/agility-speed-96057078fe40"><strong>Agility ≠ Speed</strong></a>.</p><p>Related pattern: <strong>Weekly Cycle</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">HGIH — XP</a>]</p><h4><a href="https://scrumguides.org/scrum-guide.html#sprint-planning">Sprint Planning</a></h4><blockquote>initiates the Sprint by <strong>laying out the work</strong> to be performed for the Sprint.<em> [1]</em></blockquote><h4><a href="https://scrumguides.org/scrum-guide.html#daily-scrum">Daily Scrum</a></h4><blockquote>to <strong>inspect progress</strong> toward the Sprint Goal and <strong>adapt</strong> the Sprint Backlog as necessary, <strong>adjusting</strong> the upcoming planned work.<em> [1]</em></blockquote><p>See also: <a href="https://tidyfirst.substack.com/p/standups-individual-teammate"><strong>Standups: Individual → Teammate</strong></a>, <a href="https://holub.com/nostandups/"><strong>#NoStandups</strong></a></p><h4><a href="https://scrumguides.org/scrum-guide.html#sprint-review">Sprint Review</a></h4><blockquote>to <strong>inspect</strong> the outcome of the Sprint and <strong>determine future adaptations</strong>.<em> [1]</em></blockquote><h4><a href="https://scrumguides.org/scrum-guide.html#sprint-retrospective">Sprint Retrospective</a></h4><blockquote>to plan ways to increase quality and effectiveness.<em> [1]</em></blockquote><p>Related patterns: <strong>Continuous Improvement</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">HGIH — Manifesto</a>], <strong>Reflection</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">HGIH — XP</a>]</p><h3>Scrum Artifacts</h3><blockquote>designed to <strong>maximize transparency</strong> of key information.<em> [1]</em></blockquote><p>Related pattern: <strong>Informative Workspace</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">HGIH — XP</a>]</p><h4><a href="https://scrumguides.org/scrum-guide.html#product-backlog">Product Backlog</a></h4><blockquote>an <strong>emergent</strong>, <strong>ordered</strong> list of what is needed to improve the <strong>product</strong>.<em> [1]</em></blockquote><h4>Product Goal</h4><blockquote>describes a <strong>future state of the product</strong> which can serve as a target for the Scrum Team to plan against.<em> [1]</em></blockquote><h4><a href="https://scrumguides.org/scrum-guide.html#sprint-backlog">Sprint Backlog</a></h4><blockquote>is composed of the <strong>Sprint Goal</strong>, the set of <strong>Product Backlog items</strong> selected for the Sprint, as well as an <strong>actionable plan</strong> for delivering the Increment.<em> [1]</em></blockquote><h4>Sprint Goal</h4><blockquote>the single <strong>objective</strong> for the Sprint.<em> [1]</em></blockquote><h4><a href="https://scrumguides.org/scrum-guide.html#increment">Increment</a></h4><blockquote>a concrete <strong>stepping stone</strong> toward the Product Goal.<em> [1]</em></blockquote><p>Related pattern: <strong>Baby Steps</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f">HGIH — XP</a>]</p><h4>Definition of Done</h4><blockquote>a <strong>formal description</strong> of the state of the Increment when it meets the quality measures required for the product.<em> [1]</em></blockquote><h3>Scrum Patterns</h3><p>Another, more comprehensive expression of Scrum as a Pattern Language has been being developed by the <a href="https://www.scrumplop.org/">Scrum Pattern Community</a>. I have integrated Scrum Patterns into the Hexiverse and provided a guide for it as well: <a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-patterns-15062fc30656"><strong>The Hitchhiker’s Guide to Hexiverse — Scrum Patterns</strong></a></p><p>I firmly believe that Scrum Patterns are essential for Scrum practitioners’ knowledge and understanding of Scrum.</p><h3>Your Feedback</h3><p>If you have comments or suggestions, please do not hesitate to express them here in the comments or message me directly on <a href="https://www.linkedin.com/in/aria-omidvar/">LinkedIn</a>. I welcome all kinds of commentary, ideas, and chats on the topic.</p><p>[1] <a href="https://scrumguides.org/scrum-guide.html"><strong>Scrum Guide</strong></a>, 2020</p><h3>Literature</h3><ul><li><strong>Agile Software Development with Scrum</strong>, 2002, <a href="https://en.wikipedia.org/wiki/Ken_Schwaber">Ken Schwaber</a> and <a href="https://en.wikipedia.org/wiki/Mike_Beedle">Mike Beedle</a></li><li><strong>Agile Project Management with Scrum</strong>, 2004, <a href="https://en.wikipedia.org/wiki/Ken_Schwaber">Ken Schwaber</a></li><li><strong>The Enterprise and Scrum</strong>, 2007, <a href="https://en.wikipedia.org/wiki/Ken_Schwaber">Ken Schwaber</a></li><li><a href="https://www.oreilly.com/library/view/succeeding-with-agile/9780321660534/"><strong>Succeeding with Agile</strong></a>, 2009, <a href="https://www.linkedin.com/in/mikewcohn/">Mike Cohn</a></li><li><a href="https://leanpub.com/scrumproductownership-balancingvaluefromtheinsideout3rdedition"><strong>Scrum Product Ownership</strong></a>, 2009, 2013, 2019, <a href="https://www.linkedin.com/in/bobgalen/">Bob Galen</a></li><li><a href="https://www.romanpichler.com/romans-books/agile-product-management-with-scrum/"><strong>Agile Product Management with Scrum</strong></a>, 2010, <a href="https://www.linkedin.com/in/romanpichler/">Roman Pichler</a></li><li><a href="https://www.scrum.org/resources/software-30-days"><strong>Software in 30 Days</strong></a>, 2012, <a href="https://en.wikipedia.org/wiki/Ken_Schwaber">Ken Schwaber</a>, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a></li><li><a href="https://innolution.com/essential-scrum"><strong>Essential Scrum</strong></a>, 2012, <a href="https://www.linkedin.com/in/kennethrubin/">Ken Rubin</a></li><li><a href="https://guntherverheyen.com/2013/05/03/theres-value-in-the-scrum-values/"><strong>There’s value in the Scrum Values</strong></a>, 2013, <a href="https://www.linkedin.com/in/ullizee/">Gunther Verheyen</a></li><li><a href="https://www.vanharen.net/standards/agile/scrum-pocket-guide-4th-edition/"><strong>Scrum — A Pocket Guide</strong></a>, 2013, 2019, 2021, 2024, <a href="https://www.linkedin.com/in/ullizee/">Gunther Verheyen</a></li><li><a href="https://tobiasmayer.uk/works/the-peoples-scrum/"><strong>The People’s Scrum</strong></a>, 2013, <a href="https://www.linkedin.com/in/tobiasgmayer/">Tobias Mayer</a></li><li><a href="https://www.scruminc.com/new-scrum-the-book/"><strong>Scrum: The Art of Doing Twice the Work in Half the Time</strong></a>, 2014, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a></li><li><a href="https://pragprog.com/titles/jcscrum/a-scrum-book/"><strong>A Scrum Book</strong></a>, 2019, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a>, <a href="https://www.linkedin.com/in/coplien/">James Coplien</a>, The Scrum Patterns Group</li><li><a href="https://tobiasmayer.uk/works/scrumnotes/"><strong>Scrum Notes</strong></a>, 2020, <a href="https://www.linkedin.com/in/tobiasgmayer/">Tobias Mayer</a></li><li><a href="https://leanpub.com/firstprinciplesinscrum"><strong>First Principles in Scrum</strong></a>, 2024, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a></li></ul><h3>Articles</h3><ul><li><a href="https://en.wikipedia.org/wiki/Hirotaka_Takeuchi">Hirotaka Takeuchi</a> and <a href="https://en.wikipedia.org/wiki/Ikujiro_Nonaka">Ikujiro Nonaka</a>’s paper <a href="https://hbr.org/1986/01/the-new-new-product-development-game"><strong>The New New Product Development Game</strong></a></li><li><a href="https://en.wikipedia.org/wiki/Ron_Jeffries">Ron Jeffries</a>’s essay <a href="https://ronjeffries.com/articles/016-09ff/defense/"><strong>Dark Scrum</strong></a></li><li>Martin Fowler’s <a href="https://martinfowler.com/bliki/FlaccidScrum.html"><strong>Flaccid Scrum</strong></a></li></ul><h3>Videos</h3><ul><li><a href="https://en.wikipedia.org/wiki/Alistair_Cockburn">Alistair Cockburn</a>’s <a href="https://youtu.be/AuUadPoi35M"><strong>Core Scrum, Barnacles, Rumors and Hearsay</strong></a></li><li><a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a>’s <a href="https://www.youtube.com/watch?v=Xu_X7KbtbV8"><strong>The 5 Scrum Values</strong></a></li><li><a href="https://www.linkedin.com/in/nigelthurlow/">Nigel Thurlow</a>’s introduction to <a href="https://www.youtube.com/watch?v=7gevhg_PgMM"><strong>Scrum the Toyota Way</strong></a></li><li><a href="https://www.linkedin.com/in/ullizee/">Gunther Verheyen</a> reads his book <strong>Scrum — A Pocket Guide [2nd edition]</strong> in 5 parts: <a href="https://www.youtube.com/watch?v=E_V8c_0DqNQ"><strong>1</strong></a>, <a href="https://www.youtube.com/watch?v=3JZvR0wsuhg"><strong>2</strong></a>, <a href="https://www.youtube.com/watch?v=9Y8IeXKtRNg"><strong>3</strong></a>, <a href="https://www.youtube.com/watch?v=2xv6DAXOe4w"><strong>4</strong></a>, <a href="https://www.youtube.com/watch?v=n0t2TXmmWao"><strong>5</strong></a></li><li><a href="https://www.linkedin.com/in/joejustice/">Joe Justice</a> reads his book <a href="https://www.youtube.com/playlist?list=PLjbCYneauptj7PTV2wSCwgEHZiuHLKjjr"><strong>Scrum Master</strong></a></li></ul><h3>Resources</h3><ul><li><a href="https://scrumguides.org/scrum-guide.html"><strong>Scrum Guide</strong></a>, 2020</li><li><a href="https://simplescrum.guide/"><strong>A simple guide to Scrum</strong></a>, 2025, <a href="https://www.linkedin.com/in/tobiasgmayer/">Tobias Mayer</a>, <a href="https://www.linkedin.com/in/bobhartman/">Bob Hartman</a></li><li><a href="https://scrumexpansion.org/scrum-guide-expansion-pack/"><strong>Scrum Guide Expansion Pack</strong></a>, 2025, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a>, <a href="https://www.linkedin.com/in/ralphjocham/">Ralph Jocham</a>, <a href="https://www.linkedin.com/in/johnanthonycoleman/">John Coleman</a></li><li><a href="https://www.linkedin.com/in/mikewcohn/">Mike Cohn</a>’s <a href="https://www.mountaingoatsoftware.com/agile/new-to-agile-or-scrum"><strong>Guide to Agile &amp; Scrum</strong></a> and <a href="https://www.mountaingoatsoftware.com/exclusive/scrum-foundations"><strong>Scrum Foundations</strong></a> courses</li><li><a href="https://www.linkedin.com/in/sohrabsalimi/">Sohrab Salimi</a>’s <a href="https://www.agile-academy.com/en/agile-insights/agile-fundamentals-online-course/"><strong>Agile Fundamentals</strong></a> and <a href="https://www.agile-academy.com/en/agile-insights/scrum-foundations-online-course/"><strong>Scrum Foundations</strong></a><strong> </strong>courses</li><li><a href="https://www.linkedin.com/in/ullizee/">Gunther Verheyen</a>’s <a href="https://guntherverheyen.com/library/the-scrum-values/"><strong>The Scrum Values</strong></a></li><li><a href="https://www.linkedin.com/in/kennethrubin/">Ken Rubin</a>’s <a href="https://innolution.com/essential-scrum/table-of-contents"><strong>Essential Scrum</strong></a> content summary</li><li><a href="https://scrumdictionary.com/"><strong>Scrum Dictionary</strong></a></li><li>Scrum Alliance’s <a href="https://www.scrumalliance.org/glossary"><strong>Agile Glossary</strong></a></li><li>Ivar Jacobson International’s <a href="https://www.ivarjacobson.com/publications/blog/agile-tools-coaching/better-scrum-through-essence"><strong>Scrum Essence</strong></a> and <a href="https://www.ivarjacobson.com/files/scrum_cards_2025.pdf"><strong>Scrum Essence Cards</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=794b282666cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hitchhiker’s Guide to Hexiverse — Extreme Programming]]></title>
            <link>https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-3-extreme-programming-a3f52414499f?source=rss-c98461c29fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3f52414499f</guid>
            <category><![CDATA[extreme-programming]]></category>
            <dc:creator><![CDATA[Aria Omidvar]]></dc:creator>
            <pubDate>Thu, 11 Sep 2025 15:15:53 GMT</pubDate>
            <atom:updated>2026-02-12T12:55:00.381Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Hitchhiker’s Guide to Hexiverse — Extreme Programming</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3icYYuyZSMdjPbe8KNotlA.png" /><figcaption><strong>Extreme Programming</strong> from <strong>Hexiverse</strong></figcaption></figure><p>In this article, I suggest a Hexi set for <a href="https://en.wikipedia.org/wiki/Extreme_programming"><strong>Extreme Programming (XP)</strong></a> and expand on each Hexi. The corresponding Hexi set can be found <a href="https://miro.com/app/board/uXjVKv84GGU=/?moveToWidget=3458764607401738102&amp;cot=14"><strong>here</strong></a>.</p><h3>Tracing XP</h3><p>XP has a long and lively history. When I was researching it for finalizing this Hexi set, I noticed once again how advanced and nuanced it is. <a href="https://wiki.c2.com/">C2 Wiki</a> contains a magnificent web of interrelated Patterns that can take its explorers down rabbit holes. If one survives these deep dives, however, one returns with an <em>I-know-Kung-Fu</em> [1] sensation.</p><p>It also has an organic and community-driven development history. One of the side effects of this characteristic is multiple terms for similar concepts. Here, I rely on the terminology used in the second edition of XP Explained [2] and provide the most recognized similar terms wherever possible.</p><p><a href="https://www.linkedin.com/in/kentbeck/">Kent Beck</a> created XP with strong influence from <a href="https://en.wikipedia.org/wiki/Ward_Cunningham">Ward Cunningham</a> and the efforts of <a href="https://ronjeffries.com/">Ron Jeffries</a>. Many more have since spread and expanded it, resulting in a substantial body of literature covering all aspects of XP, listed at the end of this article.</p><h3>XP Hexified</h3><p>As wonderful as it feels to explore XP and to offer this Hexi set for it, I must warn readers and learners from mistaking this effort for <em>simplifying</em> XP. This guide and its corresponding Hexi set are NOT a condensed version of XP! They are merely an effort to bring the wonderful XP into the world of Hexi and introduce it to beginners while providing it for practical purposes as well. For a deeper understanding of XP, there is no better way than referring to the body of literature listed at the end of this article.</p><h4>Values, Principles, Practices</h4><p>As in XPX2 [2], I have shaped this Hexi set based on the taxonomy of Values, Principles, and Practices.</p><p><strong>Values</strong> are at the heart of our preferences, <em>why</em> we do or don’t do, like, or choose things. They are <em>universal</em> and <em>abstract (vague)</em>, and provide <em>purpose</em> and <em>direction</em> to Practices.</p><p><strong>Practices</strong> are manifestations of Values. They are <em>concrete</em>, <em>situated</em>, and bring <em>accountability</em> to values.</p><p><strong>Principles </strong>bridge the vast gap between Values and Practices. Principles are <em>domain-specific</em> guidelines.</p><h3>Values</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OANII-TcVaycTt8_2FErEA.png" /><figcaption><strong>Extreme Programming Values</strong> from <strong>Hexiverse</strong></figcaption></figure><p>Values are interconnected. They enforce and balance each other.</p><h4>Communication</h4><p>What matters most in team software development is communication. Communication is important for creating a sense of team and effective cooperation.</p><h4>Simplicity</h4><p>To make a solution <em>simple</em> enough to solve only the problem at hand. Simplicity is <em>context-dependent</em>. Someone’s <em>simple</em> is <em>complex</em> to someone else. What was a <em>simple</em> solution yesterday may be <em>complex</em> today.</p><p>Related pattern: <strong>Simplicity</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><p>See also: <a href="http://wiki.c2.com/?DoTheSimplestThingThatCouldPossiblyWork"><strong>Do The Simplest Thing That Could Possibly Work</strong></a></p><h4>Feedback</h4><p>Change is inevitable. Change requires course correction and realignment, and it depends on feedback with a preference for shorter feedback cycles.</p><h4>Courage</h4><blockquote>Courage is effective action in the face of fear.</blockquote><blockquote>The courage to speak truths, pleasant or unpleasant, fosters communication and trust. The courage to discard failing solutions and seek new ones encourages simplicity. The courage to seek real, concrete answers creates feedback.<em> [3]</em></blockquote><p>Related pattern: <strong>Courage</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>]</p><h4>Respect</h4><p>Respect lies under the surface of the other values. Respect manifests itself in members of a team caring about each other and what they are doing, recognizing each other’s contributions, and caring about the collective effort.</p><p>Related pattern: <strong>Golden Rules</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>], <strong>Respect</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>]</p><h3>Other Values</h3><p>In XPX2 [2], it is wisely suggested that these values are not finite, and teams and organizations can create their own values. “What is most important is aligning team <em>behavior</em> to team <em>values</em>.” [3]</p><p>They even suggest <strong>Safety</strong>, <strong>Security</strong>, <strong>Predictability</strong>, and <strong>Quality-of-Life</strong> as complementary values.</p><h3>Principles</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t3K59qNuQ6HilQdJ39g2mQ.png" /><figcaption><strong>Extreme Programming Principles</strong> from <strong>Hexiverse</strong></figcaption></figure><p>These principles listed here are not the only possible principles to guide software development, but perhaps sufficient for general-purpose software development. In other domains, other principles may emerge. For instance, “in the development of safety-critical systems, the principle of <em>traceability</em> is at work.” [4]</p><p>See also: <a href="https://martinfowler.com/bliki/PrinciplesOfXP.html"><strong>Principles of XP</strong></a></p><h4>Humanity</h4><blockquote>Software development should meet <strong>human needs</strong>, acknowledge <strong>human frailty</strong>, and leverage <strong>human strength</strong>. <em>[4]</em></blockquote><p>Related patterns: <strong>Human</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-modern-synthesis-b1e3b61ba3c1">Modern Synthesis</a>]</p><h4>Economics</h4><blockquote>Make sure what you are doing has <strong>business value</strong>, meets <strong>business goals</strong>, and serves <strong>business needs</strong>. <em>[4]</em></blockquote><p>Related pattern: <strong>Business + Development</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h4>Mutual Benefit</h4><blockquote>Every activity should <strong>benefit all concerned</strong>. <em>[4]</em></blockquote><h4>Self-Similarity</h4><blockquote>Try <strong>copying the structure of one solution into a new context</strong>, even at different scales. <em>[4]</em></blockquote><h4>Improvement</h4><blockquote><strong>Do the best you can today</strong>, striving for the awareness and understanding necessary to <strong>do better tomorrow</strong>. <em>[4]</em></blockquote><p>Related patterns: <strong>Continuous Improvement</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>], <strong>Sprint Retrospective</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>], <strong>Continuous Improvement</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4>Diversity</h4><blockquote>Teams need to bring together a variety of <strong>skills</strong>, <strong>attitudes</strong>, and <strong>perspectives</strong> to see problems and pitfalls, to think of multiple ways to solve problems, and to implement the solutions. Teams need diversity. <em>[4]</em></blockquote><blockquote>Diversity is expressed in the practice of <strong>Whole Team</strong>, where you bring together on the team people with a variety of skills and perspectives. <em>[4]</em></blockquote><p>Related pattern: <strong>Scrum Team</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>], <strong>Team Cognition</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4>Reflection</h4><blockquote>Good teams don’t just do their work, they think about <strong>how they are working</strong> and <strong>why they are working</strong>. They analyze <strong>why they succeeded or failed</strong>. They don’t try to hide their mistakes, but <strong>expose them</strong> and <strong>learn from them</strong>. <em>[4]</em></blockquote><p>Related patterns: <strong>Continuous Improvement</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>], <strong>Sprint Retrospective</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>], <strong>Retrospectives &amp; Retrospecting</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4>Flow</h4><blockquote>Flow in software development is delivering a <strong>steady flow of valuable software</strong> by engaging in all the activities of development simultaneously. <em>[4]</em></blockquote><p>Related pattern: <strong>Early &amp; Continuous Delivery of Value</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h4>Opportunity</h4><blockquote>To reach excellence, <strong>problems</strong> need to turn into <strong>opportunities for learning and improvement</strong>, not just survival. <em>[4]</em></blockquote><h4>Redundancy</h4><blockquote>The critical, difficult problems in software development should be solved <strong>several different ways</strong>. Even if one solution fails utterly, the other solutions will prevent disaster. The cost of the redundancy is more than paid for by the savings from not having the disaster. <em>[4]</em></blockquote><h4>Failure</h4><blockquote>If you’re having trouble succeeding, <strong>risking failure</strong> can be the shortest, surest road to success.</blockquote><blockquote>Isn’t failure waste? No, not if it <strong>imparts knowledge</strong>. <em>[4]</em></blockquote><p>Related patterns: <strong>Exploration &amp; Experimentation</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4>Quality</h4><blockquote>Each increase in quality leads to <strong>improvements</strong> in other desirable project properties, like <strong>productivity</strong> and <strong>effectiveness</strong>, as well. <em>[4]</em></blockquote><h4>Baby Steps</h4><blockquote>Baby steps acknowledge that the <strong>overhead of small steps</strong> is much less than when a team wastefully recoils from aborted big changes. <em>[4]</em></blockquote><p>Related pattern: <strong>Increment</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>], <strong>MMMSS</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-modern-synthesis-b1e3b61ba3c1">Modern Synthesis</a>]</p><h4>Accepted Responsibility</h4><blockquote>Responsibility <strong>cannot be assigned</strong>; it can only be accepted. <em>[4]</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CQoXCwVFLRAALXi5euJ1_g.png" /><figcaption><strong>Extreme Programming Practices</strong> from <strong>Hexiverse</strong></figcaption></figure><h3>Practices</h3><p>Practices are the <em>day-to-day activities</em> that teams engage in. They are <em>situation-dependent</em>. If the situation changes, you choose different practices to meet those conditions. [5]</p><p>XP practices are interrelated, and the interactions between them amplify their effect.</p><p>See also: <a href="https://ootips.org/xp.html"><strong>Extreme Programming Practices</strong></a> [Kent Beck], <a href="https://en.wikipedia.org/wiki/Extreme_programming_practices"><strong>Extreme Programming Practices</strong></a> [Wikipedia], <a href="https://wiki.c2.com/?ExtremeProgrammingCorePractices"><strong>Extreme Programming Core Practices</strong></a></p><h3>Primary Practices</h3><p>The primary practices are useful independent of what else you are doing. They each can give you immediate improvement. You can start safely with any of them. Which one you should use first depends completely on your environment and what you perceive as your biggest opportunity for improvement. [5][6]</p><h4>Sit Together</h4><blockquote>Develop in an <strong>open space big enough for the whole team</strong>.<em> [6]</em></blockquote><p>This is nearly identical to the concept of <strong>Co-location</strong> in Scrum and its post-COVID-19 adapted version, <strong>Virtual Team Space</strong>.</p><p>Antipatterns: <strong>Cubicles</strong></p><p>Related patterns: <strong>Team Space</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4>Whole Team</h4><blockquote>Include on the team people with all the <strong>skills</strong> and <strong>perspectives</strong> necessary for the project to <strong>succeed</strong>.<em> [6]</em></blockquote><p>This is, in theory, identical to <strong>Cross-functionality </strong>in Scrum. However, in practice, Scrum teams only include the technical functions, and <em>business</em> and <em>customer</em> are often proxied by the <em>Product Owner</em>. XP emphasizes <strong>Real Customer Involvement</strong>.</p><p>Antipatterns: <strong>Too Large Teams</strong>, <strong>Fractional Team Members</strong></p><p>Related patterns: <strong>Business + Development</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>], <strong>Scrum Team</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>]</p><h4>Informative Workspace</h4><blockquote>Make your workspace about your work. Use your space for <strong>important, active information</strong>.<em> [6]</em></blockquote><p>Related pattern: <strong>Scrum Artifacts</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>], <strong>Team Space</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-software-teaming-21a574ba46e7">Software Teaming</a>]</p><h4>Energized Work</h4><blockquote>Work only as many hours as you can be <strong>productive</strong> and only as many hours as you can <strong>sustain</strong>.<em> [6]</em></blockquote><p>Related patterns: <strong>Sustainable Pace</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>], <strong>Rhythm</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-modern-synthesis-b1e3b61ba3c1">Modern Synthesis</a>]</p><h4>Pair Programming</h4><blockquote>Write all production programs with <strong>two people sitting at one machine</strong>.<em> [6]</em></blockquote><p>See also: <a href="https://wiki.c2.com/?PairProgramming"><strong>Pair Programming</strong></a> [C2 Wiki], <a href="https://en.wikipedia.org/wiki/Pair_programming"><strong>Pair-Programming</strong></a> [Wikipedia]</p><h4>Stories</h4><blockquote>Plan using units of customer-visible functionality.<em> [6]</em></blockquote><p>Related patterns: <strong>User Story</strong>, <strong>Estimation</strong>, <strong>Spike</strong>, <strong>Story Wall</strong></p><p>See also: <a href="http://wiki.c2.com/?UserStory"><strong>User Story</strong></a> [C2 Wiki], <a href="https://ronjeffries.com/xprog/articles/expcardconversationconfirmation/"><strong>Card, Conversation, Confirmation</strong></a> [Ron Jeffries]</p><h4>Weekly Cycle</h4><blockquote><strong>Plan</strong> work <strong>a week</strong> at a time.<em> [6]</em></blockquote><p>Related pattern: <strong>Sprint</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-scrum-794b282666cf">Scrum</a>]</p><h4>Quarterly Cycle</h4><blockquote><strong>Plan</strong> work <strong>a quarter</strong> at a time.<em> [6]</em></blockquote><p>Related patterns: <strong>Theme</strong></p><p>See also: <a href="http://wiki.c2.com/?ExtremePlanning"><strong>Extreme Planning</strong></a>, <a href="http://wiki.c2.com/?PlanningGame"><strong>Planning Game</strong></a></p><h4>Slack</h4><blockquote>In any <strong>plan</strong>, include some minor tasks that <strong>can be dropped</strong> if you get behind.<em> [6]</em></blockquote><p>Related patterns: <strong>Geek Week</strong>, <strong>Hack Days</strong>, <strong>20% Capacity</strong></p><h4>Ten-Minute Build</h4><blockquote><strong>Automatically</strong> build the <strong>whole system</strong> and run all of the <strong>tests</strong> in <strong>ten minutes</strong>.<em> [6]</em></blockquote><h4>Continuous Integration (CI)</h4><blockquote><strong>Integrate and test changes</strong> after no more than a couple of hours.<em> [6]</em></blockquote><p>I wonder if Beck was formalizing these practices today, would he replace this one with — or promote it to — <a href="https://en.wikipedia.org/wiki/Continuous_delivery"><strong>Continuous Delivery (CD)</strong></a> already?</p><p>See also: <a href="http://wiki.c2.com/?ContinuousIntegration"><strong>Continuous Integration</strong></a> [C2 Wiki], <a href="https://en.wikipedia.org/wiki/Continuous_integration"><strong>Continuous Integration</strong></a> [Wikipedia]</p><h4>Test-First Programming</h4><blockquote>Write a failing <strong>automated test</strong> before changing any code.<em> [6]</em></blockquote><p>See also: <a href="https://wiki.c2.com/?TestDrivenDevelopment"><strong>Test Driven Development</strong></a> [C2 Wiki], <a href="https://en.wikipedia.org/wiki/Test-driven_development"><strong>Test-Driven Development</strong></a> [Wikipedia], <a href="https://wiki.c2.com/?ProgrammerTest"><strong>Programmer Test</strong></a>, <a href="https://wiki.c2.com/?DeveloperTest"><strong>Developer Test</strong></a>, <a href="https://wiki.c2.com/?UnitTest"><strong>Unit Test</strong></a>, <a href="https://wiki.c2.com/?AcceptanceTest"><strong>Acceptance Test</strong></a>, <a href="https://wiki.c2.com/?FunctionalTest"><strong>Functional Test</strong></a>, <a href="https://wiki.c2.com/?CustomerTest"><strong>Customer Test</strong></a>, <a href="https://en.wikipedia.org/wiki/Continuous_testing"><strong>Continuous Testing</strong></a></p><h4>Incremental Design</h4><blockquote><strong>Invest</strong> in the design of the system <strong>every day</strong>. Strive to make the design of the system an excellent <strong>fit for the needs</strong> of the system that day.<em> [6]</em></blockquote><p>Related pattern: <strong>Technical Excellence</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><p>See also: <a href="https://en.wikipedia.org/wiki/Code_refactoring"><strong>Code Refactoring</strong></a>, <a href="http://wiki.c2.com/?WhatIsRefactoring"><strong>What Is Refactoring</strong></a>, <a href="http://wiki.c2.com/?ReFactor"><strong>Re Factor</strong></a>, <a href="http://wiki.c2.com/?RefactorMercilessly"><strong>Refactor Mercilessly</strong></a>, <a href="https://refactoring.com/"><strong>refactoring.com</strong></a></p><h3>Corollary Practices</h3><blockquote>The corollary practices are likely to be difficult or even dangerous without first mastering the primary practices.<em> [5][7]</em></blockquote><h4>Real Customer Involvement</h4><blockquote>Make people whose lives and business are <strong>affected</strong> by your system <strong>part of the team</strong>.<em> [7]</em></blockquote><p>Related Pattern: <strong>Customer Collaboration</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h4>Incremental Deployment</h4><blockquote>When replacing a legacy system, <strong>gradually</strong> take over its workload beginning very <strong>early in the project</strong>.<em> [7]</em></blockquote><h4>Team Continuity</h4><blockquote><strong>Keep</strong> effective teams <strong>together</strong>.<em> [7]</em></blockquote><p>This relates to <strong>Stable Teams</strong> as suggested in Scrum and most Agile approaches, and is challenged by <strong>Fluid Teams </strong>as suggested in FAST.</p><h4>Shrinking Teams</h4><blockquote>As a team grows in <strong>capability</strong>, keep its <strong>workload</strong> constant but gradually reduce its <strong>size</strong>.<em> [7]</em></blockquote><h4>Root-Cause Analysis</h4><blockquote>Every time a defect is found after development, <strong>eliminate the defect and its cause</strong>.<em> [7]</em></blockquote><h4>Shared Code</h4><blockquote><strong>Anyone on the team</strong> can improve <strong>any part of the system</strong> at any time.<em> [7]</em></blockquote><p>See also: <a href="http://wiki.c2.com/?CollectiveCodeOwnership"><strong>Collective Code Ownership</strong></a>, <a href="http://wiki.c2.com/?FormalStandards"><strong>Coding Standard</strong></a>, <a href="http://wiki.c2.com/?SystemMetaphor"><strong>System Metaphor</strong></a></p><h4>Code &amp; Tests</h4><blockquote>Maintain only the <strong>code</strong> and the <strong>tests</strong> as <strong>permanent artifacts</strong>.<em> [7]</em></blockquote><h4>Single Code Base</h4><blockquote>There is only <strong>one code stream</strong>.<em> [7]</em></blockquote><h4>Daily Deployment</h4><blockquote>Put new software <strong>into production</strong> every night.<em> [7]</em></blockquote><p>This concept was taken even further with <strong>Continuous Deployment</strong>.</p><p>See also: <a href="https://en.wikipedia.org/wiki/Continuous_delivery"><strong>Continuous Delivery</strong></a>, <a href="https://en.wikipedia.org/wiki/Continuous_deployment"><strong>Continuous Deployment</strong></a> [Wikipedia], <a href="http://timothyfitz.com/2009/02/08/continuous-deployment/"><strong>Continuous Deployment</strong></a> [Timothy Fitz], <a href="http://timothyfitz.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/"><strong>Continuous Deployment at IMVU</strong></a>, <a href="https://www.industriallogic.com/blog/benefits-continuous-deployment/"><strong>Benefits of Continuous Deployment</strong></a></p><h4>Negotiated Scope Contract</h4><blockquote>Write contracts for software development that <strong>fix time, costs, and quality</strong> but call for an <strong>ongoing negotiation of the precise scope of the system</strong>.<em> [7]</em></blockquote><p>Related Pattern: <strong>Customer Collaboration</strong> [<a href="https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86">Manifesto</a>]</p><h4>Pay-Per-Use</h4><blockquote>With pay-per-use systems, you <strong>charge for every time the system is used</strong>.<em> [7]</em></blockquote><h3>Beyond XP</h3><p>XP’s influence did not stop at the <em>XP Series</em> books. Similar to XP’s evolution visible through the C2 Wiki pages, and the first and second editions of Extreme Programming Explained, it has continued to evolve and even mutate, albeit by individuals other than its originators.</p><p><a href="https://www.geepawhill.org/about/">Mike “GeePaw” Hill</a>’s <a href="https://www.geepawhill.org/category/modern-synthesis/"><strong>Modern Synthesis</strong></a> is like a wrapper around XP that adds some elements to it without changing its original purpose. His <a href="https://www.geepawhill.org/tag/podcast/">podcast</a> and articles are a treasure trove.</p><p><a href="https://www.industrialxp.org/"><strong>Industrial XP (IXP)</strong></a> is an adaptation of XP for the larger organization and value stream.</p><p><a href="https://www.linkedin.com/in/woodyzuill/">Woody Zuill</a>’s <a href="https://softwareteaming.com/"><strong>Software Teaming</strong></a> (AKA <strong>Mob Programming</strong> and <strong>Ensemble Programming</strong>) is the closest thing to a mutation of XP. It does not look that much like XP anymore, but XP is the closest thing to a predecessor to it. The book and all the content by Woody are invaluable.</p><h3>Your Feedback</h3><p>If you have comments or suggestions, please do not hesitate to express them here in the comments or message me directly on <a href="https://www.linkedin.com/in/aria-omidvar/">LinkedIn</a>. I welcome all kinds of commentary, ideas, and chats on the topic.</p><p>[1] <a href="https://www.youtube.com/watch?v=6vMO3XmNXe4"><strong>I Know Kung Fu</strong></a>, <a href="https://www.imdb.com/title/tt0133093/">The Matrix</a>, 1999<br>[2] <strong>Extreme Programming Explained</strong>, 2nd edition, 2004, Kent Beck<br>[3] Chapter 4: Values, <strong>Extreme Programming Explained</strong>, 2nd edition<br>[4] Chapter 5: Principles, <strong>Extreme Programming Explained</strong>, 2nd edition<br>[5] Chapter 6: Practices, <strong>Extreme Programming Explained</strong>, 2nd edition<br>[6] Chapter 7: Primary Practices, <strong>Extreme Programming Explained</strong>, 2nd edition<br>[7] Chapter 9: Corollary Practices, <strong>Extreme Programming Explained</strong>, 2nd edition</p><h3>Literature</h3><p>Here is a list of all <em>XP Series</em> books, accompanied by closely related books that are now recognized as the XP body of literature.</p><ul><li><a href="https://www.oreilly.com/library/view/extreme-programming-explained/0201616416/"><strong>Extreme Programming Explained</strong></a>, 1st edition, 1999, <a href="https://en.wikipedia.org/wiki/Kent_Beck">Kent Beck</a></li><li><a href="https://www.oreilly.com/library/view/extreme-programming-explained/0321278658/"><strong>Extreme Programming Explained</strong></a>, 2nd edition, 2004, <a href="https://en.wikipedia.org/wiki/Kent_Beck">Kent Beck</a>, Cynthia Andres</li><li><a href="https://www.oreilly.com/library/view/extreme-programming-installed/0201708426/"><strong>Extreme Programming Installed</strong></a>, 2000, <a href="https://en.wikipedia.org/wiki/Ron_Jeffries">Ron Jeffries</a>, Ann Anderson, <a href="https://www.linkedin.com/in/chet-hendrickson-94a2bb/">Chet Hendrickson</a></li><li><a href="https://www.oreilly.com/library/view/planning-extreme-programming/0201710919/"><strong>Planning Extreme Programming</strong></a>, 2000, <a href="https://en.wikipedia.org/wiki/Kent_Beck">Kent Beck</a>, <a href="https://en.wikipedia.org/wiki/Martin_Fowler_(software_engineer)">Martin Fowler</a></li><li><a href="https://books.google.de/books/about/Extreme_Programming_Applied.html?id=JHtxQgAACAAJ&amp;redir_esc=y"><strong>Extreme Programming Applied</strong></a>, 2002, <a href="https://www.linkedin.com/in/kenauer/">Ken Auer</a>, <a href="https://www.linkedin.com/in/roy-miller-51390512/">Roy Miller</a></li><li><strong>Extreme Programming Explored</strong>, 2002, <a href="https://www.linkedin.com/in/william-wake/">William C. Wake</a></li><li><a href="https://books.google.de/books/about/Extreme_Programming_for_Web_Projects.html?id=BGMk5f4tMHUC&amp;redir_esc=y"><strong>Extreme Programming for Web Projects</strong></a>, 2002, Doug Wallace, Isobel Raggett, Joel Aufgang</li><li><a href="https://books.google.de/books?id=LRQhdlrKNE8C&amp;redir_esc=y"><strong>Pair Programming Illuminated</strong></a>, 2002, <a href="https://www.linkedin.com/in/laurieawilliams/">Laurie Williams</a>, Robert Kessler</li><li><a href="https://books.google.de/books/about/Testing_Extreme_Programming.html?hl=de&amp;id=eTREaOEImsgC&amp;redir_esc=y"><strong>Testing Extreme Programming</strong></a>, 2003, <a href="https://www.linkedin.com/in/lisacrispin/">Lisa Crispin</a>, Tip House</li><li><a href="https://books.google.de/books/about/Extreme_Programming_Perspectives.html?id=ZqNQAAAAMAAJ&amp;redir_esc=y"><strong>Extreme Programming Perspectives</strong></a>, 2003, <a href="https://www.linkedin.com/in/michele-marchesi-9b35151/">Michele Marchesi</a>, <a href="https://www.linkedin.com/in/giancarlosucci/">Giancarlo Succi</a>, <a href="https://www.linkedin.com/in/don-wells-93a7585/">Don Wells</a>, <a href="https://www.linkedin.com/in/laurieawilliams/">Laurie Williams</a></li><li><a href="https://www.oreilly.com/library/view/test-driven-development/0321146530/"><strong>Test Driven Development By Example</strong></a>, 2003, <a href="https://en.wikipedia.org/wiki/Kent_Beck">Kent Beck</a></li><li><a href="https://www.jamesshore.com/v2/books/aoad1"><strong>The Art of Agile Development</strong></a>, 1st edition, 2008, <a href="https://www.linkedin.com/in/jdlshore/">James Shore</a>, Shane Warden</li><li><a href="https://www.jamesshore.com/v2/books/aoad2"><strong>The Art of Agile Development</strong></a>, 2nd edition, 2021, <a href="https://www.linkedin.com/in/jdlshore/">James Shore</a>, <a href="https://www.linkedin.com/in/dianalarsenagileswd/">Diana Larsen</a>, <a href="https://www.linkedin.com/in/gitteklitgaard/">Gitte Klitgaard</a>, Shane Warden</li></ul><h3>Articles</h3><ul><li><a href="https://web.archive.org/web/20061215120657/http://www.xprogramming.com/xpmag/whatisxp.htm"><strong>What is Extreme Programming?</strong></a>, 2001, <a href="https://en.wikipedia.org/wiki/Ron_Jeffries">Ron Jeffries</a></li><li><a href="https://martinfowler.com/articles/on-pair-programming.html"><strong>On Pair Programming</strong></a>, <a href="https://birgitta.info/">Birgitta Böckeler</a>, <a href="https://sssggr.net/">Nina Siessegger</a></li><li>Modern Agile’s <a href="https://modernagile.org/#cheatsheets"><strong>Evolutionary Design</strong></a> Cheat Sheet</li></ul><h3>Websites</h3><ul><li><a href="https://wiki.c2.com/?ExtremeProgramming"><strong>Extreme Programming</strong></a> [C2 Wiki]</li><li><a href="https://wiki.c2.com/?ExtremeProgrammingRoadmap"><strong>Extreme Programming Roadmap</strong></a> [C2 Wiki]</li><li><a href="http://www.extremeprogramming.org/"><strong>Extreme Programming: A Gentle Introduction</strong></a>, <a href="https://www.linkedin.com/in/don-wells-93a7585/">Don Wells</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3f52414499f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hitchhiker’s Guide to Hexiverse — Agile Manifesto]]></title>
            <link>https://medium.com/@omidvar.aria/the-hitchhikers-guide-to-the-independent-hexiverse-part-2-agile-manifesto-51c3119add86?source=rss-c98461c29fda------2</link>
            <guid isPermaLink="false">https://medium.com/p/51c3119add86</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-manifesto]]></category>
            <dc:creator><![CDATA[Aria Omidvar]]></dc:creator>
            <pubDate>Sat, 09 Aug 2025 17:51:43 GMT</pubDate>
            <atom:updated>2026-03-10T16:47:36.222Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Hitchhiker’s Guide to Hexiverse — Agile Manifesto</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1oWngZJzsaHuxsRjuhLR1A.png" /><figcaption><strong>Agile Manifesto </strong>from <strong>Hexiverse</strong></figcaption></figure><p>In this article, I suggest a Hexi set for the <a href="https://agilemanifesto.org/"><strong>Manifesto for Agile Software Development</strong></a> and expand on each Hexi. The corresponding Hexi set can be found <a href="https://miro.com/app/board/uXjVKv84GGU=/?moveToWidget=3458764607403112698&amp;cot=14"><strong>here</strong></a>.</p><h3>An Agile Alliance</h3><p>In 2001, an event was organized with the intention of bringing together competing lightweight process advocates to find common ground and form a unity. Seventeen of the invitees attended that<em> Light Weight Process Summit</em>. <a href="https://en.wikipedia.org/wiki/Ward_Cunningham">Ward Cunningham</a>, <a href="https://en.wikipedia.org/wiki/Kent_Beck">Kent Beck</a>, and <a href="https://en.wikipedia.org/wiki/Ron_Jeffries">Ron Jeffries</a> represented Extreme Programming (XP). <a href="https://en.wikipedia.org/wiki/Ken_Schwaber">Ken Schwaber</a>, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a>, and <a href="https://en.wikipedia.org/wiki/Mike_Beedle">Mike Beedle</a> represented Scrum. <a href="https://en.wikipedia.org/wiki/Andy_Hunt_(author)">Andy Hunt</a> and <a href="https://en.wikipedia.org/wiki/Dave_Thomas_(programmer)">Dave Thomas</a> had co-authored <em>The Pragmatic Programmer</em>. <a href="https://en.wikipedia.org/wiki/Jim_Highsmith">Jim Highsmith</a> represented Adaptive Software Development (ASD). <a href="https://en.wikipedia.org/wiki/Alistair_Cockburn">Alistair Cockburn</a> represented Crystal. <a href="https://www.linkedin.com/in/jonkern/">Jon Kern</a> represented Feature Driven Development (FDD). <a href="https://leanpub.com/u/marick">Brian Marick</a> represented the software testing community. <a href="https://www.linkedin.com/in/ariev3/">Arie van Bennekum</a> represented the not-so-lightweight Dynamic Systems Development Method (DSDM). <a href="https://en.wikipedia.org/wiki/Stephen_J._Mellor">Steve Mellor</a> was another unlikely participant representing the Shlaer–Mellor Method. <a href="https://en.wikipedia.org/wiki/Martin_Fowler_(software_engineer)">Martin Fowler</a>, <a href="https://www.linkedin.com/in/jwgrenning/">James Grenning</a>, and <a href="https://en.wikipedia.org/wiki/Robert_C._Martin">Robert C. Martin</a> were attendees with no affiliation to a single approach. The Agile Manifesto was the result.</p><p>Over two decades later, the Agile Manifesto is sometimes criticized for its shortcomings in answering the needs that it was not even intended for, or at the other end of the spectrum, it is treated as absolute, timeless, and universal. These misconceptions can only be resolved by understanding the historical context of the Manifesto and its creators.</p><p>To put it most shortly, the Manifesto addressed the issues that its authors were facing at that time, namely delivering software projects in a timely manner, within a reasonable budget, and to the satisfaction of customers’ needs. It is also essential to mention that the gathering of the seventeen was an effort to build an <em>alliance</em> against the status quo of their industry, which was failing to deliver on its promises while ignoring them and their successful though unconventional approaches. The Manifesto was synonymous with the birth of David, an insignificant opponent to the Goliath of academia and industry of their time. Literally every sentence in the Manifesto should be looked at from this point of view. In this sense, the Manifesto could also be dubbed the <em>Manifesto of Not Failing in Software Development by the Conventional Approaches</em>.</p><p>An often-overlooked yet intriguing fact about the Manifesto is that it was a <em>collective</em> effort, and no part of it can be attributed to any <em>individual</em>. This seems to be an unspoken and unbroken agreement among the seventeen.</p><p>For authentic and thorough accounts of the event, the intentions behind it, and the expectations from it, I suggest seeing Alistair Cockburn’s Agile Software Development [1] and Robert Martin’s Clean Agile [2]. More recently, Jim Highsmith authored a book [3] on the larger context of the Agile movement as well.</p><p>In conclusion, the Manifesto, although a product of its time, still offers a great foundation for other methods and approaches to build upon. The Hexi approach makes this combining and blending very easy.</p><p>What follows are the Hexis that I suggest for the Manifesto. Keep in mind that these elements are interconnected and do not bear much fruit if applied in isolation.</p><h3>Individuals &amp; Interactions</h3><blockquote><strong>Individuals &amp; Interactions</strong> over processes and tools</blockquote><p>This was perhaps the most outlandish, the most mysterious, and the most mystical claim of the Manifesto. This value is, in my personal opinion, the least comprehended one as well; not because of lack of intelligence but merely because it is still unfolding and revealing itself in ways that the seventeen did not expect or fully imagined at the time.</p><p><em>Individuals and interactions</em> is the strongest statement of the <em>rebellion</em> against the <em>empire</em> of heavyweight, sophisticated, overly-prescriptive, rigid, predictive methods of the time that claimed knowledge of the <em>unknown</em> or even the <em>unknowable</em>. The Alliance knew, through experience, that processes and tools can not be the primary factors and that focusing instead on individuals and interactions yields far better results in the domain of software development.</p><p>For more clarity: processes and tools are always useful, but putting them at the center of our frame of work not only results in belittling and underestimating individuals to mere agents of the process, or cogs in the machine, but also minimizes the one factor that is the most essential in the ever-changing, complex, and not-so-knowable domain of software product development in the fast-paced markets of our time.</p><h3>Working Software</h3><blockquote><strong>Working Software</strong> over comprehensive documentation</blockquote><p>Also…</p><blockquote>Deliver <strong>working software</strong> frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.</blockquote><p>And…</p><blockquote><strong>Working software</strong> is the primary measure of progress.</blockquote><p><em>Working software</em> was an antidote to the dominant <a href="https://en.wikipedia.org/wiki/Phase-gate_process">phase-gate</a> and <a href="https://en.wikipedia.org/wiki/Waterfall_model">waterfall</a> approaches of the time, where work was departmentalized and the output of each phase was handed over to the next, accompanied by mountains of documentation. The deadly assumptions of these approaches were knowing what the customer wants, each department being able to deliver their part of the project in isolation, the input and output of each phase being clear and sufficient, market and customer needs not changing by the end of the project, and many more.</p><p><em>Working software</em> was the only way to overcome those illusions through making <a href="https://en.wikipedia.org/wiki/Vertical_slice">vertical slices</a> of the known part of the project, developing and delivering <em>iteratively and incrementally</em>, minimizing handoffs and loss of information, maximizing learning, and, most importantly, minimizing all manners of risk associated with the project.</p><h3>Customer Collaboration</h3><blockquote><strong>Customer Collaboration</strong> over contract negotiation</blockquote><p>Prioritizing <em>customer collaboration</em> over contract negotiation was also redefining the rules of the game to fit the nature of the game. Predictive approaches claimed the ability to estimate the work and hence offering a fair contract. As a result, contract negotiation was a central part of the business of these software shops. The seventeen knew that estimating the entire project in terms of effort, time, resources, and such was virtually impossible. That would not be too terrible if the downside were still marginal. However, our contemporary history is filled with numerous accounts of software projects and even projects of entirely different industries that turn out to cost double, triple, or even larger amounts of investment than initially predicted.</p><p>Prioritizing <em>customer collaboration</em> was an antidote to that grave problem. It entailed involving the customer in the process, giving frequent progress reports and demonstrations, letting the customer decide the direction of the upcoming developments, and in this way, transforming the need for in-advance negotiations into constant engagement of the customer for their advantage and satisfaction.</p><p><em>Customer collaboration</em>, of course, has even more beneficial effects, such as better understanding the problem space and offering a more effective solution, detecting miscommunicated and misunderstood needs earlier, and handing the power to steer the project to the customer to prioritize their more pressing needs.</p><h3>Welcoming Change</h3><blockquote><strong>Responding to Change</strong> over following a plan</blockquote><p>And…</p><blockquote>Welcome <strong>changing requirements</strong>, even late in development. Agile processes <strong>harness change</strong> for the customer’s <strong>competitive advantage</strong>.</blockquote><p><em>Welcoming change</em> was perhaps the most significant differentiator of Agile approaches from their <em>heavyweight</em> counterparts. The <em>Alliance</em> already knew that the nature of software development was less <em>deterministic</em> and <em>predictable</em> and more <em>emergent</em>, and that their approaches needed to be more <em>adaptive</em> than <em>predictive</em>. As well, their methods not only survived better in ever-changing environments but also utilized them to their advantage. Welcoming change was also, in a sense, acknowledging and embracing <a href="https://en.wikipedia.org/wiki/VUCA"><strong>VUCA</strong></a>.</p><h3>Early &amp; Continuous Delivery of Value</h3><blockquote>Our highest priority is to <strong>satisfy the customer</strong> through <strong>early and continuous delivery</strong> of <strong>valuable software</strong>.</blockquote><p>Unlike the waterfall approaches that would not deliver any tangible value to the customer until the end of long periods, Agile methods saw it essential to deliver <em>valuable software</em> as early and as frequently as possible. This way, they could…</p><ul><li>make sure they are building the right thing and course correct early and cheaply if not,</li><li>understand customers’ needs better due to having an actual running software where users could understand their own needs better,</li><li>enable customers to benefit from the already-developed functionalities of the software solution,</li></ul><p>and more.</p><p>Once again, <em>valuable software</em> depended on <em>vertical slices</em> [4] of the known part of the project, and developing and delivering them <em>iteratively and incrementally</em>.</p><p>It is important to mention that the Manifesto predates all formalizations of <em>Product Discovery</em>, <em>Continuous Discovery</em>, <em>Product-led</em>, <em>Product-first</em>, the <em>Product Operating Model</em>, and generally, what today is often referred to as <em>Product Thinking</em>. Most of these software shops were developing custom-made software solutions for specific customers with specific needs. The <em>age of product</em> had not arrived yet, and <em>early &amp; continuous delivery of value</em> was sufficient for their needs and purposes.</p><h3>Simplicity</h3><blockquote><strong>Simplicity</strong> — the art of maximizing the amount of work not done — is essential.</blockquote><p>I think this tenet would not appear in the Manifesto if its authors were not software developers and craftspeople. It is in the craft of software development that the tendency to over-prepare and over-design was already recognized, and its remedy, <em>simplicity</em>, was also commonly accepted.</p><p>See also: <a href="https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it"><strong>YAGNI</strong></a></p><h3>Technical Excellence</h3><blockquote><strong>Continuous</strong> attention to <strong>technical excellence</strong> and <strong>good design</strong> enhances agility.</blockquote><p><em>Technical excellence</em> was central to many in the <em>alliance</em>. Extreme Programming (XP) emphasized them, and Refactoring [5] and Pragmatic Programming [6] were already known practices and had corresponding literature. Dominance of Scrum in the years after the Manifesto, however, is often recognized as the reason that <em>technical excellence</em> lost its importance, became subject to negligence, and resulted in the suffering of software projects.</p><p><em>Technical excellence</em> remained central and was protected among the XP community. Robert Martin’s Clean Code [7] later became synonymous with ‘good code’, and Emily Bache’s Samman Method [8] may be the first formalized method of coaching <em>technical excellence</em>.</p><h3>Face-to-face Interactions</h3><blockquote>The most efficient and effective method of <strong>conveying information</strong> to and within a development team is <strong>face-to-face conversation</strong>.</blockquote><p><em>Face-to-face interaction</em> was also a principle that recognized and acknowledged the ambiguity of human communication and defied the document-oriented, requirement-based approach of the <em>mechanical</em> methods.</p><p>At the time, remote face-to-face interactions were not common enough, so the Manifesto’s <em>“face-to-face conversation”</em> was not explicitly about in-person interactions. The COVID pandemic made remote interactions commonplace, and its challenges and advantages have been researched and discussed ever since.</p><h3>Business + Development</h3><blockquote><strong>Business people</strong> and <strong>developers</strong> must work together <strong>daily</strong> throughout the project.</blockquote><p>Does it ring a bell? No handoffs? No throwing requests over the wall? No running around to get the hang of someone who has the answer to a question? Yep. That is exactly what this principle means.</p><h3>Motivated Individuals</h3><blockquote>Build <strong>projects</strong> around <strong>motivated individuals</strong>. Give them the <strong>environment and support</strong> they need, and <strong>trust</strong> them to get the job done.</blockquote><p>The simple fact that this principle turned the common practice of the time on its head makes it historically significant. Unfortunately, over two decades later, we still go behind closed doors, choose what needs to be done and in what order, handpick individuals who are to be assigned to the work, and in the end, kindly ask them to go and be an ‘empowered’ team and get it done. In 2001, they all knew that for such efforts to succeed, they needed to be built around the individuals and not the other way around.</p><p>I also want to emphasize <em>motivation</em>. I find it astounding that they included it in this phrase. I have a personal and perhaps controversial opinion on the subject. I believe work environments are able to improve the level of motivation in individuals. Dan Pink’s Drive [9] provides incredible evidence for that. However, I also believe that not all individuals will have the same amount of motivation and passion towards their work, no matter how nurturing the environment. There have always been and there will always be those who treat their professions way beyond a job or even a career. For them, this is their calling, their vocation. I believe distinguishing these <em>highly</em> motivated individuals and investing in them pays dividends beyond imagination.</p><p>See also: <a href="https://en.wikipedia.org/wiki/Drive:_The_Surprising_Truth_About_What_Motivates_Us"><strong>Drive</strong></a>, <a href="https://www.geepawhill.org/series/ramps/"><strong>RAMPS</strong></a></p><h3>Support &amp; Trust</h3><blockquote>Build <strong>projects</strong> around <strong>motivated individuals</strong>. Give them the <strong>environment and support</strong> they need, and <strong>trust</strong> them to get the job done.</blockquote><p>This element, more than anything, reminds me of the <em>aligned autonomy</em> characteristic of Spotify’s <em>squads</em> [10][11]. There is so much to be said about an <em>environment of support &amp; trust</em> and how essential it is in combination with <em>motivated individuals</em>, and <em>self-organizing teams</em>.</p><h3>Self-Organizing Teams</h3><blockquote>The best architectures, requirements, and designs emerge from <strong>self-organizing teams</strong>.</blockquote><p>Self-organization is often defined as teams having autonomy over <em>how</em> they deliver their work or <em>how</em> they get the job done. According to this definition, the <em>what</em> of work is defined outside the team, most likely through product or strategy. I believe this notion is also widened through time. For instance, it has always been the case that the teams know <em>what</em> things need to be done before features and functionalities can be implemented. But more recently, Marty Cagan has been a strong proponent of teams also being a defining factor of <em>what</em> features and functionalities need to be delivered. In his view, “engineers are typically the best single source of innovation” [12]. <em>Self-organization</em> is a manifestation of <em>autonomy</em> and can be expanded beyond the <em>how</em> to the <em>what</em> and even the <em>why</em>.</p><h3>Continuous Improvement</h3><blockquote>At <strong>regular intervals</strong>, the team <strong>reflects</strong> on how to become more <strong>effective</strong>, then <strong>tunes and adjusts</strong> its behavior accordingly.</blockquote><p>This principle is often referred to as <em>Agile Retrospectives</em> or simply <em>Retrospectives</em> today, and has been the subject of several excellent books. The concept behind it is that when a group of individuals becomes a <em>team</em>, working collaboratively and as one unit towards a common goal, then they can improve the way they work within themselves, with the larger organization, and with external entities by reflecting on them, finding ways to improve, and taking ownership of those improvements.</p><p>See also: <a href="https://en.wikipedia.org/wiki/Kaizen"><strong>Kaizen</strong></a>, <a href="https://en.wikipedia.org/wiki/PDCA"><strong>PDCA</strong></a></p><h3>Sustainable Pace</h3><blockquote>Agile processes promote <strong>sustainable development</strong>. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.</blockquote><p>This principle is widely accepted, if not respected, in our time. I know of only one more advanced version of it, suggested by Mike “GeePaw” Hill. In his formalization of <em>Rhythm</em>, he suggests it as <em>sequences of alternating tension and release</em>. I believe his notion adds more nuance to sustainable pace and is more consistent with the natural patterns of workload in reality.</p><p>See also: <a href="https://www.geepawhill.org/2017/09/09/rhythm-as-urgency-the-r-in-ramps/"><strong>Rhythm as Urgency</strong></a></p><h3>Possible Modifications</h3><p>This Hexi set is only one of the possible Hexi sets to be created based on the Manifesto. I can imagine that for different users, it can be modified, expanded, or even condensed. For instance, <em>Competitive Advantage</em>, <em>Valuable Software</em>, <em>Good Design</em>, and <em>Environment</em> are some extended Hexis I imagine useful for different users with certain contexts and needs. You can extend this set as you see fit for your purposes.</p><h3>Your Feedback</h3><p>If you have comments or suggestions, please do not hesitate to express them here in the comments or message me directly on <a href="https://www.linkedin.com/in/aria-omidvar/">LinkedIn</a>. I welcome all kinds of commentary, ideas, and chats on the topic.</p><h3>Special Thanks</h3><p>I am grateful to <a href="https://www.linkedin.com/in/alistaircockburn/"><strong>Alistair Cockburn</strong></a> for his insightful feedback on this guide.</p><p>[1] Appendix A, <strong>Agile Software Development</strong>, 2002, <a href="https://www.linkedin.com/in/alistaircockburn/">Alistair Cockburn</a><br>[2] Chapter 1, <strong>Clean Agile: Back to Basics</strong>, 2019, <a href="https://www.linkedin.com/in/robert-martin-7395b0/">Robert C. Martin</a><br>[3] <a href="http://jimhighsmith.com/wild-west-to-agile-book/"><strong>Wild West to Agile</strong></a>, 2023, <a href="https://www.linkedin.com/in/jhighsmith/">Jim Highsmith</a><br>[4] See also: <a href="https://www.linkedin.com/in/antonskornyakov/">Anton Skornyakov</a> deep dives into this particular topic in his book <a href="https://slicingwork.com/"><strong>The Art of Slicing Work (2024)</strong></a> and his HBR article <a href="https://hbr.org/2025/01/how-project-leaders-can-tame-unpredictability"><strong>How Project Leaders Can Tame Unpredictability</strong></a><a href="https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it"> </a><br>[5] <a href="https://martinfowler.com/books/refactoring.html"><strong>Refactoring</strong></a>, 1999, <a href="https://en.wikipedia.org/wiki/Martin_Fowler_(software_engineer)">Martin Fowler</a><br>[6] <a href="https://en.wikipedia.org/wiki/The_Pragmatic_Programmer"><strong>The Pragmatic Programmer</strong></a>, 1999, <a href="https://www.linkedin.com/in/pragmaticandy/">Andrew Hunt</a>, <a href="https://en.wikipedia.org/wiki/Dave_Thomas_(programmer)">Dave Thomas</a><br>[7] <a href="https://www.oreilly.com/library/view/clean-code-a/9780136083238/"><strong>Clean Code</strong></a>, 2008, <a href="https://www.linkedin.com/in/robert-martin-7395b0/">Robert C. Martin</a><br>[8] <a href="https://leanpub.com/techagilecoach"><strong>Technical Agile Coaching with the Samman Method</strong></a>, 2021, <a href="https://www.linkedin.com/in/emilybache/">Emily Bache</a><br>[9] <a href="https://en.wikipedia.org/wiki/Drive:_The_Surprising_Truth_About_What_Motivates_Us"><strong>Drive</strong></a>, 2009, <a href="https://en.wikipedia.org/wiki/Daniel_H._Pink">Daniel H. Pink</a><br>[10] <a href="https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf"><strong>Scaling Agile @ Spotify</strong></a>, 2012, <a href="https://www.linkedin.com/in/hkniberg/">Henrik Kniberg</a>, <a href="https://www.linkedin.com/in/aivarsson/">Anders Ivarsson</a><br>[11] <strong>Spotify Engineering Culture</strong>: <a href="https://engineering.atspotify.com/2014/3/spotify-engineering-culture-part-1">part 1</a> and <a href="https://engineering.atspotify.com/2014/9/spotify-engineering-culture-part-2">part 2</a>, <a href="https://www.linkedin.com/in/hkniberg/">Henrik Kniberg</a><br>[12] Chapter 6, <a href="https://www.svpg.com/books/inspired-how-to-create-tech-products-customers-love-2nd-edition/"><strong>Inspired</strong></a>, 2nd edition, 2018, Marty Cagan</p><h3>Books</h3><ul><li><strong>Clean Agile: Back to Basics</strong>, 2019, <a href="https://www.linkedin.com/in/robert-martin-7395b0/">Robert C. Martin</a></li><li><a href="http://jimhighsmith.com/wild-west-to-agile-book/"><strong>Wild West to Agile</strong></a>, 2023, <a href="https://www.linkedin.com/in/jhighsmith/">Jim Highsmith</a></li></ul><h3>Articles</h3><ul><li><a href="https://martinfowler.com/articles/agileStory.html"><strong>Writing The Agile Manifesto</strong></a>, 2006, <a href="https://en.wikipedia.org/wiki/Martin_Fowler_(software_engineer)">Martin Fowler</a></li><li><a href="https://pragdave.me/thoughts/active/2007-02-24-some-agile-history.html"><strong>Some Agile History</strong></a>, 2007, <a href="https://en.wikipedia.org/wiki/Dave_Thomas_(programmer)">Dave Thomas</a></li><li><a href="https://sites.google.com/site/unclebobconsultingllc/the-founding-of-the-agile-alliance"><strong>The Founding of the Agile Alliance</strong></a>, 2007, <a href="https://www.linkedin.com/in/robert-martin-7395b0/">Robert C. Martin</a></li><li><a href="https://ronjeffries.com/xprog/articles/beyond-agile-new-principles/"><strong>Beyond Agile: New Principles?</strong></a>, 2010, Ron Jeffries</li><li><a href="https://holub.com/heuristics/"><strong>Heuristics for Effective Organizations</strong></a>, 2021, <a href="https://www.linkedin.com/in/allenholub/">Allen Holub</a></li><li><a href="https://en.wikipedia.org/wiki/Martin_Fowler_(software_engineer)">Martin Fowler</a>’s <a href="https://martinfowler.com/agile.html"><strong>Agile Software Guide</strong></a></li></ul><h3>Videos</h3><ul><li><a href="https://youtu.be/y_uOWMx1D9w"><strong>Agile History by Alistair Cockburn</strong></a> (Solita Helsinki) [YouTube]</li><li><a href="https://www.youtube.com/watch?v=AGdi3zZutXk"><strong>How The Agile Manifesto Came To Be</strong></a>, 2021, <a href="https://en.wikipedia.org/wiki/Jeff_Sutherland">Jeff Sutherland</a> [YouTube]</li><li><a href="https://youtu.be/zNvmjPzdqKc"><strong>A Retake on the Agile Manifesto</strong></a> — GOTO 2014 [YouTube]</li><li><a href="https://www.youtube.com/watch?v=pDtAnrSO83A"><strong>25th Anniversary of Agile Manifesto</strong></a>, 2026 [YouTube]</li><li><a href="https://www.linkedin.com/in/martin-fowler-com/">Martin Fowler</a> and Neal Ford <a href="https://www.youtube.com/watch?v=GE6lbPLEAzc"><strong>Explaining Agile</strong></a></li><li><a href="https://en.wikipedia.org/wiki/Russell_L._Ackoff">Russ Ackoff</a>’s talk on <a href="https://www.youtube.com/watch?v=OqEeIG8aPPk"><strong>Continuous Improvement through the lens of Systems Thinking</strong></a></li></ul><h3>Resources</h3><ul><li><a href="https://www.linkedin.com/in/kerrybuckley/">Kerry Buckley</a>’s <a href="https://www.halfarsedagilemanifesto.org/"><strong>Manifesto for Half-Arsed Agile Software Development</strong></a></li><li><a href="https://en.wikipedia.org/wiki/Alistair_Cockburn">Alistair Cockburn</a>’s <a href="https://heartofagile.com/"><strong>Heart of Agile</strong></a></li><li><a href="https://modernagile.org/"><strong>Modern Agile</strong></a></li><li><a href="https://www.linkedin.com/in/quintonquartel/">Quinton Quartel</a>’s <a href="https://www.agilitymanifesto.org/"><strong>Agility Manifesto</strong></a></li><li><a href="https://docs.google.com/document/d/10YZt7Tv_03r0xDcvRCNApzPfkYg57dLVhv-dt16KyQM/"><strong>Agile Time Machine</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51c3119add86" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>