Standups work really well when there are dependencies between different functional groups. Consider a team working on a live browser/Facebook-based free to pla

Standups work really well when there are dependencies between different functional groups. Consider a team working on a live browser/Facebook-based free to play game (social game as a service). There are many releases a week. - Engineering typically requires art assets to begin/complete work. Ie. building models, unit models, 2D unit images, item images, etc. - Releases don't end when they are pushed up to prod -- most releases have some kind of "go to market" plan that must be executed. For example, if a new Dragon Armor is released, we need to message all players to inform them of the new functionality and educate them on how it works, there would typically be a simultaneous tournament or contest that awards the new Armor as a prize, and possibly some other sale or promotion on a related item. - It's a time for product to provide updates on where different specs are and on key game metrics. - Customer Support/Community Management also provide updates on any emerging issues in the game, which improves everyone's situational awareness.