Productivity · App Starter
Project Management Template
Boards, sprints, and burndown over one task schema — generated into a codebase your team runs on its own terms.
Describe how your team plans and ships work, and Dual7 generates this tracker around it: six connected entities, kanban and list views, sprint ceremonies, and progress charts, as a full-stack app in your repository. When the process changes, you change the tool — in code, the same afternoon.
- 6 core entities
- Kanban + list views
- Code you own
- Vibe + Governed modes
01 · Data model
What's inside: the data model
Every tracker is six tables and a thousand opinions. This starter generates the six tables and leaves the opinions to your team — statuses, workflows, and views are code you shape, and each screen below is a projection of this schema.
| table | what it holds |
|---|---|
projects | Containers for a body of work — goal, timeframe, members, and the boards and sprints inside it. |
boards | Configurable views with columns, swimlanes, and filters — multiple boards can slice one project differently. |
tasks | The atom of work: title, description, status, assignee, estimate, due date, and relations to other tasks. |
sprints | Timeboxed iterations with committed scope, capacity, and the history burndown draws from. |
comments | Threaded discussion on tasks with mentions and edit history — decisions stay next to the work. |
labels | Cross-project markers for type, urgency, or theme — the pivot axis for filters and reports. |
02 · Screens
Signature modules
Kanban and list views
01The same tasks render as a drag-and-drop board or a sortable, bulk-editable list — column changes and status updates are one write to one table. Views are components in your repo, so the variant your team wishes existed can.
Sprint planning
02Pull from the backlog into a timeboxed sprint against a visible capacity line, then carry unfinished work forward explicitly at the close. Scope added mid-sprint is marked as such — so the retro argues from data, not recollection.
Assignees and workload
03Every task carries an owner, and the workload view totals estimates per person across projects. The overloaded engineer shows up as a bar on a chart before they show up in a resignation letter.
Burndown and progress charts
04Burndown per sprint, cumulative flow per board, and cycle-time trends — computed live from task history in your own database. When leadership wants a different cut, that's a query you write, not an export you massage.
03 · Process
How it works
- 1You
Describe how your team works
Sprints or continuous flow, strict statuses or loose ones, one team or nine — say it plainly. The starter generates the workflow you described, not a default you must un-configure.
- 2Vibe mode
Adjust it in Vibe mode
Add a blocked status, split a board by client, make estimates required — conversationally, with every change landing as reviewable code. The tool keeps up with the process instead of lagging it.
- 3Governed mode
Roll out through the governed pipeline
Deploy to your infrastructure through approval gates with an audit trail. Your roadmap, backlog, and delivery history stay in a database you control end to end.
04 · Fit
Who the Project Management starter is for
Teams whose tracker grew hostile
Heavyweight trackers accrete required fields, mandatory workflows, and admin-only settings until updating a task feels like filing taxes. A generated tracker contains exactly your process — and when the process simplifies, the tool can actually follow it down.
Companies consolidating tool sprawl
One team on a board tool, another in a spreadsheet, leadership in slides — status meetings become reconciliation meetings. One tracker over one schema, extended per team in code, gives everyone the same truth with their preferred view on top.
Teams handling client or regulated work
When task data includes client names, unreleased features, or audit-relevant decisions, per-seat cloud trackers add a vendor to every disclosure conversation. Self-hosting the tracker keeps the work about the work.
Builders who want the tracker in the stack
Deploys that close tasks, alerts that open them, dashboards that join delivery data to business data — trivial when the tracker shares your database and codebase, and a permanent integration project when it doesn't.
05 · Yours
Customize it, own it
Make it yours
First, make the vocabulary and workflow yours: rename sprints to cycles, add a blocked-by-client status, require estimates only on engineering boards, define the label taxonomy your reports will pivot on. In Vibe mode each is a sentence, and each lands as inspectable code.
Then wire it into how you actually ship: connect your repository so merges move tasks, add an approvals column for release-gated work, build the client-facing read-only view your PM keeps mocking up. There's no runtime dependency on Dual7 — it's your app, extended however your team extends apps.
Why a starter, not a subscription
Per-seat tracker pricing has a quiet corollary: the record of how your team works — every estimate, every slipped date, every decision thread — sits in someone else's product, readable through whatever API tier you rent. This starter generates that system of record as code in your repository, on your infrastructure, at infrastructure cost.
What you take on is operating it, and the governed pipeline is designed to make that a non-event: approval-gated deploys, an audit trail of changes, and regeneration for structural evolution. Your process will change; the point is that the tool can change with it, deliberately.
06 · Industries
Industry versions
Agency Project Management
A tracker that knows the client is in the room — scoped boards, retainer burn, approval loops — in code your agency owns.
Creative Project Management
A tracker that thinks in deliverables and review rounds, not just tasks — generated into code your studio owns.
Software Project Management
Epics, sprints, releases, and triage in one schema — a tracker your engineering team owns and can finally script.
Project Management template — frequently asked questions
What's in the box when I start from this template?
A working tracker generated into your own codebase: projects, boards, tasks, sprints, comments, and labels, with kanban and list views, sprint planning, workload visibility, and burndown charts. It deploys on your infrastructure and your delivery history stays in your database.
Can it do both scrum and kanban?
Both, per project — sprints with capacity and burndown where teams run scrum, continuous-flow boards with cumulative flow diagrams where they don't. Mixed organizations aren't an edge case; the schema treats sprints as optional structure, not a mandate.
How many users and projects can it handle?
It's a standard full-stack app on a relational database — the practical limits are your hosting, not a plan tier. There are no per-seat fees to shape who gets access; contractors, stakeholders, and view-only executives are all just rows.
Can I connect it to our code repository and CI?
Yes, and it's natural work because the tracker is a normal app: webhook handlers that move tasks on merge, links from tasks to pull requests, deploy events on the timeline. You're integrating your own schema, not negotiating a marketplace app's permissions.
Does it work for construction project management?
For construction you want the dedicated construction management starter instead — it models RFIs, change orders, subcontractors, and daily logs, which are the actual objects of jobsite work. This starter is built for team task and sprint workflows.
Can clients see project status without full access?
Role-scoped views are part of the schema, so a client can get a read-only window on their project's board and milestones without seeing internal comments or other clients' work. What each role sees is a rule in your code, as strict as you need.
Related
Dual7 App Starters
Build your Project Management on your terms
Boards, sprints, and burndown over one task schema — generated into a codebase your team runs on its own terms. Describe your version to start — the output is a project you own.