Goals and artifacts

Skopo keeps delivery work connected to the outcomes it is meant to produce. Goals capture the measurable change a project is trying to create. Artifacts are the durable working agreements, definitions, and evidence records the methodology requires. Both are managed from the Delivery view.

Goals and outcomes

A goal in Skopo is a measurable outcome with a description, a metric, a numeric target, and a target date. Goals represent the result the project is trying to produce, not the work being done to produce it.

Each project can have multiple active goals. The Delivery view shows each goal's current progress relative to its target, along with how many artifacts are approved and whether release readiness criteria are met.

Work items, releases, and artifacts can all be linked to goals. Those links make it possible to answer: which work is advancing this outcome, and is it enough?

Artifacts

Artifacts are the durable records that a methodology requires its teams to maintain. The set of available artifact types is defined by the active methodology. Examples include:

• Scrum: Product Goal, Sprint Goal, Definition of Done.
• Kanban: Definition of Workflow, Service-level expectation.
• Shape Up: Pitch, Appetite, Hill Chart.
• Extreme Programming: Stories, Acceptance tests, Coding standard.
• Scrumban: Delivery goal, Definition of Done, Service-level expectation.
• Dual-Track Agile: Opportunity, Hypothesis, Experiment result, Product outcome.

Artifacts have structured forms appropriate to their type — a Definition of Done is a checklist; a Pitch captures problem, solution sketch, appetite, and no-gos; an Experiment result records hypothesis, method, and findings. Artifacts can progress through a review lifecycle — typically from an initial draft, through review, to an approved state that satisfies the relevant policy checks.

Artifacts support the same collaboration model as other records: comments, @mentions, and watchers.

Traceability

Skopo connects goals, artifacts, policies, work items, releases, and rituals into a traceable chain. From the Delivery view you can see:

• which goals are active and what progress they show;
• which artifacts exist and which are approved;
• which quality gates have evidence and which are still outstanding;
• whether release readiness criteria are satisfied.

From a work item you can navigate to the goal it advances or the risk it creates. From a ritual outcome you can navigate to the decision it recorded. This traceability is persistent — it survives methodology migrations because item identities are stable.