Sign in to create and edit playbooks. Sign In Register

Score Cycle Impact

CAS-2 Order: #2 Exploratory Data Analysis Has Dependencies

Updated 1 month, 2 weeks ago

Guidance

Purpose

Reconstruct touch vs wait, score impact, and mark where AI could help. Do not design agents.

Formula

  • wall-clock = touch_time + wait_time
  • effort = people_in_role × touch_time
  • impact = effort + (people_downstream × wait_time)

Inputs

  • Filled streamlit/data/value_stream.yaml.
  • sql/stage_touch_wait.sql and skill Cycle Impact Scoring → Recipe.
  • Skill AI Leverage Mapping → Recipe.
  • Role capacity file streamlit/data/role_capacity.yaml.

Steps

  1. Open streamlit/data/cost_of_delay.yaml. For each stage on the map, set touch_time and wait_time from catalog events (issue → PR → CI → merge → deploy). Never treat wall-clock as effort. Label measured vs assumed. Pin query_execution_id from sql/stage_touch_wait.sql (workgroup from the contract; extract $.payload.*).
  2. Fill streamlit/data/role_capacity.yaml: people_in_role, people_downstream, source of the assumption. Do not infer headcount from unique GitHub authors.
  3. Join issue↔PR on Closes #N in payload, never repo or timestamps alone.
  4. Compute effort, wall-clock, impact (worked sample in the YAML: Sec wait 48h × 8 downstream + 2h touch × 1 person = 386). Keep ToC #1 visible (toc_rank_1: true).
  5. Fill streamlit/data/ai_opportunities.yaml: opportunity names, ai_can_help yes/no/unknown, effort S–XL. Low hanging fruit = high impact AND AI-yes AND low effort. No agent products.
  6. Those three YAML files are artifacts Delivery Cycle Reconstruction, Cost of Delay Ranking, and AI Opportunity Prioritization Matrix.

Done when

  • Ranking has impact scores with measured/assumed labels and one named #1 constraint.
  • Matrix has at least the high-impact boxes scored; no agent names.

Feeds

Look until trusted, then Triage: Eliminate / Automate / Delegate.

Skip

Do not optimize a non-constraint. Do not put AI on a low-impact stage because it is easy.

Details
Order:
#2
Phase:
Predecessor:
CAS-1 Map the BizDevTestSecOps Value Stream
Successor:
CAS-3 Look until Trusted
Created:
Aug 31, 2026
Last Updated:
Sep 17, 2026
Workflow
Constraint and Flow Analysis

Reconstruct the delivery cycle, score impact, look until the ranking can be trusted, then decide what to drop or automate. …

View Workflow
Assigned Agent
Operations Analyst

Agent: Operations Analyst Role Turns the catalog into an understanding of where the delivery cycle …

Required Skills
Rules
Input Artifacts 1
Output Artifacts 4