--- title: From Methodology to Source Code description: "Scrum was a process framework designed for people. Its principles and practices were documented in advance and relied on teams to apply them throughout development. This approach suited an environment in which writing code was a major constraint and methodologies primarily helped coordinate human effort. Emerging agentic development frameworks serve a different purpose: they provide instructions and structures that AI agents can access and execute during development. Methodology is increasingly becoming an executable component of the software development process, changing how these frameworks are designed, distributed, and applied." image: https://elaxtra.com/hubfs/From%20Methodology%20to%20Source%20Code.png --- [Skip to content](https://elaxtra.com/insights/from-methodology-to-source-code#main-content) [![](https://elaxtra.com/hs-fs/hubfs/ELAXTRA%20MANUAL-16-4.png?width=150&height=47&name=ELAXTRA%20MANUAL-16-4.png)](https://elaxtra.com/) - [Corporate Development](https://elaxtra.com/corporatedevelopment) - [Value Creation](https://elaxtra.com/valuecreation) - [About](https://elaxtra.com/about) - [Insights](https://elaxtra.com/insights) Open main navigation Close main navigation - [Corporate Development](https://elaxtra.com/corporatedevelopment) - [Value Creation](https://elaxtra.com/valuecreation) - [About](https://elaxtra.com/about) - [Insights](https://elaxtra.com/insights) - [Contact Us](https://elaxtra.com/contact) [Contact Us](https://elaxtra.com/contact) [All posts](https://elaxtra.com/insights/all) October 27, 2026 # From Methodology to Source Code By  Elaxtra Advisors  ·  3 minute read Scrum was a process framework designed for people. Its principles and practices were documented in advance and relied on teams to apply them throughout development. This approach suited an environment in which writing code was a major constraint and methodologies primarily helped coordinate human effort. Emerging agentic development frameworks serve a different purpose: they provide instructions and structures that AI agents can access and execute during development. Methodology is increasingly becoming an executable component of the software development process, changing how these frameworks are designed, distributed, and applied. --- Today's agentic development frameworks are distributed as files within software repositories. GitHub's Spec Kit structures development around a constitution, specification, plan, tasks, and implementation. BMAD uses specialized personas that produce versioned artifacts and pass them between stages. AWS has proposed AI-Driven Development Life Cycle (AI-DLC), which replaces the traditional two-week sprint with a shorter cycle called a bolt, measured in hours or days. It also introduces units of work in place of epics and a collaborative planning process called Mob Elaboration. Rather than simply describing how teams should operate, these frameworks provide instructions and context that agents can use while executing tasks. Rules governing what an agent can modify, for example, can become explicit constraints within the development workflow rather than guidelines that depend entirely on individual compliance. The executable nature of these methodologies also changes how they are distributed and adopted. They are installed through package managers or incorporated into repositories, making GitHub stars one readily available indicator of community interest. Spec Kit has surpassed 130,000 stars, approaching the count for Claude Code itself, while OpenSpec, GSD, and BMAD each have approximately 50,000 to 67,000. These figures should be interpreted cautiously: star counts do not decline when projects lose momentum, and they do not directly measure active usage or enterprise adoption. In the absence of standardized certification or adoption surveys for these frameworks, however, they remain a visible, if imperfect, indicator of developer interest. A more consequential change is the application of version control to development methodology. Teams can fork a process, compare revisions, pin it to a specific version, and roll back changes if they degrade agent performance. This allows methodologies to evolve at the pace of software, although faster iteration does not guarantee better results. Thoughtworks placed spec-driven development in the Assess ring of its Technology Radar rather than Adopt, citing concerns about elaborate, opinionated workflows and specifications that can become too lengthy to review. These limitations raise a broader question about whether manually defining increasingly detailed instructions for AI models can scale effectively across complex development environments. The terminology used by these frameworks can obscure how their roles differ from traditional team structures. BMAD, for example, uses personas such as analyst, architect, scrum master, and developer, borrowing familiar titles from software development methodologies while assigning them different functions. In Scrum, roles establish responsibilities and accountability among people. In agentic frameworks, personas define the context, tasks, deliverables, and permissions available to an agent. Although the structure resembles an organizational chart, it functions more like a mechanism for controlling an agent's scope and authority. These changes also raise questions about where commercial value will accrue. Spec Kit, OpenSpec, BMAD, and GSD are available at no cost, and most use the MIT license. As development methodologies become freely accessible and reproducible, differentiation may shift toward the surrounding infrastructure: agent harnesses, evaluation systems, and platforms that govern how much change reaches production without human review, as discussed in ([https://elaxtra.com/insights/the-improved-economics-of-agentic-services](https://elaxtra.com/insights/the-improved-economics-of-agentic-services) ). The frameworks do not resolve the main constraint: code review. Telemetry across millions of pull requests shows that machine-generated changes take several times longer to receive an initial review, are substantially larger, and are accepted at roughly one-third the rate of human-written changes. AI can increase code production, but it does not automatically expand review capacity. Frameworks that emphasize specification and alignment attempt to address this challenge earlier in the development process, reinforcing the role of human judgment and coordination explored in ([https://elaxtra.com/insights/emergence-of-the-ai-agent-orchestrator](https://elaxtra.com/insights/emergence-of-the-ai-agent-orchestrator)). For technology services firms, these frameworks have direct operational implications. By dividing development into smaller units of work, the frameworks can shorten delivery cycles and change how engagements are scoped and priced. Work that once spanned a quarter may now be organized into cycles lasting hours or days, challenging pricing models built around longer timelines and labor inputs. As discussed in ([https://elaxtra.com/insights/pricing-services-from-time-to-outcomes](https://elaxtra.com/insights/pricing-services-from-time-to-outcomes)), this shift increases the relevance of pricing models tied to deliverables and outcomes rather than time alone. With methodologies freely available and development cycles becoming shorter, the ability to review outputs, maintain quality, and apply human judgment becomes a more consequential source of differentiation. Scrum emphasized designing processes around the most costly and primary constraint, human time. That principle still applies, but in agentic development, the constraint is increasingly the capacity to review and validate AI-generated work. Elaxtra Advisors is an M&A and value-creation advisory firm that assists institutional investors, private equity-owned platforms, and strategic acquirers invest and create value in worldwide technology services companies. Please contact us to explore potential partnerships. Share: [mailto:?body=https://elaxtra.com/insights/from-methodology-to-source-code](mailto:?body=https://elaxtra.com/insights/from-methodology-to-source-code) ![](https://elaxtra.com/hs-fs/hubfs/ELAXTRA%20MANUAL-16%20-%20copia.png?width=140&height=46&name=ELAXTRA%20MANUAL-16%20-%20copia.png) Elaxtra Advisors is the highest conversion corporate development team in technology services. [Home](https://elaxtra.com/) [Corp Dev](https://elaxtra.com/corporatedevelopment) [Value Creation](https://elaxtra.com/valuecreation) [About](https://elaxtra.com/about) [Insights](https://elaxtra.com/insights) [Contact Us](https://elaxtra.com/contact) New York Office 386 Park Ave South, 18th Floor, New York, NY 10016  ## Subscribe to our newsletter ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Elaxtra Advisors", "url" : "https://elaxtra.com/insights/author/elaxtra-advisors" }, "dateModified" : "2026-10-27T16:23:37.664Z", "datePublished" : "2026-10-27T16:23:37.000Z", "headline" : "From Methodology to Source Code", "image" : [ "https://elaxtra.com/hubfs/From%20Methodology%20to%20Source%20Code.png" ], "mainEntityOfPage" : { "@id" : "https://elaxtra.com/insights/from-methodology-to-source-code", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject" }, "name" : "Elaxtra Advisors" } } ``` ```json { "@context" : "http://schema.org", "@type" : "Article", "author" : { "@type" : "Person", "name" : [ "Elaxtra Advisors" ] }, "datePublished" : "2026-10-27T16:23:37+0000", "description" : "Scrum was a process framework designed for people. Its principles and practices were documented in advance and relied on teams to apply them throughout development. This approach suited an environment in which writing code was a major constraint and methodologies primarily helped coordinate human effort. Emerging agentic development frameworks serve a different purpose: they provide instructions and structures that AI agents can access and execute during development. Methodology is increasingly becoming an executable component of the software development process, changing how these frameworks are designed, distributed, and applied. ", "headline" : "From Methodology to Source Code", "image" : "https://45774781.fs1.hubspotusercontent-na1.net/hubfs/45774781/From%20Methodology%20to%20Source%20Code.png", "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "" }, "name" : "Elaxtra Advisors" }, "url" : "https://elaxtra.com/insights/from-methodology-to-source-code" } ```