TrawpieDocs Guide Open Trawpie
Use cases

A software team

A small team shipping an app: versions and branches on the board, sprints, GitHub, a beta test, and decisions on record.

Updated 11 Nov 2026 · 1 min read

A six-person team building an app, shipping a release every few weeks, with code on GitHub.

Releases on a line under the weeks; branches curve off while they’re being built.
Set this upHow
VersionsSettings ▸ Features ▸ Versions; add v1.0, v1.1, v1.2 on the release line
WorkflowSoftware: Backlog → In progress → Code review → Done
SprintsTwo weeks each, with a goal, drawn above the weeks
GitHubSettings ▸ Integrations ▸ GitHub; a branch or PR with the task’s reference links itself
DecisionsA decision matrix on tasks like “Database choice”
Example
Alex plans v1.1 for Friday. Six tasks carry the v1.1 tag; two have branches, feature/booking-flow-v2 and fix/duplicate-push-tokens. Clicking v1.1 lights them up: four done, two to go.
The software sample team in the demo opens on its release line.