---
# System prepended metadata

title: Untitled

---

```mermaid
sequenceDiagram
loop Cross-functional requirement grooming, ~3 sprint horizon
Note over Product,Full Team: Regular initiative-level grooming series
Product->>Full Team: Requirements readout to Design, Client, Service, QE
Full Team-->>Product: Functional notes
Full Team-->>Product: Test case & Precondition definition
Full Team-->>Product: Test data definition
Full Team-->>Product: Dependency graph
Full Team-->>Product: T-shirt sizing
Note over Product,Full Team: Team accepts definition
end
```

```mermaid
sequenceDiagram
loop Cross-functional requirement grooming, ~3 sprint horizon
Note over Product,Full Team: Regular initiative-level grooming series
Product->>Full Team: Requirements readout to Design, Client, Service, QE
Full Team-->>Product: Functional notes
Full Team-->>Product: Test case & Precondition definition
Full Team-->>Product: Dependency work identified
Full Team-->>Product: T-shirt sizing
Note over Product,Full Team: Team accepts definition
end

Product->>Service: Business requirements 


Note over Service: Identify upstream capabilties and roadmap dependencies (this should)

loop Contract Agreements
Service->>Client: Present schema designs
Client-->>Service: Request changes
Client-->>Service: Test case scope lock
end

Client->>Service: Accept
Note over Service,Client: Functional Change Sprint Completes...

Service->>Client: Functional Demo w/Postman
Client-->>Service: Feedback / Accept
Service-->>Product: Client team unblocked
Note over Service,Client: QE Completes...

Service->>Client: Present QE PR for approval 
Client-->>Service: Feedback / Accept
Service-->>Product: Service change done
```

- "Full Team" includes client(s), GQL, rest service and design leads as part of regular grooming
- Client teams delegate an approver to participate in bringing forward new Services
- Service teams present service designs and QE to delegates
- Delegates are responsible for: 
-- Representing client requirements for each service and ensure schema accounts for their needs
-- Providing their QE acceptance 

Target state:

```mermaid
sequenceDiagram
loop Cross-functional requirement grooming, ~3 sprint horizon
Note over Product,Full Team: Regular initiative-level grooming series
Product->>Full Team: Requirements readout to Design, Client, Service, QE
Full Team-->>Product: Functional notes
Full Team-->>Product: Test case & Precondition definition
Full Team-->>Product: Dependency work identified
Full Team-->>Product: T-shirt sizing
Note over Product,Full Team: Team accepts definition
end

Product->>Service: MVP1 business requirement 

Note over Service: Research Source System Schema

loop
Service->>Client: Present schema design
Client-->>Service: Request changes
end

Client->>Service: Accept
Note over Service,Client: Functional Change Sprint Completes...

Service->>Client: Present QE PR for approval 
Client-->>Service: Feedback / Accept
Service-->>Product: Service change done
```