Salman—you're probably already aware of this—a major argument for small cross-functional teams (e.g. agile teams) is based on the fact that roles on the team tend to blend depending on how much work each member has to do. For example, when there isn't much copy to write at some point in a sprint the copywriter is asked to help QA something, or provide input on visual design. The result is more engaged teams (because we like doing things outside of our primary domain) and more innovative teams (because individuals outside of a domain often come with fresh, unencumbered, ideas). .... In other places, this is stated as the development of "T" shaped team members who have a broad range of shallow experience but go deep in a domain or two. That's one kind of polymath.
Salman—you're probably already aware of this—a major argument for small cross-functional teams (e.g. agile teams) is based on the fact that roles on the team tend to blend depending on how much work each member has to do. For example, when there isn't much copy to write at some point in a sprint the copywriter is asked to help QA something, or provide input on visual design. The result is more engaged teams (because we like doing things outside of our primary domain) and more innovative teams (because individuals outside of a domain often come with fresh, unencumbered, ideas). .... In other places, this is stated as the development of "T" shaped team members who have a broad range of shallow experience but go deep in a domain or two. That's one kind of polymath.