Domain Knowledge
The contextual outer ring: industry specialization, technical architectures, product discovery, and commercial realities. Enables the coach to formulate sharp, impactful questions that matter to the business.
Three Pillars of Domain Knowledge
What Constitutes Domain Knowledge in Agile Coaching?
Business & Market Domains
Deep grasp of industry specificities (FinTech, MedTech, e-Commerce, Automotive), regulatory compliance (GDPR, DORA, SOX, HIPAA), monetization mechanics, and market pressure.
- • Business models and P&L drivers
- • Regulatory compliance & governance
- • Market dynamics & customer behavior
Architecture & Engineering
Fundamental understanding of modern technology stacks, architectural paradigms (monolith vs microservices, event-driven), CI/CD automation, technical debt, and SDLC maturity.
- • Modern engineering practices (XP, DevOps)
- • Production resilience & telemetry
- • Technical debt payoff strategies
Product Discovery & Strategy
Mastery of user research methods, rapid prototyping, Lean Startup experimentation, behavioral product analytics, and hypothesis validation prior to costly engineering.
- • Customer Journey Mapping (CJM)
- • Product health metrics (NPS, Churn, ARR, CAC)
- • Value-driven outcome backlog management
Assessment & Diagnostic Focus
Evaluating a Coach's Domain Acumen
1. Does the coach speak the ubiquitous domain language?
When collaborating with Product Owners and tech leads, does the coach use substantive domain terminology, or merely generic Agile jargon?
2. Do recommendations respect compliance and architectural realities?
Does the coach recognize why certain practices (e.g., continuous deployment to production) require specific compliance gates or audits in regulated environments?
3. How fast does the coach internalize market dynamics?
Does the coach actively engage with end-users, attend product demo feedback sessions, and study company financial metrics?