I Got Obsessed With Killing Scrum. So I Built a World Out of 12 AI Agents.

A developer built Bodhiorchard, an open-source platform that replaces Scrum and Jira with 12 specialized AI agents and a 3D world. The platform uses Agent-Driven Development (ADD) with a single Business Understanding Document (BUD) as the source of truth, and rewards quality over output. It is self-hosted, runs on a Mac mini, and is available under Apache 2.0.

This is a submission for Weekend Challenge: Passion Edition I built Bodhiorchard — an open-source platform that replaces Scrum, Jira, and the team wiki with 12 specialised AI agents and a living 3D world you can actually walk around in. I call the methodology Agent-Driven Development ADD . Instead of story points, planning poker, and a graveyard of stale Confluence pages, the work lives in one place: a BUD Business Understanding Document — a single, vector-indexed source of truth that carries a feature from a Slack conversation all the way to production. The agents handle the busywork I never wanted humans doing: triage, design drafts, tech plans, standups, test plans, estimation, retros. Your repos show up as trees in an orchard. Features are branches . The whole team walks around as avatars — WASD to move, emotes, houses you upgrade with points you only earn when something actually ships to prod and stays healthy. The scoreboard is the part I'm proudest of: it rewards quality, not output . Ship a BUD to production: +1. A bug escapes to prod: -1. It scores the things AI is bad at and humans are good at. Honest status: the platform, the BUD lifecycle, the code-dependency graph, skill profiling, and the 3D world are all live . The fully autonomous execution loop is still being built — today it's agents-assisted, human-in-the-loop. I'd rather undersell it than lie to you. Two views ship today: GARDEN the orchard and GRAPH a cross-repo dependency graph with Bus Factor, Threats, and BUD-stage lenses . Two Slack bots sit on top — one triages new requests and kills duplicates before they become tickets; the other answers plain-English questions like "are we on track for go-live?" straight from the live BUD. Open source, Apache 2.0, self-hosted — it runs on a Mac mini. The open-source, self-hosted alternative to Jira & Scrum — AI agents run the process end-to-end, developers earn XP for what actually ships, and your data never leaves your machine. Website https://bodhiorchard.ai/ · Quick Start https://github.com/mickyarun/bodhiorchard quick-start · Why Bodhiorchard https://github.com/mickyarun/bodhiorchard why-bodhiorchard · The Twelve Agents https://github.com/mickyarun/bodhiorchard the-twelve-agents · Docs https://github.com/mickyarun/bodhiorchard documentation · FAQ https://github.com/mickyarun/bodhiorchard faq ▶ Watch the demo — a Slack message becomes a scoped, estimated BUD. No sprints, no story points, no standups. Bodhiorchard replaces sprint, scrum, and Jira ceremony with Agent-Driven Development ADD — twelve specialised AI agents handle the busywork triage, specs, estimates, test plans, retrospectives while humans keep the decisions that matter, and developers earn XP for the work that actually reaches production. It's a self-hosted Jira alternative for the full lifecycle: intake → spec → design → development → testing → deploy → retrospective. The data plane stays on your hardware; inference runs through your choice of agent CLI… This is a solo project. Nights and weekends, on my own, because I couldn't leave it alone. The stack: FastAPI + Python 3.12 on the backend, Vue 3 + PlayCanvas for the 3D world, Postgres + pgvector for the BUD memory, and Redis underneath. Inference runs through Claude Code today, with Ollama and OpenAI on the roadmap so you can bring your own model. The hard part wasn't the agents. It was the ontology — deciding that a BUD, not a ticket, is the atom of work, and that everything estimates, design, tests, the retro's estimated-vs-actual drift table hangs off that one object. Once that clicked, the agents became small. Each one reads BUD context over a local MCP server and writes back only in the three creative phases where a human is still driving. The 3D layer looks like the toy. It's actually the point. A dependency graph as a spreadsheet is a chore. A dependency graph as an orchard you can lose an afternoon in — that's the thing that made me want to open it every day. I've spent years watching good engineers spend half their week on Jira instead of building. That quietly made me angry. This is the project I built to get that time back — mine first, then anyone else's who wants it. "Build well. Then go outside." That's the whole idea. Bodhi means awakening. An orchard is a grove you tend on purpose. The name is the pitch. If you've ever felt sprints were broken and wanted to do something about it instead of just complaining in retro — clone it, break it, tell me where I'm wrong. That feedback is the only prize I'm actually chasing.