Generic project tools don't know what a DA submission is, or why "blocked" and "on hold" are different problems. Scrumban is a board built for one landscape studio's real flow — it speaks AEC stages, separates waiting on yourself from waiting on an authority, and tracks the milestones that actually move a project forward.
Generic boards treat every task the same. A landscape studio doesn't work that way. A project moves through real stages — Concept → SD → DD → DA → CD → Tender → Construction → Closeout — and the words that matter on a given day are specific: a DA submission, an IFC issue, a site inspection.
Two kinds of stuck look identical on a normal board but aren't: Blocked means you're waiting on your own dependency; On Hold means you're waiting on a client or an authority — and you manage them completely differently. A generic tool forces you to translate your discipline into its vocabulary, every single day. The gap is that the board doesn't understand the work it's supposed to track.
The domain comes first. A dependency-free Domain layer encodes the discipline — the stages, the Blocked-vs-On-Hold distinction, the AEC milestones — so the rules of landscape practice live in code, not in how someone happens to label a column. Around it sit Application, Infrastructure and a WinUI front end, kept in clean layers so the studio's logic stays portable as the app grows.
"The board should already know your discipline — not make you translate it into someone else's columns."
The app is built outward from the studio's daily rhythm: see everything at once, then drill into a single project, a single board, a single task — without ever leaving the AEC vocabulary.
The whole studio at a glance — 3 to 15 concurrent projects, their stages and what needs attention. Live and verified.
点Seven columns — Backlog · Ready · In Progress · Review · Blocked · On Hold · Done — with drag-drop and a task-detail popup. The active build.
线Stage timelines and AEC milestones — DA submission, IFC issue, site inspection — mapped across the year. Next on the path.
面Stages, Blocked-vs-On-Hold and AEC milestones modelled in a zero-dependency Domain layer before any UI.
The studio-wide overview is built and verified against real concurrent projects.
The seven-column board with drag-drop and task detail — the current focus.
Stage timelines and milestone tracking, building out from the board.
From a local SQLite tool to a multi-user studio app on Oracle Cloud — and eventually beyond landscape.
Where it's heading is a tool a landscape studio can open and recognise immediately — its stages, its kinds of stuck, its milestones already there. No translation tax, no generic columns bent to fit. The dashboard already proves the model; the board makes it daily.
Each page a 点, each link a 线, the whole a 面. Hover a node to trace its connections.