Waves / The Team

The Team

In Waves, every role has an AI partner and every meeting has a clear purpose. No fixed ceremonies, no calendar-driven rituals.

Every Role Has an AI Partner

In Waves, AI agents are not tools — they are team members with defined responsibilities within each role.

👤

Product Owner

Owns the product blueprint. Validates wave outputs. Gives go/no-go at gates. AI agents assist with market analysis, feasibility simulations, competitive research, and data-driven decision support.

Authority: Final decision on what gets built
📋

Coordinator

Convenes meetings, tracks roadmap progress, identifies blockers, and ensures wave flow. AI agents assist with progress reporting, dependency detection, and meeting preparation.

Authority: Wave cadence and team synchronization
💻

Technical Manager

Translates business requirements into technical reality. Manages AI agent output quality. AI agents implement features, write code, analyze architecture, audit quality, and execute objectives from logbooks.

Authority: Implementation, architecture, and quality

All On-Demand. Zero Fixed Ceremonies.

Every meeting in Waves has a clear purpose, defined inputs, defined outputs, and a responsible convener. No calendar-driven rituals.

Coordination Meeting CM

Frequent and lightweight. Plan, track progress, resolve doubts and blockers. Convened by the Coordinator as often as needed. Every CM has a stated objective before it begins.

Blueprint Refinement BR

Change control for the product. Evaluates and approves changes to the product blueprint. Infrequent but high-impact. Requires PO approval. Every change is recorded with reasons in the decision trail.

QA & Demo QA

The wave gate. Validates completed work and gets PO approval for production. Test plan defined before the meeting, not improvised. If rejected, observations become logbook entries for the next iteration.

Health Check HC

Team wellbeing assessment adapted from the Spotify Squad Health Check model. 8 dimensions: product quality, participation, work-life balance, learning, clarity, tooling, team support, and delivery confidence.

Wave Celebration WC

Positive closure at the end of each wave. Recognize achievements, document improvements constructively, and confirm production launch. Not a retrospective — the tone is celebratory, not forensic.