sinra

Workflow

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.

What Is the Workflow?

The Workflow is the thread that runs through Sinra. It splits the life of a feature into six steps, always in the same order:

StepThe question it asksWhat you work with
SpecifyWhat must the product do?Capabilities, specs, Spec Pipeline
RefineIs it clear enough to commit?Refinement queue, estimation sessions
PlanWhat do we ship, and when?Releases, cycles, backlog, planning meetings
BuildWho does what now?Issues, current cycle, current release
VerifyIs it ready for production?Testings, phase gate reviews
LearnWhat do we change next time?Retrospectives, postmortems

Steps and Objects

Sinra rests on four objects: capabilities, issues, cycles and releases. The Workflow does not replace them, it puts them in order:

  • Objects answer “what?”: the thing you are working on.
  • Steps answer “when?”: what should be done now.

A single capability goes through all six steps. It is written in Specify, estimated in Refine, placed in a release in Plan, delivered through its issues in Build, tested in Verify, then reviewed in Learn.

The V-Model Without the Jargon

Read in order, the six steps draw a V:

Specify                         Learn
   Refine                   Verify
       Plan             
            Build

The first three steps go down: you clarify before you produce. Build is the bottom. The last two go back up: you verify what was specified, then draw lessons for the next specification.

This is what ties the V-Model to short cycles. The V brings rigor (nothing is built without a spec, nothing ships without verification). Cycles bring the rhythm: the loop repeats with every release, not once per project.

What the Workflow Is Not

  • Not an enforced process: no step is blocking. A small team can go from Specify to Build without a refinement session.
  • Not a certification: there is nothing to learn beforehand. The six words are in the sidebar.
  • Not a waterfall: several capabilities sit at different steps at the same time. The Workflow describes the path of a feature, not the team’s calendar.

In the Application

The sidebar shows these six steps in its Workflow section. Each step groups the screens that matter at that point of the project. The Data section, right below, gives access to the complete lists. See Navigation for the detail of each entry.

Sync events fall naturally along this path: the planning meeting in Plan, the phase gate review in Verify, the retrospective and the postmortem in Learn.