Chapter 3 talks about designing the environment to help team interactions and has several different example case studies for physical environment design. For virtual environment design, however, there's really only one example: chat. What other virtual environment design strategies have people found success with? (or failed with, I guess)

Chapter 3 talks about designing the environment to help team interactions and has several different example case studies for physical environment design. For virtual environment design, however, there's really only one example: chat. What other virtual environment design strategies have people found success with? (or failed with, I guess)

Somewhat related to lewinski's question above: Chapter 3 talks about long-lived teams, fostering trust within teams, and facilitating interactions for trust, awareness, and learning. Anyone care to share examples of things your teams have done to promote these things? Especially looking for things that involve remote teams.

Somewhat related to lewinski's question above: Chapter 3 talks about long-lived teams, fostering trust within teams, and facilitating interactions for trust, awareness, and learning. Anyone care to share examples of things your teams have done to promote these things? Especially looking for things that involve remote teams.

Chapter 3: I love the idea of measuring cognitive load by looking at relative complexity (employing relative sizing has proven well to “size” pieces of work, a la story points). The geeky part of me wonders if there aren’t some more abstract way of approximating cognitive load by looking at the different roles that interact with a piece of software and the interfaces they do that through (e.g. is it a multiple online forms or a simple GET call to a single endpoint?).

Chapter 3: I love the idea of measuring cognitive load by looking at relative complexity (employing relative sizing has proven well to “size” pieces of work, a la story points). The geeky part of me wonders if there aren’t some more abstract way of approximating cognitive load by looking at the different roles that interact with a piece of software and the interfaces they do that through (e.g. is it a multiple online forms or a simple GET call to a single endpoint?).

I found the nomenclature for service load to be a bit problematic (mainly from my work with complex distributed systems). "Complex" means something entirely different than just "more complicated" - you also see that phase distinction in Team of Teams. I think that changing the terminology to "simple", "compound", and "complicated" would be less likely to be mis-understood...

I found the nomenclature for service load to be a bit problematic (mainly from my work with complex distributed systems). "Complex" means something entirely different than just "more complicated" - you also see that phase distinction in Team of Teams. I think that changing the terminology to "simple", "compound", and "complicated" would be less likely to be mis-understood...

<!here>

<!here>