tl;dr:How you split your software organization into teams can make or break developer experience and productivity. Your organization structure should allow each team to make decisions about a clearly defined product area. After reading this blog post, you’ll know how to balance the four defining factors of a team: outcomes, features, people, and architecture.
tl;dr:Our new book, Build: Elements of an Effective Software Organization, is a blueprint for continuous improvement. It zeroes in on three key ingredients: a relentless focus on business outcomes, actionable insights to boost the productivity of your software teams, and a thoughtful approach to improving the experience of building software at your company. Read it online for free.