sprint

To run parallel pipelines across multiple feature requests, you can orchestrate concurrent /proceed sessions using a sprint dashboard that isolates each REQ in its own worktree and enforces concurrency limits for coordinated progress.

Parallel ADLC orchestration is the process of running multiple /proceed pipelines concurrently across approved REQs. You need it when managing many feature requests and requiring a scalable sprint dashboard to reduce wait times and monitor progress.

You coordinate worktrees and merges by isolating each pipeline in a per-REQ worktree, monitoring pipeline-state.json, and enforcing pre-flight checks and merge sequencing to support both batch and per-REQ merges.

Yes, you can track blockers, status, and progress across parallel pipelines using a unified sprint dashboard that monitors pipeline-state.json for each worktree and coordinates merge readiness across all active REQs.

Concurrency limits for parallel pipeline orchestration are enforced by the sprint coordinator, which monitors pipeline-state.json across per-REQ worktrees and applies pre-flight checks before launching new /proceed sessions.

The best way to merge parallel pipelines without conflicts is to use coordinated merge sequencing, which enforces pre-flight checks and supports both batch and per-REQ merges across isolated worktrees to ensure merge readiness.