Concepts

Sinra organizes work in six steps: Specify, Refine, Plan, Build, Verify, Learn. It is not a process to get certified in, it is the order in which a project moves forward, and the structure of the sidebar.

Cycles are Sinra's time-boxed work periods. Learn how they differ from traditional sprints and why they fit V-Model + Agile teams.

Issues are the fundamental unit of work in Sinra. Every specification, plan, task, and bug is an issue. Learn how they work, what fields they carry, and how each type carries a single status that matches its nature.

From requirement to proof: how Sinra links a specification to the plan and tasks that carry it out, and to the tests that verify it, and how a bug points at the feature it concerns.

Capabilities are Sinra's equivalent of epics, but with a key difference: a capability has a clear completion state. Learn how capabilities connect releases, issues, and QA into a traceable delivery unit.

A release in Sinra is a scope commitment, not just a deployment event. Learn how releases define what you deliver, connect to cycles and capabilities, and communicate progress to your whole organization.

Sinra's capacity system makes the fundamental project equation visible: what you want to deliver vs. what your team can actually do. Learn how availability rates, cycle capacity, and workload calculations work.

Sync events are Sinra's structured team synchronization moments: planning meetings, retrospectives, phase gate reviews, and post-mortems. Each has a precise role in the project lifecycle.