Knowledge Management

Keep institutional knowledge organized and easy to reuse.

Overview

Knowledge management keeps delivery context reusable across Projects.

It reduces rework caused by repeated discovery.

Key Concepts

• Source of truth: the record that should be referenced during delivery
• Traceability: links between meeting context, requirements, tasks, and tests
• Retention: how long information remains available (plan dependent)

How It’s Used

Use Artifacts for reference material and outputs that need a stable home.

Use comments and history for decisions made in the flow of work.

Use Console for retrieval across Projects when the location is unknown.

Benefits

• Faster onboarding for new delivery teams
• Cleaner audits for approvals and scope changes
• Less duplication across Projects

Setup Steps

1

Standardize capture locations

1. Store reference files as Artifacts.
2. Record decisions in comments using a consistent pattern.

2

Link sources instead of duplicating text

Link requirements, tasks, and meeting records to preserve origin context.

3

Define ownership

Assign ownership for the core knowledge set, such as process definitions and templates.

Best Practices

• Prefer stable naming across Projects.
• Archive outdated content when auditability matters.
• Keep Segment Types stable to protect reporting continuity.

Summary

Start here:

• What Are Artifacts?
• Console AI Search

Related:

• Comments and History
• Audit Trail