sinra

Every screen, before you sign up.

Sinra's real interface, captured from the app. Demo data, untouched screens.

Try free for 14 days Browse the screens
Current cycle: date, status and time progress, issue count, and the issue list grouped by status.
The cycle your team is in right now: how far the dates have run, how far the work has, and every issue underneath.

Follow the product, step by step.

The rail below mirrors the Workflow of Sinra's sidebar, from spec to lessons learned. What you see here is what you get on day one.

Specify
Refine
Plan
Build
Verify
Learn
The Spec Pipeline: capabilities in columns by the writing status of their spec.
Where every spec stands, at a glance: to write, in progress, in review, ready. Drag a card to change its status.
Two workflows

Writing and development advance in parallel

Every other tool gives an issue one status. Sinra gives it two: where the specification stands, and where the code stands. You build both lists yourself.

  • Product writes while developers build
  • No issue waits on a status that means two things at once
  • A spec can be finished long before the branch is
Writing status and development status configured as two separate lists.
Capacity

You find out someone is overloaded before the cycle starts

Sinra adds up estimated time per person and per team and compares it to the availability you set. The warning arrives during planning.

  • Availability per person, per team, in percent
  • Estimated against real capacity, per cycle
  • The overflow is shown, not hidden in a total
Workload per person against capacity for a cycle.
Specification

Spec writing has its own board

Product owners track specifications the way developers track code, grouped by capability, filtered by release.

  • Columns by writing status
  • Grouped by capability, so a late feature is obvious
  • Drag a card to change its status
Spec pipeline board grouped by capability.
Quality

Tests are attached to the thing they check

A test case points at a capability and its acceptance criteria. A release cannot claim to be ready while its tests say otherwise.

  • Reusable test templates
  • A named tester, with their workload counted
  • Acceptance recorded against the release
A test case with its scope, its steps, its expected result and its acceptance status.

And the rest of it.

Everything below ships in the same account. Nothing here is an add-on or a paid tier.

Projects Long-range view of planned capabilities
All cycles Past, current and planned, in one list
Bulk edits Change status or release on a whole selection
Pages Documentation, organised by category
Templates Reusable pages, issues and tests
Global search Shift + F, from anywhere
Labels Across issues, capabilities and tests
Platforms Where your product runs
Categories Structure for the knowledge base
Teams and roles Ownership, permissions and availability
Notifications Mentions and assignments
API tokens For your own integrations

Open it on your own backlog.

Try free for 14 days Book 20 minutes with Thomas