For very simple cases, it may be enough to model the entire value stream inside a single Go Pipeline as the diagram in the documentation suggests.
There is no need to stop at one pipeline per team. If anything, the pipeline group is useful as a team level concept. Modeling your delivery value stream using multiple pipelines allows you to:
- Associate different materials with different pipelines
- Associate different pipelines with different environments.
- Pause or lock a specific pipeline without affecting the other pipelines.