Key Principle: Tighten Feedback Loops
Learn how a loose feedback loop affects distributed Agile teams and how to allocate responsibilities across these teams.
We'll cover the following...
ABOUT THIS CHAPTER In more than 20 years of working with companies that have established geographically distributed development teams, we have seen only a small number of examples in which productivity was comparable to a team that was co-located. We have not seen any indication that geographically distributed Agile teams will ever be as effective as co-located teams. However, distributed teams are a fact of life for most large companies today, so this chapter describes how to make them work as well as possible.
One principle of effective software development is to tighten feedback loops as much as possible. Many of the details in this book can be inferred from that principle. Why do we want a Product Owner within the Agile team? To tighten the feedback loops related to requirements. Why do we use cross-functional teams? To tighten the feedback loop needed for decision making. Why do we define and deliver requirements in small batches? To tighten the feedback loop from requirements definition to executable, demonstrable software. Why do we perform test-first development? To tighten the feedback loop between code ...