A stream-aligned team owns an independent flow of value, from discovering unmet user needs in a business subdomain through building, deploying, and running the product capability. It combines business and IT responsibilities rather than acting as an IT function separated from the business. section 11.2.1 section 6.1.1
An effective stream-aligned team typically has:
- A loosely coupled business subdomain or product area to align with. section 6.1.1
- Purposeful business outcomes that guide its decisions. section 6.1.1
- The skills needed across the stream, such as product management, testing, and user experience. section 11.2.1
- Authority to change and deploy decoupled software with minimal dependencies on teams outside it. section 6.1.1
Typical team boundaries
Examples include a team responsible for domain APIs, a team building embedded hardware software, a mobile or web team, and a full-stack team owning the backend API and user interface for an end-to-end search feature. section 11.2.1 section 6.1.1
Use the model of the four key characteristics of an independent value stream to assess alignment, outcomes, autonomy, and architectural decoupling. section 6.1.1

