We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:<\/p>\n\n\n\n
Individuals and interactions <\/strong>over<\/em> processes and tools<\/p>\n\n\n\n Working software<\/strong> over<\/em> comprehensive documentation<\/p>\n\n\n\n Customer collaboration<\/strong> over<\/em> contract negotiation<\/p>\n\n\n\n Responding to change <\/strong>over<\/em> following a plan<\/p>\n\n\n\n That is, while there is value in the items on the right, Twenty-five years ago this week, from February 11-13, 2001, seventeen software practitioners met at a ski resort in Snowbird, Utah, to talk about the way they were building software and the frustrations they shared.<\/strong> This account draws on recollections from several participants and related materials.<\/p>\n\n\n\n The group at Snowbird was small and informal. Attendance was driven by interest and availability rather than titles or formal authority.<\/p>\n\n\n\n As Martin Fowler later wrote<\/a>, there was \u201cnothing particularly special about the seventeen of us who happened to be at Snowbird,\u201d and the group did not see itself as having any special status in the movement.<\/p>\n\n\n\n The meeting did not begin with a shared plan for the future. What participants shared was a dissatisfaction with the conditions many teams were working in.<\/p>\n\n\n\n In his history of the meeting, Jim Highsmith<\/a> wrote that much of the energy behind Agile was about values and culture rather than techniques, referring to what he called \u201cthe mushy stuff.\u201d<\/p>\n\n\n\n Expectations for the meeting were modest. In his recollection, Martin Fowler<\/a> wrote that he mainly hoped the group would get to know each other better and improve communication.<\/p>\n\n\n\n Participants came from different methods and perspectives, and early conversations focused on explaining and comparing those approaches. Several recollections describe a shift when the discussion moved away from defending individual methods and toward identifying what the group actually had in common.<\/p>\n\n\n\n Dave Thomas recalled that recurring themes began to surface as the conversation continued. During a break, he and Fowler worked at a whiteboard to capture what they were hearing.<\/p>\n\n\n\n \u201cSo we experimented with writing down our conversation that way: we prefer X over Y,\u201d Thomas wrote in Some Agile History<\/a>.<\/p>\n\n\n\n When participants returned from their break, the discussion continued around the emerging statements laid out on the whiteboard.<\/p>\n\n\n\n In a 10th anniversary video panel at Agile2011<\/a>, several authors described the moment when the values took shape. Ron Jeffries recalled, \u201cIt\u2019s hard now to imagine just how crystallizing that moment was\u2026 that was the moment when everything twisted, when everything turned. It was the pivotal event.\u201d<\/p>\n\n\n\n The shift was not the introduction of a new idea, but the explanation of shared priorities in language that the entire group could accept.<\/p>\n\n\n\n The final form of the values came through iteration and reduction.<\/p>\n\n\n\n Dave Thomas recalled that the initial list was longer:<\/p>\n\n\n\n \u201cI think we sat down after lunch with five bullets on the board,” he says.<\/a> “By the end of the afternoon, it was down to four, plus an introduction.\u201d<\/p>\n\n\n\n The comparative structure of the values emerged as the group worked to express priorities while still acknowledging value in the items on the right.<\/p>\n\n\n\n In his account, Martin Fowler<\/a> noted that the values were developed during the meeting itself, while the 12 Principles Behind the Agile Manifesto<\/a> took longer and required additional work.<\/p>\n\n\n\n The anniversary video<\/a> also describes techniques used during the meeting, including the use of index cards to surface strongly held beliefs and collective review of wording until full agreement was reached.<\/p>\n\n\n\n The group also needed a name.<\/p>\n\n\n\n In the 10th anniversary video<\/a>, Mike Beedle remarked that the group was \u201cextremely lucky\u201d in selecting the word because it already had meaning in the business world.<\/p>\n\n\n\n In his written recollection, Martin Fowler<\/a> explained that the group understood the word \u201cagile\u201d was not exclusive to their work and would be interpreted in different ways, but that they needed a term to describe the common views they held.<\/p>\n\n\n\n The authors did not see themselves as an authority over what would follow.<\/p>\n\n\n\n As Fowler wrote<\/a>, the seventeen “had ‘launched the ship,’ but saw no reason to have any special say in agile software’s future.”<\/p>\n\n\n\n In his own account, Bob Martin<\/a> described the Snowbird meeting as focused and collaborative, and noted that the formal creation of the Agile Alliance as a legal organization happened afterward.<\/p>\n\n\n\n The anniversary video<\/a> also includes reflections expressing the hope that Agile would eventually become normal practice rather than something treated as a special label.<\/p>\n\n\n\n Twenty-five years later, the Agile Manifesto still reflects the spirit of that weekend. It does not prescribe a system or claim authority. It offers a set of shared priorities and leaves room for judgment, context, and learning over time. Its influence has come less from detailed instruction than from the conversation it continues to invite.<\/p>\n\n\n\n This anniversary is a moment to recognize the ideas produced that weekend 25 years ago, but also the people who took part in that gathering and contributed to a document that has shaped how many teams think about their work.<\/p>\n\n\n\n With gratitude to the seventeen who came together at Snowbird in February 2001 and helped articulate the values that became the Agile Manifesto: Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, and Dave Thomas.<\/p>\n\n\n\n Twenty\u2011five years after the creation of the Agile Manifesto, the challenges facing organizations have evolved dramatically. Markets shift faster, technologies disrupt entire industries overnight, and global complexity demands new ways of working. Yet the spirit of that weekend in Snowbird endures: a belief that adaptability, collaboration, and human\u2011centered ways of working unlock better outcomes. <\/p>\n\n\n\n Today, those same foundational ideas extend far beyond software teams. Organizations now ask a broader, more urgent question: <\/p>\n\n\n\n PMI and Agile Alliance are carrying forward the intent of the original manifesto by helping organizations answer that question at enterprise scale. Enterprise<\/a> Agility<\/a> builds on Agile\u2019s core values and expands them to the entire organizational system\u2014where strategy, leadership, operating models, decision flow, governance, and culture must work together to deliver value with purpose and clarity in a constantly changing environment. This evolution reflects what executives across industries have told us: agility is no longer a team capability; it is an organizational one. <\/p>\n\n\n\n Just as the Agile Manifesto sparked a movement that reshaped how teams work, Enterprise Agility represents the next era\u2014helping organizations sense change earlier, respond with alignment and speed, and create environments where empowered teams can deliver value that truly matters. By building on the legacy of the original signatories and uniting the strengths of PMI and Agile Alliance, we are shaping a future where agility becomes a strategic advantage for every organization. <\/p>\n\n\n\n Read the Enterprise <\/a>Agility<\/a> report from PMI<\/a> and make sure to follow the Agile Alliance newsletter<\/a> for the announcement of the new Manifesto for Enterprise Agility<\/em> coming soon.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" A concise history of the Agile Manifesto\u2019s creation at Snowbird, told through participant recollections and the pivotal moments that shaped its four values, 25 years later. As well as a look forward at where Agile goes next.<\/p>\n","protected":false},"author":6000331,"featured_media":8104692,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_tec_requires_first_save":true,"_EventAllDay":false,"_EventTimezone":"","_EventStartDate":"","_EventEndDate":"","_EventStartDateUTC":"","_EventEndDateUTC":"","_EventShowMap":false,"_EventShowMapLink":false,"_EventURL":"","_EventCost":"","_EventCostDescription":"","_EventCurrencySymbol":"","_EventCurrencyCode":"","_EventCurrencyPosition":"","_EventDateTimeSeparator":"","_EventTimeRangeSeparator":"","_EventOrganizerID":[],"_EventVenueID":[],"_OrganizerEmail":"","_OrganizerPhone":"","_OrganizerWebsite":"","_VenueAddress":"","_VenueCity":"","_VenueCountry":"","_VenueProvince":"","_VenueState":"","_VenueZip":"","_VenuePhone":"","_VenueURL":"","_VenueStateProvince":"","_VenueLat":"","_VenueLng":"","_VenueShowMap":false,"_VenueShowMapLink":false,"_tribe_blocks_recurrence_rules":"","_tribe_blocks_recurrence_description":"","_tribe_blocks_recurrence_exclusions":"","ep_exclude_from_search":false,"_jf_limit_responses":"","footnotes":""},"categories":[182,883,890,183],"tags":[],"content_source":[],"class_list":["post-8104669","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-community","category-mindset","category-people","category-the-alliance"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8104669","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/6000331"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=8104669"}],"version-history":[{"count":30,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8104669\/revisions"}],"predecessor-version":[{"id":8105073,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/posts\/8104669\/revisions\/8105073"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8104692"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=8104669"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=8104669"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=8104669"},{"taxonomy":"content_source","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/content_source?post=8104669"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
we value the items on the left more.<\/strong><\/em><\/p>\n<\/blockquote>\n\n\n\nThe Beginning<\/h2>\n\n\n\n
They did not represent a single method, company, or organization. They did not arrive with a plan to launch a movement. By the end of the weekend, they had written a short statement of values that became the \u201cManifesto for Agile Software Development,\u201d or as most of us refer to it these days, simply the Agile Manifesto<\/a>.<\/p>\n\n\n\nWho Was in the Room<\/h2>\n\n\n\n
\n
What They Were Reacting Against<\/h2>\n\n\n\n
\n
The Whiteboard Moment<\/h2>\n\n\n\n
![\"Agile](\"https:\/\/agilealliance.org\/wp-content\/uploads\/2023\/03\/agile-manifesto-authors-wide-1024x381.jpg\")
<\/figure>\n\n\n\nHow the Four Values Emerged<\/h2>\n\n\n\n
Why the Name Mattered<\/h2>\n\n\n\n
\n
What They Hoped Would Happen Next<\/h2>\n\n\n\n
25 Years Later<\/h2>\n\n\n\n
The Next 25 Years: From Agile to Enterprise Agility<\/h2>\n\n\n\n
Are we built for change?<\/em> <\/h4>\n\n\n\n