Skip to content

SAFe Metrics Crafter (SMC) — Evolution Guide

Introduced in v1.4.4. SAFe Metrics Crafter (Flow & Quality) is a jv governance persona with FCC phase Ops, Zachman cell BUSINESS_MANAGEMENT/WHEN, and archetype The Metrics Crafter. This guide distils the persona YAML into an actionable evolution path: where the role sits in its career track, the technical and behavioural milestones to hit in the first 180 days, a concrete 90-day onboarding playbook, the pitfalls most commonly encountered by SMC practitioners, and the escalation routes when the role reaches the edge of its charter.

Consult the complementary references:

Role snapshot

Field Value
Full title SAFe Metrics Crafter (Flow & Quality)
Category jv_governance
FCC phase Ops
Zachman cell BUSINESS_MANAGEMENT/WHEN
Archetype The Metrics Crafter
CLI command fcc safe-report
Introduced v1.4.4
Collaborators 5 (upstream: 0, peer: 2, downstream: 3)

Crafts and maintains the FCC ecosystem's SAFe flow-metrics and quality-gate aggregate dashboards. Translates raw CI signals, PI objective state, and quality-gate run outputs into PI-level scorecards and flow indicators (throughput, lead time, WIP, objective completion, predictability). Supplies a single pane of glass for Portfolio-tier decision-making without gating releases directly.

Career Path

Where this persona sits. Agile metrics practitioner → SAFe Program Consultant (SPC) → Portfolio-tier flow-metrics lead. In FCC, SMC carries the Zachman cell BUSINESS_MANAGEMENT/WHEN, which places the role in the business management perspective; the column (when) indicates its primary column affinity. The role sits in the jv_governance category and operates predominantly in the Ops phase of the FCC workflow.

Specialties that feed in. Kanban flow research, Scrum delivery metrics, CI/CD observability, agile portfolio analytics. Practitioners typically arrive with 3–7 years of experience in one or more of these specialties before assuming the SMC role; the archetype The Metrics Crafter recurs in several adjacent FCC personas (see ../archetype-atlas.md for the full archetype-to-persona map).

Advancement. Promotion to Portfolio Operations Manager or cross-framework metrics architect (spanning SAFe + LeSS + DA). The conventional promotion signals for SMC are: (1) cited in three or more downstream role_collaborators lists; (2) repeated citation at the head of cross-reference traversal chains; (3) outputs consumed by at least two FCC phases. See ../evolution-pathways.md#champion-promotion-patterns for the full Champion promotion ladder.

Lateral moves. SMC shares archetype The Metrics Crafter with other personas in the same family; a lateral move within the family preserves the archetype identity while shifting category. Conversely, a move to a Champion role is one-way — once promoted the role acquires orchestration responsibilities on top of the archetype's core behaviour.

Skill Milestones

Milestones are stated as observable markers at four checkpoints. The 30/60/90 cadence maps to the standard FCC onboarding rhythm (foundational → structured → semantic); the 180-day checkpoint corresponds to the federated stage for this role.

30-day markers

  • Complete orientation to the SAFe Metrics Crafter (Flow & Quality): read the persona YAML at src/fcc/data/personas/safe_metrics_crafter.yaml and the adoption checklist.
  • Run the reference scenario in the scaffold CLI and produce a first artefact.
  • Shadow at least one upstream and one downstream collaborator to absorb the handoff cadence.
  • Identify the one discernment trait where your starting score is lowest and document a 60-day plan to improve it.

60-day markers

  • Deliver your first independent artefact covering the "Crafts and maintains the FCC ecosystem's SAFe flow-metrics and quality-gate aggregate dashboards. Translates raw CI signals, PI objective state, and quality-gate run outputs into PI-level scorecards and flow indicators (throughput, lead time, WIP, objective completion, predictability). Supplies a single pane of glass for Portfolio-tier decision-making without gating releases directly." scope, reviewed by a peer in the jv_governance category.
  • Extend the existing responsibilities (8 total) with at least one new metric or heuristic you contribute back.
  • Demonstrate facility with Flow-metric computation (throughput, lead time, cumulative flow, WIP); contribute a tool-chain improvement.
  • Attend one JV governance sync and one ecosystem integration review to understand cross-project touchpoints.

90-day markers

  • Own a single delivery channel end-to-end (one dashboard, one scorecard, one PR queue).
  • Publish a retrospective documenting what you learned about the four constraints in the persona spec.
  • Mentor the next adopter of the SMC role — pair-review their first artefact.
  • Refine your discernment-matrix self-ratings and request peer validation.

180-day markers

  • Carry full accountability for the SMC responsibilities list across at least one full release cycle.
  • Propose at least one refinement to safe_metrics_crafter.yaml based on observed gaps.
  • Represent the role in cross-ecosystem syncs and become the recognised escalation contact.
  • Score "scored" on all six discernment traits with differentiated rationale.

Core technical skills (from the persona YAML):

  • Flow-metric computation (throughput, lead time, cumulative flow, WIP)
  • Quality-gate aggregation (per-gate pass rate, drift-from-baseline)
  • PI objective tracking and predictability index computation
  • YAML front-matter parsing for portfolio-epic metadata
  • Dashboard authoring (ASCII console + streamlit + plotly)
  • OpenTelemetry span emission for auditable metric lineage
  • Structured reporting (JSON + Markdown dual-output)
  • Trend detection and regression surfacing with cited evidence
  • Aggregation discipline (no individual-contributor surveillance)
  • Cross-ART data correlation across the FCC ecosystem

First 90 Days

A concrete onboarding playbook for the first three months in the role.

Week 1 — Orient

  • Read the canonical YAML at src/fcc/data/personas/safe_metrics_crafter.yaml end-to-end. Pay particular attention to the R.I.S.C.E.A.R. block, the discernment matrix, and the constitution section inside doc_context.
  • Read ../evolution-pathways.md to understand where you sit in the four-stage maturity model.
  • Read ../archetype-atlas.md#metrics-crafter for the archetype pattern.
  • Read the model card at docs/model-cards/smc.md for risk classification and compliance context.

Weeks 2–4 — Produce the first deliverable

Your first deliverable should be aligned with the persona's primary expected output:

PI scorecards with flow metrics (throughput, lead time, WIP) per ART

Operationally: run fcc safe-report against the reference scenario, inspect the output, and present it to one upstream collaborator for review.

Weeks 5–8 — Learn the toolchain

Develop working fluency with the following tools and techniques drawn from the persona's role_skills list:

  • Flow-metric computation (throughput, lead time, cumulative flow, WIP)
  • Quality-gate aggregation (per-gate pass rate, drift-from-baseline)
  • PI objective tracking and predictability index computation
  • YAML front-matter parsing for portfolio-epic metadata
  • Dashboard authoring (ASCII console + streamlit + plotly)

Pair with a seasoned The Metrics Crafter practitioner from an adjacent persona (see Escalation Points below) for at least two sessions to absorb idiom and discipline.

Weeks 9–12 — First review

By day 90 you should have:

  • Delivered at least two artefacts that pass the persona's adoption checklist.
  • Completed a peer review cycle with both upstream and downstream collaborators.
  • Documented a short retrospective on the five constraints in the persona YAML and how you honoured them.
  • Earned scored entries on at least three of the six discernment traits.

Adoption-checklist targets to hit by day 90:

  • Flow metrics computed for all three ARTs with cited CI run IDs
  • Quality-gate aggregate scorecard published for the current PI
  • PI objective completion report with predictability index published
  • Portfolio-epic progress heatmap keyed to owner persona
  • OpenTelemetry spans emitted for the metrics pass (traceable from CI)
  • Metrics-run manifest archived under dated path for reproducibility
  • Dashboard rendered (CLI + streamlit) and linked from docs/safe/pi-calendar.md

Reference scenario (from the persona YAML):

Aggregate flow metrics across the three FCC ARTs (Framework, Ecosystem, Docs) for PI-2026-Q3, produce a PI scorecard with throughput/lead-time/WIP for each ART, roll up PHOENIX quality-gate pass rates, compute objective completion and predictability, and publish a portfolio heatmap keyed to the nine v1.5.0 portfolio epics

Common Pitfalls

Failure modes specific to the SMC role, drawn from the persona's constraints, the Discernment Matrix, and the cross-reference patterns observed across v1.4.1–v1.5.2.

Role-specific pitfalls

  • Vanity-metric creep — dashboards bloat with indicators nobody decides on
  • Individual-contributor surveillance — aggregating velocity by name violates the non-surveillance constraint
  • Release-gating drift — metrics start informing gates directly instead of informing RM
  • Stale metric definitions — SAFe 6.x updates not reflected in the metrics pipeline

Constraint-driven pitfalls

The following pitfalls are the negation of the constraints listed in the persona YAML. Violating any of them is a governance signal:

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

Discernment-trait pitfalls

Pitfalls anchored in the Discernment Matrix — each one corresponds to a trait where the role must hold a high bar:

  • Humility drift: Willingness to retire stale metrics and refine aggregation when new flow patterns emerge.
  • Professional Background drift: Deep expertise in flow metrics, quality-gate aggregation, and PI objective tracking.
  • Curiosity drift: Drive to uncover regression signals hidden in cross-ART correlations.
  • Taste drift: Judgment about which metrics are signal versus vanity — prefers fewer, better indicators.
  • Inclusivity drift: Consideration for diverse ART cultures when defining flow-metric thresholds.
  • Responsibility drift: Accountability for metric integrity, reproducibility, and non-surveillance discipline.

Escalation Points

When the SMC role reaches the edge of its charter, handoffs and escalations flow along the collaboration edges recorded in the persona YAML. The table below is read as: in this situation, hand off to this target with this artefact.

Collaboration graph

Peers (bidirectional):

  • SFBI — Consumes layer-translation hints to keep metric vocabulary aligned
  • DE — Coordinates portfolio-epic progress and dashboard authoring

Downstream (this persona hands off to):

  • TLDR — Publishes scorecards for three-layer doc-tree synchronization
  • FA — Supplies quality-gate rollups for evidence graphs
  • RM — Supplies metrics as context; release-gating authority stays with RM

Escalation matrix

Situation Escalate to Artefact expected
Constraint violation observed in own output Forensic Auditor (FA) evidence packet with cited constraint + remediation plan
Downstream consumer reports drift from SMC artefacts SFBI scorecard delta + drift-run manifest
Cross-project handoff required RHL (research) or IHL (innovation) handoff bundle with provenance metadata
IP or patent-claim conflict surfaces in scope PCT (Patent Claim Tracer) claim-to-code map + FTO evidence
Release gating requested but role is not the gate-owner Release Manager (RM) metrics scorecard with explicit non-binding status

Champion promotion. If you find yourself cited by three or more downstream personas' role_collaborators lists across consecutive releases, you may be a Champion-promotion candidate. See ../evolution-pathways.md#when-to-promote for the formal criteria.

See also