Creating Artifacts

Overview

Artifact creation standardizes where reference material lives.

It reduces repeated searches across external folders and message threads.

Key Concepts

• Account Artifact: reusable reference available at Account scope
• Project Artifact: delivery-specific reference available inside a Project
• Linking: adding references from requirements, tasks, and tests

How It’s Used

Create Account Artifacts for shared standards and templates.

Create Project Artifacts for delivery evidence and working references.

Benefits

• Clear separation between reusable standards and delivery-specific content
• Faster retrieval during governance reviews
• Better traceability from scope to evidence

Setup Steps

Select the creation path based on the scope.

• At Account Level
• At Project Level

Best Practices

• Use a stable folder structure aligned to governance.
• Link Artifacts from requirements and tasks instead of copying content into descriptions.
• Keep file names consistent across Projects to support reuse.

Summary

Create Artifacts at the correct scope, then link them to delivery work for traceability.