Are cross-functional teams in Scrum allowed to work on only one technical layer of a system?

In Scrum, cross-functional teams are designed to encompass all the necessary skills and competencies required to complete the work within a given Sprint. These teams are not limited to a single technical layer; rather, they are expected to work collaboratively across various layers and aspects of the system. The concept of cross-functionality emphasizes that team members should possess a range of skills, enabling them to support one another in delivering a potentially releasable increment of the product at the end of each Sprint.

By working across multiple technical layers, Scrum teams can enhance flexibility, innovation, and problem-solving capabilities. This allows them to respond effectively to changing requirements and fosters a more holistic approach to product development, incorporating perspectives from different areas of expertise. In this context, restricting a team to only one technical layer would undermine the principles of collaboration and the potential for delivering a well-rounded product.

Acknowledging the importance of cross-functionality aligns with Scrum values and practices, where the emphasis is placed on collaboration, continuous improvement, and delivering value to the customer.