Why we built it
A bootcamp is a software team in training. Somewhere along the way it started being run like a group chat.
Bootcamps run on chaos: syllabi live in spreadsheets, task tracking happens in shared chat channels, and student progress is reconstructed from memory at demo day. Leads burn their evenings reconciling who did what, while students squint at a shared board that shows everyone's work instead of their own.
Agilytics started with a simple observation. A bootcamp cohort is structurally a product team: there is a scope (the curriculum), a backlog (the projects), a cadence (the sprints), and a definition of done (graduation). The tools should say so. Instead of forcing education into generic project software, we built the workspace a bootcamp would design for itself.
From the field
The mission
Give every bootcamp the operational clarity of a well-run engineering org.
- Leads stop reconciling and start running: assignments, sprints, permissions, and reporting in one place, updated the moment work moves.
- Students see exactly their work: a private instance of every ticket they own, with the spec one click away in the Document Hub.
- Program offices get proof, not anecdotes: velocity, predictability, and scope churn exported in one click.
The north star
One system, four surfaces
Everything a bootcamp needs, nothing it doesn't. Four surfaces, one shared model.
| Surface | What it does | Why it matters |
|---|---|---|
| Task Board | Projects, sprints, and tickets with drag-and-drop kanban, bulk assignment by track, and live sprint countdowns. | Work flows PENDING to DONE in the open, so progress stops being a guess. |
| Document Hub | A living knowledge base: root documents, subpages, attachments, and a full markdown editor with autosave. | Specs live one click from the tickets that reference them. |
| Permissions | Role-based access with explicit document grants, resolved server-side on every request. | Students only ever receive what they're allowed to see, even in the payload. |
| Agile History | Velocity trends, predictability scores, scope churn, and burndown per project, exportable to XLSX. | Course correction becomes a meeting agenda instead of a debate. |
Design principles
Five rules that shape every screen, every API, and every permission check.
- Enforce where it counts: permissions are resolved on the server for every request, never trusted from the client.
- Explicit beats implicit: grants, not guesses. Access is granted to exactly the right people, or it doesn't exist.
- Proof, not anecdotes: if it can be measured, it is measured, and the numbers export.
- Keep the loop tight: open sprints never auto-close, so late work doesn't silently vanish.
- Fast over fancy: every load is optimized, every document tree is lazy, every edit autosaves. The tool gets out of the way of the work.
Who it's for
One workspace, four roles. Each sees exactly what their job requires.
| Role | Sees & does | Boundaries |
|---|---|---|
| ADMIN | Full workspace control, invites, approvals, and permissions. | Oversight role for the program office. |
| LEAD | Everything: sprints, documents, members, agile history, exports. | Creates and deletes workspace-level structures. |
| SUB_LEAD | Task board and analytics; assists with execution and review. | Documents and members stay read-mostly. |
| STUDENT | Their private ticket instances, assigned work, and granted documents. | No cross-student visibility, ever. |
Built for the whole cohort
Where it's going
The coordinate system is just getting its bearings.
- Deeper analytics: per-track comparisons and cohort-level trends on top of the existing velocity and burndown.
- Smoother sync: real-time board updates so a move by one student appears on the lead's screen without a refresh.
- Integrations: calendar feeds for sprint timelines and gradebook export for program reporting.
- Templates: proven project and document structures for common bootcamp tracks, ready in one click.
Say hello
Questions, ideas, or a cohort you want to run on Agilytics.
The fastest way to see what Agilytics does is to use it. The guide walks through a workspace from zero to a closed sprint, and the workspace link gets you in the door.