QUAD™ - Terminology & Jargons
The 1-2-3-4 Hierarchy
QUAD uses mathematical terminology throughout:
┌────────────────────────────────────────────────────────────────────────────────┐
│ QUAD™ - Circle of Functions │
├────────────────────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ 1 │ │ 2 │ │ 3 │ │ 4 │ │
│ │ METHOD │ │ DIMENSIONS │ │ AXIOMS │ │ CIRCLES │ │
│ ├─────────┤ ├─────────────┤ ├─────────────┤ ├─────────────┤ │
│ │ QUAD │ │ Business │ │ 4 Circles │ │ Management │ │
│ │ │ │ Technical │ │ AI Agents │ │ Development │ │
│ │ │ │ │ │ Docs-First │ │ QA │ │
│ │ │ │ │ │ │ │ Infra │ │
│ └─────────┘ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │
│ METHOD: The algorithm/procedure (QUAD = Quick Unified Agentic Development) │
│ DIMENSIONS: Coordinate axes (Business ↔ Technical focus) │
│ AXIOMS: Foundational truths that define QUAD │
│ CIRCLES: Geometric shapes representing functional teams │
│ │
└────────────────────────────────────────────────────────────────────────────────┘
QUAD Glossary
QUAD uses new terms instead of Scrum jargon:
Adoption Levels (Dimensional Geometry)
QUAD adoption follows dimensional progression (0D → 4D):
QUAD Glossary Card
+-------------------------------------------------------------------+
QUAD GLOSSARY
+-------------------------------------------------------------------+
CYCLE 4-week period of continuous work
PULSE Optional weekly sync (5-15 min)
TRAJECTORY Setting priorities for the cycle
CHECKPOINT Monthly demo + release decision
CALIBRATION Monthly reflection + improvement
HORIZON Work backlog (what's ahead)
REFINEMENT Breaking down and clarifying work
CYCLE QUEUE Work selected for current cycle
FLOW RATE Speed of work through pipeline
PROGRESSION Visual of work remaining
COMPLETION Definition of done criteria
IMPEDIMENT Blocker that needs resolution
CIRCLES 4 functional teams (Mgmt, Dev, QA, Infra)
AGENTS AI helpers assigned to each circle
ENABLING Optional support teams (Architect, Security)
ADOPTION LEVELS (0D-4D)
─────────────────────────
ORIGIN 0D - Documentation-first, no agents
VECTOR 1D - AI agents, sequential execution
PLANE 2D - Parallel agent execution
SPACE 3D - End-to-end pipelines
HYPERSPACE 4D - Guardrails + self-improving
+-------------------------------------------------------------------+
The 4 Circles
+------------------+------------------+
CIRCLE 1 CIRCLE 2
MANAGEMENT DEVELOPMENT
B80% / T20% B30% / T70%
+------------------+------------------+
CIRCLE 3 CIRCLE 4
QA INFRA
B30% / T70% B20% / T80%
+------------------+------------------+
B = Business Focus T = Technical Focus
Circle 1: Management (Business 80% / Technical 20%)
Roles: Business Analyst, Project Manager, Tech Lead Key Activities:Circle 2: Development (Business 30% / Technical 70%)
Roles: Full Stack Developer, Backend Developer, UI Developer, Mobile Developer Key Activities:Circle 3: QA (Business 30% / Technical 70%)
Roles: QA Engineer, Automation Engineer, Performance Tester, Security Tester Key Activities:Circle 4: Infrastructure (Business 20% / Technical 80%)
Roles: DevOps Engineer, SRE, Cloud Engineer, DBA Key Activities:Cycle Events
Estimation Methods
QUAD offers multiple estimation methods. Teams choose in settings:
Option 1: Platonic Solids (Default)
Option 2: Dimensions
Option 3: Powers
Option 4: Classic Fibonacci
Enabling Teams
Enabling Teams are optional support groups that are NOT counted as QUAD circles:
Related Documentation
QUAD™ - A methodology by Suman Addanki | First Published: December 2025