Skriv tries to be the most easy-to-use software (do you know you can tell Skriv to use your own terminology?), but you need to know a few key concepts:

Project: A project is something you can work on. It can be “done” (finished).

A project as some properties:

  • Title (mandatory)
  • Value (see below)
  • Template (see below)
  • Deadline, which can be a given date or a milestone (see below)
  • Text
  • Attached files
  • Activated steps (see below)
  • Stakeholders (some of them could have an assigned role, see below)
  • Comments

The value of a project is a number that helps you to set its priority.

Workflow: This is a repeatable pattern of activities (Wikipedia). Each activity is called a step (see below). Most of the time, a project must go through different steps in order to be completed.

Organization: It's a group of projects which are based on the same workflow. In Skriv, organizations are separated from each other, each one having its own configuration, steps, users, roles, templates and milestones.

Role: In an organization, roles are used to defined the different kind of users, and how they interact on their projects.

When people are appointed to a project, it is possible to define their roles. Then Skriv will be able to assign the project to them at the right moment, depending of the step that is currently waiting to be done.

Step: As seen above, a step is a subdivision of a workflow.

On a project, a step may be assigned to a user (direclty or through her role) who will have to “do it” (complete the task represented by the step). Optionally, a step could be assigned to a “validator user” (again, directly or through her role); then the step will be ended when it is done and validated.

Steps have a configured duration (in days); these durations are used to compute the deadlines of a project's steps.

Template: A template is a pratical use case of a workflow that could be used on a project.

You may have a single workflow, but different way to use it, each way being a subset of the workflow. The most simple usage is to define templates depending of projects size: small projects will have fewer activated steps, and step durations are short; bigger projects will have more activated steps, and step durations are bigger too.

Milestone: A milestone is used to define a point in time. It has an optional starting date and a mandatory deadline. If both dates are given, it's a cycle or a sprint more than a real milestone.

When a project is created, it could be linked to a milestone. If you look at an organization's list of projects, you'll see that projects are grouped by milestone. It's easy to change a project's deadline by changing its milestone (using drag'n drop on this list).