This article from Rob Maher focuses on how to increase productivity. It discusses how changing a project staffing model could increase the productivity of project teams (PDF document). There is published evidence that short-lived groups of people brought together for a project are correlated with lower productivity. His view is that in an agile world, teams are permanent and the organization optimizes at the team level. Permanent teams enable consistent estimation, which is not possible using the matrix approach.
Scrum teams usually develop iteratively new product features. In larger project, teams can also be organized around layers or components of the product. In this article, Mukesh Chaudhary discusses how to manage the complexity with Scrum component teams and integration of their deliverables to make up a feature.
In his article “Creating an ATDD Ready Sprint Backlog in Scrum“, Ralph Jocham discusses the requirements definition in Scrum and how examples allows the team to better understand them. As the backlog is now also expressed in terms of business requirements, each team member can easily focus on the bigger picture during the Scrum stand-up meeting and align with the ‘why’. If you translate the business-facing examples into automated tests, it enables the team to verify during the Sprint that the software increment always meets the evolving requirements towards the Definition of Done and the overall goal.