<?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 Scott Duncan on Medium]]></title>
        <description><![CDATA[Stories by Scott Duncan on Medium]]></description>
        <link>https://medium.com/@scott-duncan?source=rss-74df688fc261------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8ajmEYmg85kxJOKqZr5XKQ.jpeg</url>
            <title>Stories by Scott Duncan on Medium</title>
            <link>https://medium.com/@scott-duncan?source=rss-74df688fc261------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:40:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@scott-duncan/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[Agile is About Two Things: Individuals and Interactions and Delivering Value]]></title>
            <link>https://scott-duncan.medium.com/agile-is-about-two-things-individuals-and-interactions-and-delivering-value-fa0fa0f55826?source=rss-74df688fc261------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa0fa0f55826</guid>
            <category><![CDATA[individeal-interactions]]></category>
            <category><![CDATA[value-delivery]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-manifesto]]></category>
            <category><![CDATA[teams-and-teamwork]]></category>
            <dc:creator><![CDATA[Scott Duncan]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 15:40:58 GMT</pubDate>
            <atom:updated>2026-09-21T15:41:41.648Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/658/1*OnNETcIYmuJyxmfB-Wbe5g.png" /></figure><p>In the Letters to the Editor section of the December, 2001 edition of IEEE <em>Computer,</em> a letter expressed strong concern that Agile ideas would destroy all the effort made during prior years to put discipline into software development. Not too many years after that in various places, articles and posts emerged about how “Agile didn’t work/failed.” Some time later, the focus of articles and posts were that Agile was “dead” or “passé”. Recently there have been more of these two claims. Now the trend seems to be that Agile is “dead” because of AI or that Agile “is” now AI.</p><p>Other than the statement in IEEE <em>Computer</em>, everything else has sounded like the failure/problems could be attributed to an organization’s lack of success with a specific framework. Indeed, many organizations I have had the chance to hear about/from do not seem to have ever sat down with the Manifesto and considered what the values and principles should mean for them. It is for this reason that I cannot agree with the “didn’t work/failed,” “dead,” “passé” or replacement statements.</p><p>While the Agile Manifesto was written focused on software development, from the outset, the values and principles have been applicable to any time people seek to accomplish something together to produce a result of some value. This has led me to believe that Agile ideas have always been, as the title suggests, about two main things that continue to be applicable if people want to make use of them to guide how they work together.</p><p>I believe that individuals and interactions is a theme across the values and principles. Three of the value statements specifically say or imply this:</p><ul><li>Individuals and interactions over processes and tools</li><li>Customer collaboration over contract negotiation</li><li>Responding to change over following a plan</li></ul><p>Of the twelve Agile principles, seven also specifically say or imply this:</p><ul><li>Business people and developers must work together daily throughout the project.</li><li>Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.</li><li>The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.</li><li>Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.</li><li>Continuous attention to technical excellence and good design enhances agility.</li><li>The best architectures, requirements, and designs emerge from self-organizing teams.</li><li>At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.</li></ul><p>The remaining Manifesto value says “working software” which I consider to be about “delivering value.” The remaining principles seem to me to fit the value delivery idea:</p><ul><li>Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.</li><li>Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.</li><li>Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.</li><li>Working software is the primary measure of progress.</li><li>Simplicity — the art of maximizing the amount of work not done — is essential.</li></ul><p>I see no reason, therefore, to talk as if the subject of “Agile” can be swept away. Indeed, I feel it has to be promoted even more, but disconnected from frameworks and certifications. Certainly, people must “do” something to implement those ideas, but I think they should consult on what they should do rather than simply adopt what others say they should do.</p><p>(Rather than say more about this, I’m posting to see what others think about what I have said then let the conversation bring out more ideas.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa0fa0f55826" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Wisdom of West Wing Continued]]></title>
            <link>https://scott-duncan.medium.com/the-wisdom-of-west-wing-continued-51b39d7eb4d6?source=rss-74df688fc261------2</link>
            <guid isPermaLink="false">https://medium.com/p/51b39d7eb4d6</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[commitment]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[the-west-wing]]></category>
            <dc:creator><![CDATA[Scott Duncan]]></dc:creator>
            <pubDate>Thu, 25 Jun 2026 21:35:04 GMT</pubDate>
            <atom:updated>2026-06-25T21:35:04.100Z</atom:updated>
            <content:encoded><![CDATA[<p>Back on May 17th, I published “The Wisdom of West Wing,” noting that I would post more as I read more of the book. I just did some further reading and have selected the following quotes of interest to me:</p><p>p. 352 — “If we don’t allow talented people to live their lives outside pf their work, they are not going to be available to us to be on the show and be good. We do that in all kinds of areas. People get sick, and we keep them on payroll and tell them to get better. You’ve got to create that world.”</p><p>To me, this is another form of psychological safety that exists in an organization where people care about other people. If that sense of safety isn’t present people will be hesitant about devoting their full selves to the relationship(s) in the organization.</p><p>p. 372 — “That idea — that arguing honestly and ’til we’re blue in the face, can lead to the best outcomes.”</p><p>Arguing honestly can make the “blue in the face” seem more like a commitment to search for the best outcomes rather than an attempt to “win.”</p><p>p. 373 — “We’re a group. We’re a team. From the President and Leo on through, we’re a team. We win together, we lose together. We celebrate and we mourn together. And defeats are softened and victories sweetened because we did them together” — Toby Ziegler, “WAR CRIMES”</p><p>This is a quote from one of the episodes (“WAR CRIMES”) which applies, of course, to real human interactions when groups of people commit to the success of one another. To me, it’s a form of servant leadership as people ask themselves “What can I do to help others succeed?” Everybody on a team thinking this way can result in everyone succeeding in the spirit of “a rising tide lifts all boats.”</p><p>p. 376 — “You’ll never regret showing up for your friends. … The more we show up for one another, the stronger the feeling of family becomes.”</p><p>This connects back to the prior quote</p><p>As before, when I have read more, I will pass on the quotes I find valuable.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51b39d7eb4d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Wisdom of West Wing]]></title>
            <link>https://scott-duncan.medium.com/the-wisdom-of-west-wing-47e10b703ecd?source=rss-74df688fc261------2</link>
            <guid isPermaLink="false">https://medium.com/p/47e10b703ecd</guid>
            <category><![CDATA[commitment]]></category>
            <category><![CDATA[the-west-wing]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Scott Duncan]]></dc:creator>
            <pubDate>Sun, 17 May 2026 18:25:23 GMT</pubDate>
            <atom:updated>2026-05-17T18:25:23.676Z</atom:updated>
            <content:encoded><![CDATA[<p>I have been reading a book entitled <em>What’s Next</em> by Melissa Fitzgerald and Mary McCormack who were part of the cast of the TV series <em>The West Wing</em>. The book is subtitled “A Backstage Pass to The West Wing, Its Cast and Crew, and Its Enduring Legacy of Service”. It describes the backgrounds of cast and crew members, how they became associated with the series, and how episodes came to be. It also describes people engage, and have engaged, in various forms of service in their communities, in the broader United States, and beyond.</p><p>My wife and I have binged-watched <em>The West Wing</em> on streaming services a couple times and we have the entire DVD collection. It is very well written, directed, and performed including the music. It addresses important issues and tries to present various sides of the issues. Overall, it does have what people would call a “liberal” slant. It also shows its connection with other work written by Aaron Sorkin such as <em>A Few Good Men</em> and <em>The American President</em>.</p><p>As I have been reading the book, some passages have struck me because of how they address teamwork and respect for team members. I’m about halfway through the book, but I want to offer quotes I have found relevant to work I do training and working with people and teams.</p><p>The following excerpts from the book describe how I would hope people on teams would feel about (and pursue) their relationship with one another. I have made some comments of my own about each excerpt based on things I have seen and encouraged working with people:</p><p>p. 160 — “I felt like I was with a lot of people who knew what they were doing. And that was exciting.”</p><p>This somewhat reminds me of the Retrospective Prime Directive from Norman Kerth’s book entitled <em>Project Retrospectives</em> which says “Regardless of what we discover, we understand and truly believe that <strong>everyone did the best job they could</strong>, <strong>given</strong> what was known at the time, <strong>their skills and abilities</strong>, the resources available, and the situation at hand.” The words in bold aren’t quite what “who knew what they were doing” means; however, the idea that working with people who behave competently is “exciting” is suggested by both.</p><p>p. 161 “…it was a group that like to pass as much as they liked to shoot.”</p><p>The idea of sharing opportunity with others is a valued and admired trait seems a clear implication of this quote.</p><p>p. 162 — “We always had lunch together.” The point was for the cast to get to know one another — for real — to get a sense of everybody’s rhythms, a sense of the connections between them.”</p><p>Many people who coach teams talk about people getting to know one another as individuals beyond their professional, technical contributions as a way to create more meaningful “connections between them.”</p><p>p. 208 — “Every time we think we’ve measured our capacity to meet a challenge, we look up and we’re reminded that the capacity may well be limitless.”</p><p>While suggesting we have greater capacity than we realize, I believe this quote also encourages pursuit of that greater capacity beyond our current perception of our limits.</p><p>p. 229 — Robert Hennedy’s declaration that “one heart with courage is a majority.”</p><p>In my classes, I usually end with the suggestion that, for change to occur, it has to start with someone who believes that is important and possible and that each person in the class can be that “one.”</p><p>p. 295 — “…commitment — from every corner — to respect the process of whatever work is being done by whichever member of the team, is vitally important.</p><p>I often tell classes that an idea may fail, not because it is a bad idea, but because people do not fully commit to try to make it succeed. This quote suggest that commitment can come in the form of support for those working to make something a success, not just those doing the work.</p><p>p. 295 — Speaking about showing a level of trust to give a person the time to follow their vision as “magic” compared to other shows: “The vast majority of the time, it doesn’t happen. The vast majority of the time, vision and artistry eventually get chipped away. And if nobody’s protective of it, the clock starts ticking in your head. Instead of the work, the clock becomes what matters.</p><p>To me, this means that without the vision and broader purpose for which people can pursue, effort will become perfunctory and tend to doing the least possible to meet the minimum. Years ago while helping people achieve ISO9001 registration I showed this diagram:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*y1iItoq6h6KfwfAGNECPNg.png" /></figure><p>Some of the management encouraged people to do “No more than necessary” to meet the ISO9001 expectations. It was clear they meant people should do “As little as possible” to just meet the expectations of the standard rather than “A little more than we have to.” I observed that trying to just meet the registration target and do no more occupied more time for people to assess where that minimum existed than to risk doing more.</p><p>p. 295 — “The culture of mutually assured protection…”</p><p>The idea of people feeling there is psychologically safety in their environment is what this quote suggests to me. The safety comes from everyone working to make it true for one another.</p><p>p. 295 — “And it wasn’t that we just liked one another or laughed a lot or had the good fortune to share great chemistry — it wasn’t <em>just</em> those things. It was the faith we had in every other person to do their job at a very high level.”</p><p>This quote gets back to the first one and the ideas of the Prime Directive where we believe people do the best they can but also go beyond their assumed capacity to excel. This can happen in an environment where people feel supported by one another. I often tell people my definition of a “servant leader” is a person who looks at other people with whom they interact regularly and ask “What can I do to help these people succeed?” If everyone does that, I believe people can be successful because everyone is working to make that happen.</p><p>p. 295 — It’s not magic. It just feels that way.</p><p>This quote reminds me of teams who seem to get things done much more easily than other teams. To those outside such successful team, it seems like what they do is magical. I point out, however, that such teams worked very deliberately to get to where they could achieve things together with far less friction than other teams. It wasn’t “magic”; it was commitment to everyone’s success.</p><p>As noted above, I believe I’ll have more to add as I continue reading the book. I’ll update this as that happens.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47e10b703ecd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Information, Decisions, Actions]]></title>
            <link>https://scott-duncan.medium.com/information-decisions-actions-f304e64dd5dd?source=rss-74df688fc261------2</link>
            <guid isPermaLink="false">https://medium.com/p/f304e64dd5dd</guid>
            <dc:creator><![CDATA[Scott Duncan]]></dc:creator>
            <pubDate>Sat, 28 Feb 2026 14:11:51 GMT</pubDate>
            <atom:updated>2026-02-28T14:11:51.148Z</atom:updated>
            <content:encoded><![CDATA[<p>As I was waking up this morning, I suddenly thought about something Alistair Cockburn said many years ago about “What we deliver is decisions” and how “decisions build upon decisions” and that “unvalidated decisions” are our “internal inventory.” That reminded me of the statement I’ve heard elsewhere that not deciding is a decision.</p><p>I hope to be giving a talk in April for Linda Westfall related to metrics. I decided this morning that I want to start the talk by asking “Why?” Why would someone want to pursue metrics? Presumably to gain some information used to learn something, so decisions can be made based on that learning which lead to some sort of action(s).</p><p>That got me thinking how agile/agility are often defined as <em>“having the ability to move quickly and easily.”</em> Now that’s the action part, but you need the others (i.e., information and decisions) to get to actions.</p><p>I have previously written and spoken about three things which I suggest people look at their organizations and consider:</p><p>· How effectively and frequently do people in their organization communicate with one another?</p><p>· How effectively and frequently do people in their organization collaborate with one another?</p><p>· How effectively and frequently do people in their organization demonstrate trust with one another?</p><p>I believe you need to communicate effectively and frequently to get the information to learn something. Then you need to collaborate effectively and frequently to make decisions based on that learning. Finally, you need to trust one another effectively and frequently to lead you to, and accomplish, action(s).</p><p>Along the way I would suggest you need to employ a servant-leader mentality to ask “How am I helping someone/thing to succeed by what I am doing?”</p><p>So correctly or not, I drew parallels between communication and information, collaboration and decisions, trust and actions.</p><p>I haven’t thought more than this since this morning. I plan to before April. But I am wondering what people think about what I’ve said.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f304e64dd5dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Project Management Responsibilities Can Agile Teams Perform?]]></title>
            <link>https://scott-duncan.medium.com/what-project-management-responsibilities-can-agile-teams-perform-6d7cbb00bb37?source=rss-74df688fc261------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d7cbb00bb37</guid>
            <dc:creator><![CDATA[Scott Duncan]]></dc:creator>
            <pubDate>Wed, 30 Apr 2025 18:52:46 GMT</pubDate>
            <atom:updated>2025-04-30T18:52:46.414Z</atom:updated>
            <content:encoded><![CDATA[<p>People have suggested that, in an Agile approach, project managers are not needed and that managers, in general, are not needed. However, management practice as well as project management are both needed. Do these have to be done by people with formal titles? Undoubtedly some things would be, but Agile teams could do many of these practices themselves or in collaboration with others.</p><p>There are many project management responsibilities identified in websites and articles, including the Project Management Body of Knowledge from the Project Management Institute. Listed below (in no order) are some responsibilities and how Agile teams would be expected to do (at least some of) them.</p><p><strong>Client responsibilities:</strong></p><p>One project management responsibility would be to seek client<strong> </strong>feedback on satisfaction, approval, concerns and questions regarding work delivered. The expectation would be to meet stakeholder satisfaction by reducing uncertainty, avoid surprises, and involve clients as much as possible. This includes being responsible for clarity of release requirements and being the connection between project stakeholders. All this means providing clear, transparent communication among team members, stakeholders, and clients.</p><p>An Agile team has many opportunities to be a part of this relationship. They can participate in requirements writing workshops, story refinement, and, of course, iteration review sessions. If frequent customer involvement is possible in these work sessions, clarity can be achieved and uncertainty eliminated.</p><p><strong>Document:</strong></p><p>A part of maintaining communication with stakeholders might be expected to include preparation of reports covering:</p><p>· records of project plans, progress, issues, resolutions, activities, progress, and decisions;</p><p>· deviations that occurred and corrective actions;</p><p>· project requirements that were fulfilled;</p><p>· project history describing what was done, who was involved, and what could be done better in the future.</p><p>Documentation is unlikely to remain static as they may need to be revisited and revised throughout the project lifecycle because things change. For example, the roles of different individuals may change and while a company’s objectives might not change, the way to reach them could.</p><p>Though there is a need to monitor progress so it can be completed within the schedule and budget, teams should not be overburdened with detailed spreadsheets, lengthy checklists, and other forms of documentation as excessive monitoring may result in demotivation for team members.</p><p>An Agile team, through visibility into what they do, can provide the information that others would need to gain the knowledge they need, either directly or through more standard forms of documentation that others would create.</p><p><strong>Planning:</strong></p><p>Typical project management is expected to identify key milestones and set realistic deadlines as well as negotiating an appropriate budget with clients so the scope can be completed within the budget and schedule give available personnel, equipment, and other resources. All these then need to be communicated clearly to their teams so everyone can work and adapt when needed to keep work on track.</p><p>An Agile team should be involved in release planning activities so they can reasonably commit to the work they can accomplish. Once again, other people (e.g., management) would be the appropriate people to provide the resources a team needs to meet the expected budget and schedule. The fifth Agile principle suggests what the team needs from others to be successful in meeting customer value expectations.</p><p><strong>Quality:</strong></p><p>Being on budget and on schedule are certainly important, but project management also includes working to ensure quality of the results. This includes helping to define standards against which to measure quality to assess work effectiveness. As with planning concerns, quality expectations must be clearly identified so all team members know what they must do to achieve such standards.</p><p>An Agile team has significant responsibility to deliver results of high quality. They should have an effective Definition of Done to guide them in doing so. But also, their frequency of interaction with and feedback from customers adds a further element to the achievement of quality results as such quality goes beyond defect freeness into the many thins needed to achieve “fitness for use.” When teams have effective relationships between designers, Business Analysts, Quality Analysts, and User Experience Designers the customer experience will add to the overall quality achieved by the work.</p><p><strong>Risk:</strong></p><p>Effective project management requires understanding that things won’t all go as planned nor be as easy as expected. This can include unexpected requirements changes, resource constraints, market and competitive activity, dependencies between groups, and challenging circumstances due to stakeholder changes. While not everything like this can be identified at the outset of work, some strategies for handling typical project risks should be discussed so management, teams, and clients can discuss possible approaches should such things occur. Then, if such things occur, everyone can work together to resolve them as they arise.</p><p>Agile teams have daily opportunities (among other ones) to assess their ability to deliver value, ensuring each iteration can identify and addresses risks significantly sooner than possible in a more phased-sequential cycle of work. The frequent feedback from customers, at least at the end of every iteration, limits long-term impacts of risks since they can be resolved before they become much more serious.</p><p><strong>Team:</strong></p><p>Some less typical, but still important, project management expectations include acting to effectively contribute to team facilitation by working with team coaches and facilitators. This includes helping to:</p><p>· foster collaborative team behaviors,</p><p>· provide useful feedback,</p><p>· address issues that encourage motivation as well as prevent demotivating actions,</p><p>· and promote regular, meaningful reflection and adaptation.</p><p>These require building a team that agrees on roles and responsibilities as well as expectation for technical and quality standards so they can be trusted to work independently. This can take a while with people who are not used to working this way, including resolving conflicts and concerns constructively as a team.</p><p>Teams need, and should also provide, useful feedback to surface concerns and impediments but also to celebrate accomplishments. For this to happen, those who help facilitate teams, need to be close to them so such feedback can be easily communicated. This is supported through regular reflection to understand the lessons learned about its success and identify areas for improvement.</p><p>Much could be said about team motivation (and demotivation) that affects (or inhibits) team member desire to keep moving on the right track. This means such facilitation requires people to lead by example. Having a healthy relationship with teams will promote motivation.</p><p>A final way project management considerations can help teams is through encouragement to break tasks into smaller pieces to help set easily managed priorities and milestones. Teams can handle complex issues with better agility by working in small increments.</p><p>Agile teams can do many things to build effective communication, collaboration, and trust through honest and open engagement between team members and those outside the team. They can contribute to everything noted in the five paragraphs above.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d7cbb00bb37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“I come to praise Agile, not to bury it.”]]></title>
            <link>https://scott-duncan.medium.com/i-come-to-praise-agile-not-to-bury-it-17796698c89f?source=rss-74df688fc261------2</link>
            <guid isPermaLink="false">https://medium.com/p/17796698c89f</guid>
            <dc:creator><![CDATA[Scott Duncan]]></dc:creator>
            <pubDate>Thu, 10 Apr 2025 16:00:07 GMT</pubDate>
            <atom:updated>2025-04-10T16:00:07.541Z</atom:updated>
            <content:encoded><![CDATA[<p>My thoughts on the many claims that Agile is dead/failed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yln_xze5M4Ppa6ZG6OelWA.jpeg" /></figure><p>(At Agile 2009, Alistair Cockburn gave a keynote talk which started with a brilliant take on Marc Antony’s eulogy for Caeser from Shakespeare that Alistair entitled “I come to bury Agile, not to praise it.” You can see him deliver this at <a href="https://www.infoq.com/presentations/cockburn-bury-not-praise-agile/">https://www.infoq.com/presentations/cockburn-bury-not-praise-agile/</a>. I’m flipping the idea in what I write here, though I feel it is related to what Alistair said. If you want to see what I wrote about Alistair’s keynote beyond his “eulogy” speech, you can find my notes for that conference at <a href="https://scott-duncan.medium.com/agile-2009-conference-notes-adacdecdc08e">https://scott-duncan.medium.com/agile-2009-conference-notes-adacdecdc08e</a>.)</p><p>(While I agree with people who point out Agile is not a thing, i.e., it is an adjective, not a noun, I will use it here to mean “the ideas represented by the Agile Manifesto” since that’s what I think “Agile” is all about.)</p><p>— — — — — — — — — — — — — — — — — -</p><p>I got curious the other day after seeing another couple “Agile is dead/failed” posts. I wondered how many such posts, articles, or whatever there might have been. The oldest post I happened to find was from 2016. There assuredly were earlier ones. Indeed, a few months after the Manifesto was published, a letter to the editor in IEEE Computer stated how the author felt Agile would be a disaster for responsible software engineering. So not dead but deserving to be so.</p><p>My next thought was what people identified as why Agile was dead or failed. After going through 20–30 posts and articles, I believed I had come up with some of the common reasons people gave. In writing this post/article I’ll try to summarize these and offer my thoughts. I do not feel Agile is dead or failed. I believe things people identified have caused ineffectiveness in how Agile has been adopted/promoted. These have led to “failures” in successful adoption but do not, to me, prove Agile is a failure.</p><p>Some people said that Agile itself isn’t dead, but efforts to adopt it have died many times. So Agile hasn’t died, but as other people put it, it is “not well” and “smells funny.”</p><p>One of the issues mentioned was dogmatic approaches to implementing Agile. Some said Agile had moved from a “philosophy” to a “religion” where people “checked off boxes” to be sure they were “doing” it “right.” The “doing” becoming more important than the outcomes of doing it.</p><p>One thing they blamed for this dogma was framework adoption. Agile, they pointed out is not a framework, but it became sold as a framework with required certifications (pointing to Scrum in particular). It is true that many organizations adopting Scrum have equated it with Agile. Surveys such as done by VersionOne (and now Digital.AI) over the years indicate some 84% of people “doing” Agile are doing so by implementing Scrum, Scrum with XP, Scrum ban, or some such Scrum variant. We can consider at least a couple of scaling approaches to be at least Scrum-based as well. Scrum does get the focus of many people’s disdain for frameworks (and SAFe after that).</p><p>In fairness, people have acknowledged that frameworks arose from a desire to address challenges in traditional development processes and the desire for better collaboration between people. However, “doing” the frameworks “by the book” led to dogmatic approaches, seemingly ignoring the Agile call for continuous improvement and experimentation. This some feel has led to more big organization bureaucracy creeping into how Agile becomes acceptable to such organizations.</p><p>People also point out that concerns devolved into an Agile vs Waterfall battle as they were the only choices, casting those working in the traditional way as doomed to die because they would/could not adapt to change. Of course, Agile isn’t a process model whereas Waterfall is, so at the outset, it is an apples-to-oranges comparison. However, for those who equate Agile with a framework which has process model elements, perhaps that’s what they mean by the comparison.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*7MJklRPcx0zQFVHSyOefxw.png" /><figcaption>Alistair’s Crystal Methods Diagram</figcaption></figure><p>When I read Alistair Cockburn’s work on Crystal methods, his diagram in the book “Crystal Clear” illustrated that there was a spectrum of approaches, not just two. Depending on the possible cost of failure and the number of people involved, Alistair suggested multiple approaches would be needed — any of which could be called “Agile” or “Waterfall” depending on the intersection of cost and staff size.</p><p>From these dogma and framework considerations, people also pointed to corporate promotion and adoption as “killing” what Agile envisioned. On the promotion side was what has been called the “commoditization” or “industrialization” of Agile to address organizational need to see the “legitimacy” of Agile demonstrated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*3Wl8cMKmdwddvBa6rVgPmQ.png" /><figcaption>Moore’s “Chasm” Diagram</figcaption></figure><p>Referring to Moore’s “chasm” diagram, the Early Majority organizations (and certainly the Late Majority ones) needed some proof that Agile wasn’t just a fad (though critics in many articles say it is). The rise of formal (framework-based) training and certifications began to provide, and then became, the evidence such organizations needed. This led to drifting further from team experimentation for improvement to conformance to the official framework rules required by large companies to “manage” the effort. Too much difference between teams would be feared as deviating from company policies and “playbooks” sold to them by big consulting firms after they saw they needed to sell Agile.</p><p>I saw the latter happen personally and noted that the “playbooks” were often the same sold to multiple companies just changing names, title, etc. to match the new client but sold as if it was customized work for the new client. I also saw clients interested in Agile, after an Agile coach talked about how the consulting firm could help them do that, get redirected by the firm’s salesperson, uncomfortable and ill-informed about Agile, to the firm’s standard methodology, claiming the client could get “all of that” from the standard approach the consulting firm comfortably followed.</p><p>Packaging frameworks and selling them to clients evolved as traditional companies were used to “buying solutions,” especially those that did not suggest much (challenging) change had to occur. Transitions to Agile behaviors within a framework, though called “transformations,” did not ask for significant structural change within the organization. People above and outside of product development could remain doing what they always had. Consulting firms knew companies did not put out RFPs for organizational change so pushing for it would not get them a sale.</p><p>The practice of “sheep-dip” training and some small physical facilities changes (e.g., open team spaces, whiteboards, sticky notes, etc.) became the adoption approach. This was followed by organizationally driven “health-checks” used to see if the organization was “doing Agile” according to the framework rules. Like any metric, teams could see how to respond to what the organization wanted. As Goodhart’s Law says, “when a measurement becomes a target, it ceases to be a good measure.” Measures can be “gamed” easily.</p><p>The ”industrialization” concern led people to talk about the impact of company culture and/or the lack of understanding of the culture that Agile encourages. Some people did encourage following an Agile “spirit” even if not always sticking close to prescribed practices. This meant honoring the “why” of Agile rather than the “how” of specific framework rules.</p><p>I can only say I have seen (many) teams be sustainable working in an Agile fashion for years, iteration after iteration, because they had learned how to predict their capacity to get work done and, if over-committed, would voluntarily work extra to meet what they promised. One post did say that an Agile approach would only work when you have team members who would go “above and beyond.” I have heard Chet Hendrickson suggest the early Agile innovators felt they were nothing out of the ordinary and assumed everyone could work as they did. He felt this was a mistake on their part.</p><p>Regarding culture, I have always felt that the fifth Agile principle was important but also perhaps the hardest to implement in an organization based on how people have reacted to it when I have spoken about it. It says: “Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.” My thought is why would any organization not want to do this and then make it happen? People hopefully start working in an organization because they are motivated to be there, so why does leadership often ask how to motivate people? What has been done to demotivate those initial motivated people? Why would you not give people the things they need to get the job done if you hope it can be done properly? And certainly, why would you have people take on work if they cannot be trusted (or at least helped without micromanagement), as one person said, “to go off on their own for at least 4 weeks” to get work done?</p><p>Regarding Agile as a failure, it was stated that, despite what the Manifesto says, it seems to promote process over people. The examples I read to justify this always seem to go back to framework dogma and not because Agile tells people how they should specifically implement the values and principles. If so many adoption efforts are less than successful (or outright fail), critics ask can you really blame the practitioners, or is it more simply Agile’s fault?</p><p>However, there are decades of data, such as from The Standish Group, showing how the traditional Waterfall approach is much more likely to fail than an Agile one. For the Standish Group, success has always meant to meet the initial goals of schedule, budget, and functionality. Failure to meet any one of these means a challenged project, at least, and if more, a failure. If you see one of the charts from such Standish reports, Agile is always more successful than a traditional approach. But Agile is not by any means perfect. One reason may be the scope flexibility Agile promotes to meet evolving client expectations such that all initial functionality might not end up being delivered at the release date.</p><p>Another thing that the chart shows is that for large and medium projects, Agile is way better than Waterfall. However, for small projects, though Agile is still ahead of Waterfall, Waterfall is much closer in success. So perhaps keeping projects small makes them easier to manage to success? Seems straightforward. Agile’s approach of trying to break work into small iterations, envisioning short releases, and presenting frequently to clients for review is a way to do this. But short Waterfall projects could achieve the same success which the charts suggest is true.</p><p>Much of the failure criticism seems targeted at practices which Agile does not demand though frameworks and people often do. People responding to these criticisms suggest the bad experiences sound like poor (framework) implementation problems forcing bad practice. Of course, people respond to that saying this is just “blaming the victim.” But, having seen weak implementations, I can agree that the pains are because of that failure of adoption which team members must suffer under and, therefore, hate Agile.</p><p>The next complaint people have about Agile failure is leadership. The criticism is that Agile has missed by not offering clarity about what leaders/managers need to do to work in an Agile fashion. Indeed, some early protagonists for Agile did suggest, if not outright say, that management would be unnecessary in an Agile approach. The Manifesto doesn’t mention management, that’s true, but that did not mean everyone thought managers were to go the way of the Dodo, even if a couple certainly did. I do not feel anyone was saying leadership was not needed.</p><p>Indeed, the idea that everyone should see how they could promote and provide leadership always seemed to me to be what an Agile approach expected. I think individuals should all ask themselves, “How can I help the other people I work with become successful?” This is my idea of what it means for people to pursue servant leadership from the highest-ranking person in the company to every team member.</p><p>Formal leaders in an organization need to understand that adopting an Agile approach can mean significant change in how people relate to one another and to their work. This takes time, though it need not mean that useful work halts until that full switch has been made. Organizations that pursue an Agile approach because they are facing pressures may not have patience for this or a Kanban approach which may seem even longer to develop. (A few years ago, Alistair Cockburn posted a picture of him sitting facing a semi-circle of senior managers from a company. The company was concerned they had not “transformed” their organization after a year working on it. They were people who, when they decided to do something, it happened yesterday. They asked Alistair how long it should take for full organizational transformation. He said he thought a bit then said, “About 10 years.” There was silence and many dropped jaws.)</p><p>Agile does require different ways of thinking before the “doing” happens well. Changing how people think is harder than getting them to “do” something. There are two ways suggested about encouraging change: change what people think and then they will do things differently; change how they behave, and they will change how they think. Like many things, it may be a matter of both. People must have some understanding about “why” they are being asked to behave differently, then accumulated practice will help them think differently about what they do. Also expect that encouraging people to change means some experimentation in pursuit of continuous improvement.</p><p>People did ask whether organizations are mature enough to adopt Agile properly because of how thinking must change. It doesn’t have to be a change such as, figuratively speaking, on Friday we work in our normal way, learn an Agile framework over the weekend, then start practicing it on Monday. That can mean new job titles, new meetings, new technical practices, new customer relationships, new work cycle, etc. That’s a great deal to have people absorb and can lead to resistance to the change. On the other hand, on Friday we work in our normal way, learn about Kanban over the weekend, then start practicing it on Monday. However, in this case, Kanban says that on Monday you do just what you were doing on Friday — no new job titles, meetings, technical practices, customer relationships, work cycles, etc. But you must commit to continual improvement, finding, bit by bit, what the next small change could be to help you work better. Maturity grows rather than having to be a flash-cut.</p><p>By misunderstanding that Agile is about a framework, dissatisfaction is likely to arise. One large misunderstanding is about planning and what the fourth Agile value asks people to understand about “Adapting to change over following a plan.” Again, this does not suggest rejecting or ignoring planning. It’s just the precedence of learning to work so you can respond effectively to change over just forcing through the original plan.</p><p>I don’t think anyone believes these days that things will not change. The traditional approach is to do lengthy due diligence thinking about every change, challenge, and risk that might occur and then have the appropriate mitigation plan to handle that. If you are far up Alistair’s cost axis, or far out on the staffing one, this kind of effort may be necessary.</p><p>Consider what many people have said over the years about plans and change. Von Molte (paraphrased) said “No battle plan ever survives contact with the enemy” as the enemy will not simply bend to your will. Mike Tyson said “Everybody has a plan until they get hit in the face.” Eisenhower said “Plans are worthless, but planning is everything” recognizing that things change making plans no longer valid. However, by engaging collaborating in planning, when change comes, people are better prepared to work together to deal with it. Eisenhower’s view works at any level of organizational planning including, and perhaps especially, at the team level.</p><p>A different criticism was that there was never the problem that Agile was designed to solve. That is, the problem of Waterfall “didn’t really exist to any great extent.” They pointed to Royce’s paper that, while it had the “Waterfall” diagram in it at the start, never uses the word “waterfall” and proposes a recommended way to work more consistent with Agile iterative focus.</p><p>However, people did latch on to that first diagram and ignored the more iterative ideas Royce presented. He thought the original diagram was full of risk and could lead to failure because of lack of feedback. Others point out that a classic work by Parnas and Clements’ (i.e, “A Rational Design Process: How and Why to Fake It”) and the Evo approach from Tom Gilb had all one needed to be “agile,” preceding the Manifesto by a decade at least.</p><p>Having lived through the 70s, 80s, and 90s I am familiar with what people commenting on this have identified. I must say that in the early 80s, I worked on a project that had aspects of what I later read in Kent Beck’s book “eXtreme Programming Explained.” So yes, much of what Agile advocates does go back to many ideas decades before. When I read Deming’s 14 Points, several of them have close connection to Agile ideas. The Manifesto had a lot of these ideas represented in the simple statement of their beliefs about a better way to work which I believe can, in many respects, be successfully used in a Waterfall situation.</p><p>I did mention earlier that there were complaints about practices and that my feeling was this did not inviolate Agile as a whole. A few of these were the ideas of “ensemble,” “pair,” “teaming,” and “mob” development. One comment was that these did not seem “liveable” and that pairing “hugely sucks.” Other comments were that these approaches were “exhausting,” “inefficient,” “unsustainable” and were used when peers could not be trusted to work alone. Yet another opinion, however, was that “mobbing” was “great with the right people.”</p><p>Other complaints seemed to focus on daily meetings (i.e., standups) where a project manager ran it as a “sit down.” Another person said it was an event where “everyone mumbles their updates, nobody listens.” Finally, people pointed out that none of the practices others mentioned (and more) are mentioned in the Manifesto but were recommendations/requirements of specific frameworks.</p><p>Retrospectives, on the other hand, are implied in some form by the last Agile principle: “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” It doesn’t say how to do this or exactly when, but the complaints listed were that people don’t seem to want to speak up and nothing, despite all the talk, ever gets done to produce change. It was also mentioned that retrospectives turn into finger-pointing sessions. Several of the comments mention all these problems also talk about the cultural difficulties in getting useful feedback. Countering this and providing some idea of what is needed to overcome these, was a comment that said “genuine engagement” is needed or it will just be a meeting to “check-off the box” of having done it. All I can say here is that the concerns all seem to be about failure in how a retrospective is done not that it is a bad idea. Of course, if any aspect of an Agile approach is not going to be done effectively, people will find it objectionable to do it.</p><p>What do I conclude from all the dead/failed things I read? It just seems to me that they all derive from poorly understood and adopted Manifesto ideas. I don’t agree that if many people don’t do it well, it must be the fault of Agile. Neither do I agree with those who say the Manifesto is not relevant or sufficient to address everything people feel need to adopt it successfully. It was never intended to do that. It was an expression at a point in time of what the people at the meeting agreed would improve development at that time.</p><p>The first few words of the Manifesto are “We are uncovering” not we “have” uncovered. To me this means the idea was to continually find ways to work better, not to suggest the Manifesto had everything people would (ever) need to work better. Let’s pursue an effective understanding of the Manifesto’s values and principles and advocate for successful adoption of them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17796698c89f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A person is smart. People are dumb — The Traitors Reality Shows]]></title>
            <link>https://scott-duncan.medium.com/a-person-is-smart-people-are-dumb-the-traitors-reality-shows-960c995cf249?source=rss-74df688fc261------2</link>
            <guid isPermaLink="false">https://medium.com/p/960c995cf249</guid>
            <dc:creator><![CDATA[Scott Duncan]]></dc:creator>
            <pubDate>Sat, 25 Jan 2025 16:31:48 GMT</pubDate>
            <atom:updated>2026-02-13T14:07:21.468Z</atom:updated>
            <content:encoded><![CDATA[<h3>A person is smart. People are dumb — The Traitors Reality Shows</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rocAm9j7voerkSLRDt9LvA.png" /></figure><p>Tommy Lee Jones is speaking to Will Smith early in the film Men in Black: “A person is smart. People are dumb, panicky dangerous animals and you know it.</p><p>Over a year ago, I stumbled upon a series of shows called The Traitors. I found one hosted by Alan Cumming in Scotland (though featuring people from the USA). I then found an Australian version of the show and another version held in the UK but with people from the UK. I got hooked on watching them because of the interesting view of human behavior which they all revealed. (There is a version — I think the first — in the Netherlands but done in Dutch only.)</p><p>A new series with Alan Cumming just started a few weeks ago and it prompted my thoughts on how people behave in all these games as examples of crowd mentality.</p><p>Basically, a group of 21–24 people are gathered at a castle or large hotel. They are divided into two groups known as “Faithfuls” and “Traitors” with 3–4 of the latter chosen in secret so the Faithfuls do not know who they are. Then, over the course of many days the Faithfuls try to determine who the Traitors are and banish them from the game because, at the end, there is a large pot of money to be shared by the last few Faithfuls left if they eliminate all the Traitors. But if a single Traitor is left, the Traitor (or Traitors if more than one survives) claim all the money. (The money grows based on “missions” all the players engage in, and they must work cooperatively each mission to earn amounts of money to add to the total.)</p><p>Each evening, the Traitors pick a Faithful to “murder,” eliminating them from the game. Each day, all players (remaining) meet to select a person they believe is a Traitor and banish them. It is also possible for Traitors to turn on one another and help vote to banish a Traitor, reducing the number of Traitors that might split the money.</p><p>This whole process is based on the party game originally known as Mafia but more recently called Werewolf where the Traitors are werewolves and the Faithful are townspeople the werewolves want to kill before they are uncovered.</p><p>My point in writing this post, though, is not to specifically review the shows, but to comment on what I observe about how people behave during the shows when there is some pressure to make decisions in seeking to acquire the growing pot of money.</p><p>My main observation is how ineffective the Faithfuls are in identifying the Traitors, at least early in the game.</p><p>Let me start, though, with an observation that makes it clear why this is an easily anticipated problem for the Faithfuls. Since are 3–4 traitors and 21–24 total players, the odds are 1 in 6/7 that the Faithfuls can find a Traitor very early. Surprisingly, no one in the game seems to mention this. Then, when the Faithfuls guess incorrectly and banish one of their own, they act shocked and dismayed they have done this. Unless the Traitors perform foolishly early on, this should not be a real surprise. But the Faithfuls never consider the odds against them as something which can result in erroneous banishment.</p><p>Of course, some people seem very sure about their voting against another person. But why should they? People claim it is because they see behavior, before or at the banishment session, that makes others look “suspicious.” This is usually for reasons such as:</p><p>· someone does, or doesn’t, make eye contact when others think they should or they make too much eye contact;</p><p>· someone does, or does not, speak up much when others think they should or they speak up a lot;</p><p>· someone seems to express strong concern they know who a Traitor might be (which is interpreted as “deflecting” attention on others) or they don’t easily accuse someone (which is viewed as trying to hide as a Traitor by not giving anything away in their views);</p><p>· someone expresses body language that others feel marks them as a traitor or they seem to show no observable changes in their “looks” during interactions.</p><p>Of course, any of these behaviors, one way or the other, could be an accurate sign of a Traitor or it may not.</p><p>In response to accusations about any of these, those accused may rightfully claim that this is just how they respond. They are not self-conscious about it. It’s just how they are. The lesson people should learn very early is that the game is about suspicion which magnifies the smallest thing others may decide is a negative characteristic. Of course, Traitors are generally too smart to reveal this sort of thing or have very plausible explanations if they do. Traitors can display a great deal of skill in, frankly, lying to the Faithfuls.</p><p>If a Faithful gets a gut feel they know a Traitor, they may not have enough solid evidence to convince other Faithfuls. If they continue to push their idea against someone (at a single meeting or a sequence of banishments), others may come back and ask that person to defend their answers. Indeed, anyone who puts forward any seemingly strong belief is often challenged by others to defend themselves. A lot of time is spent in banishment meetings demanding of others, often heatedly, to defend their positions. This heated exchange, itself, can misdirect the group and result in the failed banishment of a Traitor.</p><p>But since the Faithfuls must vote on a suspected Traitor, people are forced into decision-making based on limited or downright weak “evidence” for doing so. Quite humorously actually, when it is revealed they have banished a Faithful (and they keep doing it), every time that happens one or more people (including Traitors sometimes) say “We have to start thinking logically.” But every time, early in the game, they do not. They have so little real information go on, so little understanding of one another, that they make decisions incorrectly.</p><p>With such little evidence, there are many Faithfuls who state they are not sure but vote against someone anyway. They often note that, without their own evidence, they have been swayed by what others say. They claim that they too have (somewhat) observed what other people claim is reason to vote someone out. So, they go along with it and, generally, the wrong person gets banished, at least early in the game.</p><p>Now, as this banishment of Faithfuls is happening, the Traitors often eliminate a player each night through virtual “murder.” I say “often” because sometimes the Traitors are given other behaviors they must carry out which isn’t an instant “murder.” And if a Traitor is found, one of the other actions made available to the remaining Traitors is to select a Faithful to invite to join them as a Traitor. (Sometimes the invitee agrees and sometimes they reject the anonymous invitation. The invitee doesn’t know who invited them.)</p><p>Thus, in a single day of the game, 2 Faithfuls may disappear. One might think this makes it easier to pick the Traitors, but that often doesn’t happen until at least half of the Faithfuls are gone. By the time this point is reached, a Traitor may have been identified. Other Traitors may feel this puts a target on them and Traitors may go after one another if only by agreeing with Faithfuls who feel they know at least one Traitor. The remaining Traitors often feel they must go along to vote the other Traitor out to deflect suspicion from them. This often works, for a while.</p><p>(Note: Traitors are not allowed to reveal themselves until banished by the majority vote and are likewise not allowed to reveal who the other Traitors are. Though, in one episode of the UK version, a Traitor, seeing the opinions against him, including another Traitor’s, made a comment about his vote during banishment that then made some remaining Faithfuls suspicious about the Traitor who also voted against the one banished.)</p><p>A further strategy Faithfuls might use could be to willingly vote another Faithful off, with supposedly good evidence, because they may not like them much for some reason. Nobody on any of the shows has talked about this, so perhaps no one thinks about this. But if you want to win the game, you may feel that reducing the number of Faithfuls will reduce the number of people who might split the money at the end if the Traitors are all eliminated. Eliminating a Faithful if you don’t like their behavior may not actually bother other Faithfuls much. I have observed this and people saying that the mistake of removing another Faithful didn’t bother them because the banished Faithful’s behavior was disagreeable and/or distracting to making “logical” decisions.</p><p>Now the whole game is an artificial situation forced by the rules of the game which require people to suspect one another and vote on a banishment each day. But it does show how people, under pressure (or perceived pressure), can revert to dysfunctional behavior and decision-making not based on fact but because they feel they have to take a position of some sort.</p><p>The game illustrates “mob mentality” which also occurs in real life situations. Years ago, James Surowiecki wrote a book called <em>The Wisdom of Crowds</em> where the point was that aggregated information in groups can result in better decisions than made by any individual in the group. There are 5 things mentioned which it was stated were necessary for this to work:</p><p>1. everyone should have information of their own even if a possibly odd interpretation of the facts;</p><p>2. everyone’s opinion should not be decided based on the opinions of people around them;</p><p>3. everyone can use locally available knowledge;</p><p>4. everyone has a way to contribute what they believe to an aggregation resulting in a collective decision;</p><p>5. everyone feels the people combining their ideas to be fair.</p><p>A couple of these are true in the game, but not all of them. In the game and often in real life, #2 and #5 are always suspect. Sometimes #3 also fails when some people have access to information others do not and that information does not get shared.</p><p>The deliberate deception of the game prevents what Surowiecki felt could give a crowd the wisdom to make a better decision than any single individual. The game illustrates what happens when people, for self-interest, pursue their own wishes rather than seek a more collaborative approach that will offer success to all the people.</p><p>[I should note that Ted Alspach wrote an article about a year ago entitled “The Fundamental Flaw with The Traitors” (<a href="https://opinionatedgamers.com/2024/02/03/the-fundamental-flaw-with-the-traitors/">https://opinionatedgamers.com/2024/02/03/the-fundamental-flaw-with-the-traitors/</a>) in which he discusses all the things he feels make the show(s) weak.]</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=960c995cf249" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life, Liberty and…]]></title>
            <link>https://scott-duncan.medium.com/life-liberty-and-0e19d1a735d7?source=rss-74df688fc261------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e19d1a735d7</guid>
            <dc:creator><![CDATA[Scott Duncan]]></dc:creator>
            <pubDate>Fri, 05 Jul 2024 17:53:33 GMT</pubDate>
            <atom:updated>2024-07-11T12:45:16.979Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*BtuTJZKroZzL2yvcvcCrrw.png" /></figure><p>The second paragraph of the Declaration says:<br>“We hold these truths to be self-evident, that all men are created equal, that they are endowed by their Creator with certain unalienable Rights, that among these are Life, Liberty and the pursuit of Happiness.”<br>I thought about this today and considered what I thought this meant (or could mean).<br>The first thing, of course, is that a long paragraph against the practice of slavery was removed calling into question how the signers viewed “all men” being “created equal”. According to the article “(1776) The Deleted Passage of the Declaration of Independence” <a href="https://www.blackpast.org/african-american-history/declaration-independence-and-debate-over-slavery/">https://www.blackpast.org/african-american-history/declaration-independence-and-debate-over-slavery/</a> Jefferson later blamed the removal of the passage on delegates from South Carolina and Georgia and Northern delegates who represented merchants who were at the time actively involved in the Trans-Atlantic slave trade.”<br>I also watched the movie “1776” (again for so many times I can’t remember) in which the slavery controversy was basically portrayed as a South Carolina issue from Edward Rutledge (with North Carolina just going along with Rutledge’s lead and Georgia’s representative later supporting the Declaration as it was).<br>Chuck Huggins listed the signers who were slave owners (<a href="https://www.quora.com/How-many-signers-of-the-Declaration-of-Independence-were-slaveowners">https://www.quora.com/How-many-signers-of-the-Declaration-of-Independence-were-slaveowners</a> the discussion of which clarifies the list and offers sources for his statement). Of the 56 signers, Huggins lists 41 as owning (or having owned) slaves. The movie, suggests some didn’t or were going to release them and neither of those were (fully) true, e.g., Franklin apparently had a slave accompany him to France post the signing and Jefferson kept slaves well after that time. While Washington was not a signer, he was commanding the army at the time and had at least one slave pictured with him in a few paintings including the famous crossing of the Delaware one (<a href="https://www.blackpast.org/african-american-history/people-african-american-history/william-lee-aka-billy-lee-will-lee-1752-1810/">https://www.blackpast.org/african-american-history/people-african-american-history/william-lee-aka-billy-lee-will-lee-1752-1810/</a>).<br>So what about the “life, liberty and pursuit of happiness” part? It doesn’t say “life, liberty and happiness.” The first two are stated as absolute and “unalienable” (<a href="https://www.ushistory.org/declaration/document/unalienable.html">https://www.ushistory.org/declaration/document/unalienable.html</a> has an interesting take on the different appearances of “un” and “in” in different drafts). The Declaration, however, just says it is a right to pursue happiness, not to actually have it. Let’s pass on that for a moment and focus on the two the Declaration says are clear rights: life and liberty.<br>So what does a right to “life” and “liberty” mean? Certainly there were the concerns at the time of American colonists being killed/imprisoned without due process, having their property taken, etc. But let’s say that all stops as the end of the Revolutionary War was intended to do. Did the signers (and later those who wrote and signed the constitution) consider what it meant, to begin with, to have “life” guaranteed? What about people needing decent health, housing, and food to have “life” guaranteed? None of that is defined in the Declaration (or Constitution, for that matter). The rest of the Declaration after the paragraph about these rights is all about the offenses “the King of Great Britain” (George III) has committed.<br>Nothing more is said about securing such rights other than “That to secure these rights, Governments are instituted among Men” and that if government actions are “destructive of these ends”, people can overthrow such a government. It does say, though, that “light and transient causes” aren’t a reason to do that as “all experience hath shewn, that mankind are more disposed to suffer, while evils are sufferable, than to right themselves by abolishing the forms to which they are accustomed.” Does this express a view that people can’t be expected to deal with their suffering if they see them as “sufferable”? How many people have to believe that someone else’s suffering is “sufferable” or not before people, suffering or not, choose to do something about that?<br>What about “liberty”? That covers a great deal. How much “liberty” do people need or be entitled to. That one seems to have been debated ever since it was agreed to down to the present day when concerns for challenges to individual rights are expressed or defense of such challenges are stated. It does say that government should do things “most likely to effect their Safety and Happiness.”<br>So “Safety” seems to be a concern to achieve “life” and “liberty.” But we come back to the “pursuit of happiness.” “Happiness” covers as much territory as “liberty” since what constitutes “happiness” for one person may impinge on what another feels is their happiness. I doubt people can be minimally happy without the “decent health, housing, and food” I mentioned above. Should a government be held responsible when these are not available to everyone under its jurisdiction?<br>Finally, the quote noted above on the responsibility of government doesn’t say it should “effect” the “pursuit” of happiness. It says government should do things to “effect” happiness not just its pursuit. What were Jefferson and all the signers thinking the second paragraph of the Declaration meant?<br>One thing it says in the last paragraph of the Declaration is “That these United Colonies are, and of Right ought to be FREE AND INDEPENDENT STATES.” I believe signers from many states envisioned the post-Revolutionary governmental stance to be based on a confederation of “independent states” which would be “free” of too much centralized authority. Therefore, each state (and perhaps even parts of each state) would be left to decide for themselves what “life, liberty and pursuit of happiness” people would be allowed.<br>I have been reading a book by A. J. Jacobs entitled ‘The Year of Living Constitutionally.” He spent a year trying live exactly as he could determine the original Constitution stated people should live. Of course, he adopted the idea of living the way people at the creation of the Constitution lived or understood living to be. What interested me are some of the historical facts he unearthed to show the divergence of thought, and then the constraint of that thought, pre and post Constitution.<br>One item regarding “liberty” was that our sense of the first amendment was clearly not what people of the time envisioned it to be. There were many restrictions on what one could say, for example. Criticism of the government was not a widely accepted “liberty.” And not having established religion? States like Connecticut, Hew Hampshire, and New Jersey, for example, had official state religions (i.e., Congregational and Protestant). Finally, it took the 19th Amendment in 1920 to give women the right to vote. However, New Jersey allowed women to vote starting in 1790 but then rescinded that in1807 possibly due to criticism that the state was promoting a “petticoat” government.<br>In any case, “life, liberty and the pursuit of happiness,” as simple as that sounds perhaps bears a lot more consideration as does the entire second paragraph of the Declaration.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e19d1a735d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Malmedy, but What About Wereth?]]></title>
            <link>https://scott-duncan.medium.com/malmedy-but-what-about-wereth-7fe3eb960fbe?source=rss-74df688fc261------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fe3eb960fbe</guid>
            <dc:creator><![CDATA[Scott Duncan]]></dc:creator>
            <pubDate>Sun, 09 Jun 2024 17:53:23 GMT</pubDate>
            <atom:updated>2024-06-09T17:53:23.098Z</atom:updated>
            <content:encoded><![CDATA[<p>I imagine that, if you know much about the Battle of the Bulge in WWII, you have heard that at least 84 captured U.S. soldiers were assembled in a field near Malmedy, Belgium on December 17, 1944 by men of the 1st SS Panzer Regiment. The SS troops proceeded to machine-gun them down and left their bodies in the frigid weather. The claim was that the Germans had no facilities for prisoners and were on a schedule to advance as fast as possible so could not take them with the advance. A reason, not an excuse.</p><p>In July of 1946, the Nuremberg trials found 43 members of the Kampfgruppe Peiper guilty and sentenced them to be hung. This included their commander, Joachim Peiper who accepted responsibility for the actions of his men. Due to irregularities in how evidence was gathered, it was determined Peiper did not necessarily give the order for the massacre, so his sentence was changed to life imprisonment. Eventually, his sentence was commuted after 12 years in December, 1956.</p><p>However, have you heard about the Wereth massacre that occurred at the same time?</p><p>On that same day in 1944, German SS troops massacred 11 Black soldiers from the 333rd Field Artillery Battalion near the farming town of Wereth in Belgium. They were known as the “Wereth 11”:</p><p>· Curtis Adams of South Carolina</p><p>· Mager Bradley of Mississippi</p><p>· George Davis Jr. of Alabama</p><p>· Thomas Forte of Mississippi</p><p>· Robert Green of Georgia</p><p>· James Leatherwood of Mississippi</p><p>· Nathaniel Moss of Texas</p><p>· George Motten of Texas</p><p>· William Pritchett of Alabama</p><p>· James Stewart of West Virginia</p><p>· Due Turner of Arkansas</p><p>The 333rd was an all black unit and the 11 men had escaped capture, trudging through deep snow, avoiding roads to avoid German patrols. They carried only two weapons. They were eventually caught again at the Langer home where the family had been feeding them. To avoid repercussions to the family, they surrendered without resisting the German soldiers.</p><p>The atrocity against them, not far from the family’s home, included blows to the head, bayonet stabbings, multiple gunshots, and some bodily mutilations.</p><p>It would be hard not to consider some racial motivations behind the kind of treatment they suffered compared to the Malmedy murders which involved none of the individual, personal attacks.</p><p>This event was not never prosecuted at the Nuremberg trials. It was not recognized until decades after the war.</p><p>This Smithsonian video (from Facebook) discusses this massacre: <a href="https://www.facebook.com/watch/?v=343719004628604">https://www.facebook.com/watch/?v=343719004628604</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*lPR3cKwpfcDSbm9IQWUL0A.png" /></figure><p>Tina Langer, whose father sheltered 11 black American soldiers during World War II before German soldiers massacred them, stands in front of the Wereth 11 Memorial in Wereth, Belgium. (Scott Schonauer / S&amp;S)</p><p>Read more at: <a href="https://www.stripes.com/migration/belgian-villagers-remember-wereth-11-with-memorial-1.migrated">https://www.stripes.com/migration/belgian-villagers-remember-wereth-11-with-memorial-1.migrated</a><br>Source — Stars and Stripes</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fe3eb960fbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile agile agility]]></title>
            <link>https://scott-duncan.medium.com/agile-agile-agility-04e187e72668?source=rss-74df688fc261------2</link>
            <guid isPermaLink="false">https://medium.com/p/04e187e72668</guid>
            <dc:creator><![CDATA[Scott Duncan]]></dc:creator>
            <pubDate>Sun, 11 Feb 2024 21:23:42 GMT</pubDate>
            <atom:updated>2024-02-11T21:23:42.915Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>Agile agile agility</strong></blockquote><p>If you are familiar with Jeffrey Moore’s <em>Crossing the Chasm</em>, you know a key aspect of his model of the propagation of new ideas is that there is a point where ideas transition from Early Adopters to larg(er) Early Majority organizations. That is it goes from those who are early enthusiasts of an idea and cross a gap (the “chasm”) to those who need more confidence in the idea. The Early Majority organizations exhibit a pragmatism about adoption of new ideas and seek signs of legitimacy of those ideas. Beyond that we find Late Majority organizations who are conservative about adoption of new ideas and wait for Early Majority organizations to accept the new ideas (at least at some level). After the Late Majority are people/organizations consider Skeptics who may never adopt the new ideas.</p><p>I become aware of the Agile Manifesto’s values and principles in 2002. After attending my first Agile Development Conference in 2004, I decided that I want to work according to those values and principles and step away from the phased-sequential (“waterfall”) approach I had been involved with since the mid-1980s. Before that, I worked in small companies where I cannot say we had any specific lifecycle and much was done somewhat ad hoc. However, in one case, when I read <em>eXtreme Programming Explained</em> in 2002, it seemed to me that, in the early 1980s, we worked in a way that was similar in spirit to Agile ideas.</p><p>Now, during two decades pursuing Agile ideas, I have o heard people ask, “What is the definition of Agile?” or say, “There is no definition of Agile.” It seems to me that lack of clarity around Big “A” Agile, small “a” agile and agility has been a problem. I think part of this is because of the wide acceptance of Agile frameworks and their associated certification programs by the Early and Late Majority organizations seeking confirmation of the legitimacy of Agile ideas. For them, “Agile” has meant the structures and practices advocated by these frameworks and there are many of them.</p><p>But the authors of the Agile Manifesto had different ways they were practicing “little” methods before the Manifesto. When they came together and created the Manifesto, they adopted the word “Agile” (with the capital “A”). It was not necessarily a wildly popular choice for them, but it is what the settled on at the time. For me, therefore, the “definition” of Agile is what exists in the Agile Manifesto’s values and principles. Until that Manifesto, there was no Big “A” Agile. If an organization claims to be (or be doing) Agile, the Manifesto must be their definition.</p><p>Of course, before Big “A” Agile, there was always the word “agile” with the lowercase “a.” Dictionaries clearly defined with in terms suggesting things such as:</p><p>· marked by ready ability to move with quick easy grace;</p><p>· being resourceful and adaptable;</p><p>· quick and well-coordinated in movement.</p><p>Similarly, dictionaries will define “agility” as:</p><p>· the quality or state of being <a href="https://www.merriam-webster.com/dictionary/agile">agile</a>.</p><p>So, to be “agile” means to demonstrate behavior that fits the definitions above. For example, I think of mountain goats as being agile in the way they easily move in mountainous terrain. Another example would be gymnasts such as those performing on the balance beam as they perform actions on that narrow beam with great fluidity.</p><p>On the other hand, there is an aspect of being truly agile that the definitions do not explicitly state, though “well coordinated” approaches the idea. That aspect of being agile is maintaining stability while moving quickly and easily. If the mountain goat slipped on the rocks and the balance beam gymnast fell of the beam or otherwise missed a move frequently, we would not likely find them good examples of “agility.” I believe an important aspect of Agile ideas is how one maintains stability while carrying out the Manifesto’s values and principles. That stability contributes to confidence in what a team does so they feel willing to move forward easily and adaptably.</p><p>So, regardless of the practices an organization pursues to “do Agile,” they must be able to understand and show how they meet the Manifesto’s values and principles as well as maintain stability while they do so. People have said that, since it has been over two decades since the Manifesto was written, there are things that have been learned and things the Manifesto did not cover. I don’t question that, but this does not mean to me that the Manifesto values and principles have become obsolete as the base definition of “Agile.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=04e187e72668" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>