Your view, not the process’s
The official tool answers to a workflow and a permission model you did not choose. Yours can track what you actually need to see, at the granularity you need, without raising a change request.
For pragmatic agilists
The big tools arrive with someone else’s process baked in — ceremonies you did not choose, fields you must fill, permissions you must ask for. Hakagile is the companion you keep beside them: your boards, your standups, your own evidence, shaped by what actually happens on the ground.
Invitation only while the product is young.
Dogma is easy to install and hard to live with. Most agilists end up keeping a private set of notes the official tool has no room for. This is that space, made useful.
The official tool answers to a workflow and a permission model you did not choose. Yours can track what you actually need to see, at the granularity you need, without raising a change request.
Run the daily from a roster, capture each person’s notes, and turn an impediment into a tracked card in one step — instead of it evaporating into a chat thread.
Cycle time, lead time, bounce-backs and blockage causes, measured from your own board history. Numbers to bring to the retrospective, rather than a quote from a framework.
Columns you define, drag-and-drop, WIP limits. A fixed intake column on the left and a single Done on the right, so a board cannot be configured into something that no longer flows.
Keys, types, criticality, estimation in points or t-shirts, dates, sprints, labels. Markdown descriptions, attachments, comment threads, decisions and linked items.
Subtasks are real cards in a swimlane under their parent, and the parent’s column is computed from its children — a story can never sit ahead of its own work.
HQL filters the board and your project list alike: type = bug, criticality = high, member = me. Plain words work too.
A month view holding both. Per-person notes, impediments promoted to the board, and a side-by-side compare against the previous session. Everything auto-saves.
Cycle and lead time, blocked time, bounce-backs, blockage by cause, workload per member, overdue and in-progress counts — computed from history, not hand-entered.
No client, no imposed tool, no ceremony you have to justify. The same thing works as your only tool: one project per product, a board you can actually keep current, and metrics that tell you whether you are shipping or spinning.
Hakagile runs in the browser and is invitation-only for now — each request is reviewed by hand. Tell us a little about how you work and we will be in touch.
Runs in any modern browser. There is no mobile app yet.