Serendipitous Communications in Geographically Distributed Agile Teams

One of the experiences people miss in distributed teams compared to collocated teams is the ability to serendipitously bump into other team members or just other people. They like the idea of having random encounters to share what they did for the weekend or, more importantly, discuss problems they are struggling with at work. Sometimes …

Distributed Teams Need Sufficient Communications Technology

In our previous article, we discussed the importance of sufficient hours of overlap in managing a team’s workspace. As a reminder, here are the four components we see that need to be managed in a distributed team workspace. Sufficient hours of overlap in everyone’s workday. Sufficient communications technology that supports everyone equally in synchronous and …

Product Roles, Part 6: Shorten Feedback Loops

I started this series discussing the issue of the various product-based roles in an agile organization. I suggested a product value team because one person becomes a bottleneck. One person is unlikely to shepherd the strategy and the tactics for a product. And, batching the product planning in one-quarter chunks doesn’t encourage us to reduce …

Product Roles, Part 4: Product Orientation and the Role of Projects

Many people in the agile community promote a product orientation over a project orientation. That’s possible because an organization has product or feature teams. That works until you have more products than teams. That’s when you might still need projects to accomplish everything. If you keep teams together, you can still use projects in a …