Pod Structure & Roles

The Velocity Pod is our unit of delivery. Unlike traditional scrum teams that might have 5-7 developers, a Velocity Pod is smaller, leaner, and heavily leveraged by AI.

The Composition

A standard Velocity Pod consists of:

The AI-Augmented Engineer (Full-Time)

• Role: The core builder.
• Responsibility: Delivering features, writing code, and managing the technical implementation.
• Leverage: Uses the Velocity Framework to do the work of 1.5 - 2 traditional seniors.

The AI Productivity Lead (Fractional)

• Role: The "Force Multiplier."
• Responsibility:
  • Maintaining the .cursorrules and project configuration.
  • Researching new AI tools and updates (e.g., "Cursor just released a new feature, let's use it").
  • Unblocking the Engineer on complex prompt engineering tasks.
• Allocation: Typically 10-20% time per pod.

The Technical Delivery / BA (Fractional)

• Role: The Bridge.
• Responsibility: Translating business requirements into the "Refined Requirements" (Step 1 of the Workflow).
• Allocation: Typically 20% time per pod.

Why This Structure Works

In traditional teams, seniors waste time on setup, juniors break things, and PMs write vague tickets. In a Velocity Pod:

• The Delivery Lead ensures the input is clean (Garbage In, Garbage Out prevention).
• The Productivity Lead ensures the "factory" (the IDE/AI stack) is optimized.
• The Engineer focuses purely on high-speed execution.