init: company-haness 설계

2026-07-23 17:49:00 +09:00
parent 57d1bab894
commit f668d6a158
962 changed files with 98989 additions and 1 deletions
@@ -0,0 +1,203 @@
+team-topology-map:
+  version: 1
+  source-document: IT 대기업 직무 성장 분석.md
+  purpose: Map each AI role to the large-scale IT operating model so workflow routing preserves business, platform, enabling, and specialist responsibilities.
+
+  role-count-policy:
+    total-ai-role-agents: 62
+    topology-is-role-count-increasing: false
+    gtm-revenue-role-agents: 10
+    explanation: Team topology, EA layers, Golden Path, SLO, Shift-left Security, and GTM revenue stack are operating lenses for routing existing role agents. GTM revenue roles are counted only because roles.yaml explicitly defines 10 additional role agents.
+
+  governance-and-orchestration-roles:
+    mission: Set direction, balance executive tradeoffs, manage workflow state, and approve or escalate decisions.
+    default-roles:
+      - EXEC-CEO
+      - OPS-ORCH
+      - EXEC-CTO
+      - EXEC-CPO
+      - EXEC-CFO
+      - EXEC-COO
+      - EXEC-CPTO
+      - EXEC-VPENG
+
+  team-types:
+    stream-aligned:
+      mission: Deliver end-to-end customer or business-domain value.
+      primary-interaction: consume-platform-and-enabling-guidance
+      workflow-use:
+        - product discovery
+        - customer problem solving
+        - feature implementation
+        - experiment learning
+      default-roles:
+        - PROD-PM
+        - PROD-PO
+        - DES-PROD
+        - DES-INTERNAL
+        - ENG-FE
+        - ENG-BE
+        - ENG-BEGEN
+        - ENG-PRODSERVER
+        - ENG-PRODUCTMINDED
+        - ENG-SW
+        - ENG-FEUX
+        - DATA-ANALYST
+        - OPS-CH
+        - OPS-CREW
+
+    enabling:
+      mission: Remove knowledge gaps, technical debt, process friction, and organizational bottlenecks across teams.
+      primary-interaction: short-term-collaboration-and-coaching
+      workflow-use:
+        - business capability mapping
+        - value stream improvement
+        - quality improvement
+        - security guidance
+        - productivity improvement
+      default-roles:
+        - STR-ANALYST
+        - UX-RESEARCHER
+        - ARCH-BA
+        - ARCH-BIZANALYST
+        - ARCH-EA
+        - QA
+        - SEC-ENGINEER
+        - SEC-APPSEC
+        - SEC-CHAMPION
+        - ENG-PRODCHAPTER
+
+    complicated-subsystem:
+      mission: Own deep specialist subsystems that should be exposed to product teams through simple interfaces.
+      primary-interaction: x-as-a-service-interface
+      workflow-use:
+        - complex architecture decision
+        - technical product design
+        - specialized engine or subsystem work
+        - high-complexity data/application/technology architecture
+      default-roles:
+        - PROD-TPO
+        - ARCH-SOLUTION
+        - ARCH-SYSANALYST
+        - ARCH-DATA
+        - ARCH-APP
+        - ARCH-TECH
+        - ARCH-SWAT
+        - ENG-DESKTOP
+        - DATA-BIGDATA
+
+    platform:
+      mission: Provide self-service internal platforms, golden paths, common components, and safe deployment foundations.
+      primary-interaction: platform-as-a-product
+      workflow-use:
+        - golden path design
+        - internal developer platform
+        - reusable components
+        - observability and reliability
+        - secure paved road
+      default-roles:
+        - PROD-PPO
+        - DES-PLATFORM
+        - ENG-FEPLAT
+        - ENG-PLATSERVER
+        - INFRA-DEV
+        - INFRA-PLATFORM
+        - INFRA-DEVOPS
+        - SRE
+        - SEC-DEVSECOPS
+        - DATA-ENGINEER
+        - ARCH-IT
+
+    gtm-revenue:
+      mission: Build and operate the revenue stack across demand creation, conversion infrastructure, product-led sales, customer expansion, pricing, compliance, and channels.
+      primary-interaction: lead-to-cash-and-product-led-sales-handoff
+      workflow-use:
+        - GTM strategy
+        - revenue stack design
+        - PLG/PLS/SLG motion selection
+        - product-led sales handoff
+        - pricing and packaging governance
+        - demand generation
+        - sales pipeline execution
+        - customer success expansion and churn prevention
+        - partner and channel expansion
+        - legal and compliance review
+      default-roles:
+        - GTM-GROWTHPM
+        - GTM-PMM
+        - GTM-SALES
+        - GTM-CS
+        - GTM-PRICING
+        - GTM-REVOPS
+        - GTM-LEGAL
+        - GTM-CI
+        - GTM-DEMANDGEN
+        - GTM-PARTNER
+
+  complete-role-coverage:
+    governance-and-orchestration: [EXEC-CEO, OPS-ORCH, EXEC-CTO, EXEC-CPO, EXEC-CFO, EXEC-COO, EXEC-CPTO, EXEC-VPENG]
+    stream-aligned: [PROD-PM, PROD-PO, DES-PROD, DES-INTERNAL, ENG-FE, ENG-BE, ENG-BEGEN, ENG-PRODSERVER, ENG-PRODUCTMINDED, ENG-SW, ENG-FEUX, DATA-ANALYST, OPS-CH, OPS-CREW]
+    enabling: [STR-ANALYST, UX-RESEARCHER, ARCH-BA, ARCH-BIZANALYST, ARCH-EA, QA, SEC-ENGINEER, SEC-APPSEC, SEC-CHAMPION, ENG-PRODCHAPTER]
+    complicated-subsystem: [PROD-TPO, ARCH-SOLUTION, ARCH-SYSANALYST, ARCH-DATA, ARCH-APP, ARCH-TECH, ARCH-SWAT, ENG-DESKTOP, DATA-BIGDATA]
+    platform: [PROD-PPO, DES-PLATFORM, ENG-FEPLAT, ENG-PLATSERVER, INFRA-DEV, INFRA-PLATFORM, INFRA-DEVOPS, SRE, SEC-DEVSECOPS, DATA-ENGINEER, ARCH-IT]
+    gtm-revenue: [GTM-GROWTHPM, GTM-PMM, GTM-SALES, GTM-CS, GTM-PRICING, GTM-REVOPS, GTM-LEGAL, GTM-CI, GTM-DEMANDGEN, GTM-PARTNER]
+
+  executive-balance:
+    principle: C-Level reports must expose tradeoffs instead of merging opinions into a single unsupported recommendation.
+    required-dimensions:
+      CEO: long-term company value, portfolio fit, customer and shareholder value
+      CTO: architecture, reliability, security, scalability, technical debt
+      CPO: customer problem, product value, roadmap, P/L
+      CFO: cost, ROI, capital efficiency, opportunity cost
+      COO: operational feasibility, process, staffing, support burden
+      CPTO: product-technology integration and conflict reduction
+    conflict-record-required-when:
+      - product-speed-vs-technical-stability
+      - revenue-opportunity-vs-operational-cost
+      - customer-value-vs-security-risk
+      - platform-standardization-vs-squad-autonomy
+      - growth-conversion-vs-customer-trust
+      - sales-speed-vs-legal-compliance
+      - pricing-margin-vs-product-adoption
+      - demand-volume-vs-pipeline-quality
+
+  revenue-stack-layers:
+    demand-creation:
+      owner-roles: [GTM-DEMANDGEN, GTM-PMM, GTM-CI]
+      outputs: [ICP-definition, ABM-plan, SEO-AEO-plan, campaign-brief, sales-battlecard]
+    conversion-infrastructure:
+      owner-roles: [GTM-GROWTHPM, GTM-PMM, GTM-REVOPS, PROD-PM, PROD-PO]
+      outputs: [PLS-threshold, onboarding-funnel, PQL-definition, handoff-brief]
+    revenue-intelligence:
+      owner-roles: [GTM-REVOPS, GTM-SALES, GTM-CS, GTM-PRICING, GTM-CI]
+      outputs: [pipeline-forecast, lead-score, churn-score, pricing-model, win-loss-analysis]
+    revenue-risk-governance:
+      owner-roles: [GTM-LEGAL, GTM-PRICING, EXEC-CFO, EXEC-COO]
+      outputs: [MSA-review, pricing-governance, compliance-risk-review, discount-approval-policy]
+
+  enterprise-architecture-layers:
+    business-architecture:
+      owner-roles: [ARCH-BA, ARCH-BIZANALYST, ARCH-EA]
+      outputs: [business-capability-map, value-stream-map, process-model, to-be-architecture]
+    data-architecture:
+      owner-roles: [ARCH-DATA, DATA-ENGINEER, DATA-BIGDATA]
+      outputs: [conceptual-data-model, logical-data-model, physical-data-model, data-pipeline-flow]
+    application-architecture:
+      owner-roles: [ARCH-APP, ARCH-SOLUTION, ENG-BE, ENG-FE]
+      outputs: [service-boundary, api-contract, integration-flow, ui-backend-mapping]
+    technology-architecture:
+      owner-roles: [ARCH-TECH, ARCH-IT, INFRA-PLATFORM, INFRA-DEVOPS, SRE]
+      outputs: [infrastructure-blueprint, cloud-landing-zone, network-topology, disaster-recovery-plan]
+    security-architecture:
+      owner-roles: [SEC-ENGINEER, SEC-APPSEC, SEC-DEVSECOPS, SEC-CHAMPION]
+      outputs: [threat-model, shift-left-check, iam-policy, secure-paved-road]
+
+  routing-rules:
+    - If the task is about a customer-facing domain, start with stream-aligned roles and add platform/enabling roles only when risk or shared capability requires them.
+    - If more than two stream-aligned teams would solve the same infrastructure or tooling problem, route to platform roles before implementation.
+    - If the task introduces deep specialist complexity, route to complicated-subsystem roles and require a simple interface contract for stream-aligned teams.
+    - If the task exposes repeated friction, skill gaps, quality failures, or process waste, route to enabling roles before expanding implementation.
+    - If the task changes production reliability, security, data integrity, or deployment foundations, require platform and auditor roles before release.
+    - If the task affects revenue, GTM motion, pricing, demand generation, product-led sales, customer expansion, or lead-to-cash process, route to gtm-revenue roles.
+    - If product usage data triggers sales handoff, require Growth PM, PMM, RevOps, Sales, and Customer Success consideration before outbound action.
+    - If pricing, contracts, enterprise procurement, or compliance claims are involved, require Pricing Strategist and Legal/Compliance review before customer-facing commitments.