Skopo documentation

Welcome to Skopo. This documentation covers everything from creating your first workspace to customising how your team works.

What Skopo is

Skopo is a project workspace that adapts to how your team delivers. You choose a delivery methodology when you create a project, and Skopo configures the right work-item types, board views, workflow states, rituals, artifacts, and metrics for that methodology. Switching from one approach to another is an explicit, previewed migration — not a destructive reset.

Core ideas

Methodology as configuration. Your chosen methodology is not a label or a column preset. It is a versioned configuration that controls available work-item types and fields, workflow states and WIP rules, rituals and their expected outputs, artifacts, release policies, and health signals. All methodologies share the same rendering engines; only the definitions differ.

One base methodology, optional practices. Each project runs one base methodology — for example, Scrum. You can then layer in optional practices, such as test-driven development or pair programming, without switching the base.

Stable work-item identity. When you migrate a project to a new methodology, type and status mappings may change, but every work item keeps its ID and full history.

Rituals create durable outcomes. Completing a ritual persists structured outcomes: selected work, decisions, action items, risks, goal links, and a metric event — not just session notes that disappear after the meeting.

Where to start

If you are new to Skopo, read the Getting started guide to create a workspace, set up your first project, and add your first work item.