Endava 如何利用 Codex 构建代理型组织

Endava是一家全球软件承包公司，其工程师遍布欧洲、美洲和亚洲，是Codex的早期采用者。对于一家以向银行、保险公司、零售商和媒体公司交付优质软件为核心业务的企业而言，其改进效果十分显著。

“我们从自己编写大量代码，转变为现在监督Codex能够产出的工作，”Endava欧洲区域首席技术官Joe Dunleavy表示，“输出质量呈指数级提升。”

Endava现在自称是一家智能体组织：一家将资深专业知识编码到智能体中，使其与团队在整个客户参与生命周期（从项目接洽、构思到最终交付）中协同工作的公司。

“Codex真正帮助我们实现的是，让小型团队在非常紧凑的时间框架内交付巨大的价值。”

— Joe Dunleavy，Endava欧洲首席技术官

放大团队中的每一项技能

Codex改变了高级和初级工程师的合作方式，Endava全球智能体架构高级副总裁Mike Krolnik表示。“像我这样来自复杂环境的高级架构师，能够清晰地表达我们的需求，而Codex将这些信息转化为团队中初级成员易于理解的内容。从初级人员的角度来看，他们能够采用这个工具，并创造出高级、成熟水平的输出。”

在实践中，这意味着将通常保留给高级工程师的工作交给初级开发人员，而Codex则充当最佳实践和架构决策的指南。“我可以给Codex一个观点，当他们在工作时，它会帮助他们理解这个观点，”Krolnik解释道。“他们可以就自己不理解的事情提问。作为开发过程中的学习工具，我能够将自己的经验编码，让Codex与团队合作，向他们传授软件架构和开发方面的更好实践。”

这种知识转移最终成为智能体组织的核心价值和优势之一。通常需要多年结对编程、代码审查和指导才能获得的资深判断力，现在变成了团队可以实时协作的东西。这改变了组织对初级开发人员的指导方式。单个资深人员的视角，编码到Codex中，可以同时指导多个经验不足的团队。

“Codex已经成熟为一款工具。我们将其用于需求分析、设计、规范、开发和运维；它是贯穿我们整个生命周期的通用桌面智能体。”

— Mike Krolnik，Endava全球智能体架构高级副总裁

数周的工作，压缩到数天

当资深判断力随时可用时，交付的每一步都能得到改进。Endava不再将分析、设计和构建视为由专家交接的连续阶段。“过去，每个阶段都需要数天或数周的分析，”Krolnik说。“现在，通过Codex将分析、设计和构建打包在一起，我们可以将其作为一个统一的工具来完成。”

最近一个跨团队的项目展示了这在实践中的样子。Endava的法律团队向工程部门提出了一个复杂的问题：需要根据一套特定标准审查数千页的合同。将律师的需求转化为工程部门可以构建的内容，通常需要数周的反复沟通。相反，Krolnik的团队录制了与法律相关方进行的两个小时的深入会议，将会议记录输入Codex，并利用它生成了一个可用的需求规范。原本可能需要一两周修订的工作，被压缩成两次一小时的会议，并产出了可用的规范。

同样的时间节省也体现在客户工作中。Endava的团队现在在客户会议中实时生成设计文档、图表和规范，以阐述想法。“你可以让它绘制提议的软件架构图，以便客户更容易理解，”Krolnik说。“它极大地加速了反复沟通的过程，真正打开了许多可能性的大门。”

领导力经验

• 将资深人员知识编码。 最大的杠杆作用来自于将资深架构师的判断力捕获到Codex中，这样初级团队成员在执行时就能获得资深指导。
• 将Codex视为桌面智能体，而非编码助手。 Endava最大的突破来自于将Codex应用于需求、设计、客户沟通以及代码之外的运维工作。
• 不要只是空想，要真正去尝试！ “第一条建议是，你需要超越思考你想做什么，而是真正投入进去尝试，”Dunleavy说。Endava给刚起步的团队的建议是：首先选择一个非编码的工作流程：需求分析、设计文档或客户沟通。看到Codex全部价值的最快方法，是在你的团队以前从未使用过编码工具的地方使用它。

“Codex放大了我所拥有的每一项技能，而每个学会使用它的人，他们所拥有的每一项技能也都会被放大。”

— Mike Krolnik，Endava全球智能体架构高级副总裁

Endava, a global software contracting firm with engineers across Europe, the Americas, and Asia, has been an early adopter of Codex. For a business built around shipping quality software for banks, insurers, retailers, and media companies, the improvements have been substantial.

“We went from producing a lot of the code ourselves to now overseeing the work that Codex can produce,” says Joe Dunleavy, Endava’s regional CTO for Europe. “The quality of output has just gone up exponentially.”

Endava now calls itself an agentic organization: a company where senior expertise is codified into agents that work alongside teams across the entire client engagement lifecycle, from intake to ideation and, finally, delivery.

“What Codex has really helped us do is have small teams of people deliver massive value in a very condensed timeframe.”

—Joe Dunleavy, CTO Europe, Endava

Magnifying every skill on the team

Codex changes how senior and junior engineers work together, says Mike Krolnik, Endava’s Global SVP of Agentic Architecture. “Senior architects like myself, coming from complex environments, are able to articulate what we want, and Codex makes that an accessible piece of information for the more junior people on the team. And from the junior perspective, they’re able to adopt this tool and create senior, mature-level outputs.”

In practice, that means giving junior developers work that would normally be reserved for senior engineers, with Codex acting as a guide on best practices and architectural decisions. “I can give Codex a point of view, and when they’re working, it will help them understand this point of view,” Krolnik explains. “They can ask questions about things they don’t understand. As a learning tool during development, I’m able to take my experience, codify it, and have Codex work with the team to teach them better practices in software architecture and development.”

This knowledge transfer ends up being one of the core values and advantages of an agentic organization. Senior judgment, which normally comes through years of pairing, code review, and mentoring, becomes something a team can work alongside in real time. This changes how mentorship can happen for an organization’s junior developers. A single senior’s perspective, encoded into Codex, can guide multiple less-seasoned teams in parallel.

“Codex has matured as a tool. We use it for requirements analysis, design, specifications, development, and operations; it’s a general desktop agent across our whole lifecycle.”

—Mike Krolnik, Global SVP of Agentic Architecture, Endava

Weeks of work, compressed into days

When senior judgment is always available, every step of delivery can be improved. Endava no longer treats analysis, design, and build as sequential stages handed off between specialists. “Each of these stages used to take days or weeks of analysis,” Krolnik says. “Now with Codex packaging together analysis, design, and build, we can do that as a single unified tool.”

A recent cross-team engagement shows what that looks like in practice. Endava’s legal team brought engineering a complex problem: thousands of pages of contracts to review against a specific set of criteria. Translating what the lawyers needed into something engineering could build against would normally take weeks of back-and-forth. Instead, Krolnik’s team recorded a two-hour deep-dive meeting with the legal stakeholders, fed the transcript to Codex, and used it to generate a working requirements specification. What could have taken a week or two of revision was compressed into two one-hour meetings and produced a usable spec.

The same time-saving is also showing up in client work. Endava’s teams now produce design documents, diagrams, and specifications live in client sessions to illustrate ideas. “You can tell it to draw a diagram of the proposed software architecture so it’s easier to understand for our clients,” Krolnik says. “It rapidly accelerates the back-and-forth, and it really opens a lot of doors.”

Leadership lessons

• **Codify your seniors.**The largest leverage comes from capturing senior architects’ judgment in Codex, so junior team members get senior guidance as they execute.
• Treat Codex as a desktop agent, not a coding assistant. The biggest unlocks at Endava came from applying Codex to requirements, design, client communication, and operations alongside code.
• Don’t just think about it, really try it! “The first piece of advice is you need to get beyond thinking about what you want to do and actually get in and try it,” Dunleavy says. Endava’s advice to teams just starting out: Pick a non-coding workflow first: requirements analysis, design documentation, or client communication. The fastest way to see Codex’s full value is to use it in a place where your team has never used a coding tool before.

“Codex magnifies every skill I have, and everybody who learns how to use it gets every skill they have magnified.”

—Mike Krolnik, Global SVP of Agentic Architecture, Endava