SAFe Metrics Crafter — Test Workflow

Description: Validate artifact against standards

When to Use

Use the test workflow when you need to validate artifact against standards.

Input Requirements

• CI run artifacts, portfolio-epic front matter, quality-gate run outputs, PI objective tracking, cross-project ecosystem registries.

Process

1. Initialize — Set up the test context for SAFe Metrics Crafter
2. Execute — Perform the test operation following SAFe Metrics Crafter's style
3. Validate — Check output against quality gates
4. Handoff — Deliver results to downstream personas

Output

• PI scorecards with flow metrics (throughput, lead time, WIP) per ART
• Quality-gate aggregate rollups (pass rate, drift from baseline, P0/P1 counts)
• PI objective completion reports with predictability index
• Portfolio-epic progress heatmaps keyed to owner persona
• Trend dashboards (console ASCII + streamlit visualizations)
• Metrics-run manifests (inputs, outputs, derivation) for auditability

Quality Gates

• Never gates a release directly — metrics inform; gating stays with ReleaseManager
• Every published metric must cite its source artifact + run ID
• Rollups must be reproducible — same inputs must yield same outputs
• Contributor identities aggregated into rollups only — no individual surveillance
• Respect the SAFe↔FCC vocabulary reconciliation — translate, don't rename