[samelawrence]

An overview of what a typical software team looks like, and some sort of role rotation so young people get a taste of all the jobs that come together to create software. Obviously CS students should remain focused on the "Dev" angle, but understanding how QA, Product, design, sales, marketing, and management all come together would be helpful for a lot of people. Not all teams have all these roles, but the majority of engineers who work in corporate America will end up working on pretty standardized cross-functional squads for decades to come. It would be nice to have recent grads respond to that environment with something other than a sneer towards the "non-technical" folks.

[Mezzie]

I wonder if this could be done as a collab with another class, because I agree with this: "It would be nice to have recent grads respond to that environment with something other than a sneer towards the "non-technical" folks" and I've also seen something similar from business/creative/sales types that assume the engineers are just 'needlessly pedantic' because they fundamentally don't understand how computers work and that they have limitations.