hn.today

Agile Manifesto for Agents

debarshibasak.github.io32 points8 comments
Screenshot of Agile Manifesto for Agents

Agent-first development is a proposed way for enterprise teams to use coding agents without confusing rapid code production with successful delivery. Its central argument is that agents make clear scope, coordination, review, and operational accountability more important - not less. The approach combines explicit requirements and dependency planning, short iterative delivery cycles, and quality built into each increment. Teams should agree on outcomes, boundaries, constraints, and acceptance criteria before production work, while using time-limited prototypes to investigate important unknowns. Preparation should resolve questions that could affect architecture, security, or commitments, without pretending every implementation detail can be predicted.

The method’s 12 practices call for named human owners, versioned shared records, agreed interfaces before parallel work, and bounded agent tasks with stopping rules. Parallel activity should stay within the team’s ability to integrate and review; acceptance should rely on evidence that can expose mistaken assumptions, including checks of failure behavior and security. Agent access must be limited, and delivery must include the documentation, monitoring, recovery plans, and operational ownership needed to run the system. Teams should measure outcomes such as customer use, defects, incidents, delivery time, review delays, and total costs - not code or prompts produced. After each increment, they should apply lessons to requirements, tools, and tests so knowledge persists beyond a single engineer or agent session.

Read on debarshibasak.github.io8 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Programming

Aristotle Expands into Rust

Aristotle Expands into Rust

Aristotle has expanded its formal verification platform to Rust, allowing developers to prove code meets specifications and contains no undefined behavior, including in unsafe blocks. It can also verify that Rust rewrites behave like their original C code, targeting critical software such as smart contracts and infrastructure. (harmonic.fun)

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.