[game_edu] Firing Team Mates

[Sheri Rubin]

Re: Playing Nice With Others - here is a link to view "The Last Lecture" 
by Randy Pausch where he goes over the spreadsheet and ratings of group 
projects with team members (from CMU)  that encourages people to learn 
how to work well in a team: http://www.youtube.com/watch?v=ji5_MqicxSo

Although I think the whole thing is worth a watch, the point in question 
starts at about the 32 min mark for the intro to the course and ETC and 
51 min for the spreadsheet.

 From personal experience when I was in group projects for my degree we 
had team projects and we were 'running a business' and one member never 
showed up or did any work for the first two weeks. I asked the professor 
if we could 'fire' the student and she said "no" because in the real 
world you won't always have coworkers who perform well. I said "in the 
real world if you didn't show up to work for 2 weeks and gave no notice 
you'd be fired." So I would love for schools with team projects to start 
implementing the ability to fire team mates.

Sheri

On 5/4/2012 10:37 AM, Corvus Elrod wrote:

> Isn't a student who "just doesn't play nice with others" wasting 

> everyone's time (including their own). Rather than paying for classes 

> designed to get them a job in the industry, they should be at home 

> watching Unity tutorials on Youtube and spamming the various app 

> stores with endless 8bit clones like the rest of the indies who can't 

> play nice with others.

>

> -Corvus

>

> On Fri, May 4, 2012 at 8:30 AM, Ian Schreiber <ai864 at yahoo.com 

> <mailto:ai864 at yahoo.com>> wrote:

>

>     I've dealt with student teams during a two-quarter capstone, also.

>     Were I to go back in time, I'd make sure the prerequisite for the

>     second course was "instructor permission" (in addition to taking

>     the first course) so that everyone had to pass some kind of review

>     to complete it. I could easily delegate that responsibility to the

>     teams themselves, and only sign off for people taking the course

>     that had their team's OK. That seems like a very easy approach

>     since there's a natural barrier to entry anyway.

>

>     If a student gets fired from a team and can't convince another

>     team to take them on, I can only offer secondhand reports of this

>     happening, but I've heard the options for the student who was

>     fired would be:

>     1. Find another team to take them on;

>     2. Drop the course and retake later;

>     3. Do a solo project, and live or die as a one-person team where

>     they have complete responsibility and control over everything.

>

>     Generally the slackers would take Option 2, and the people who are

>     productive but just don't play nice with others would have Option

>     3 as a fallback.

>

>     - Ian

>

>     ------------------------------------------------------------------------

>     *From:* STEPHEN JACOBS <itprofjacobs at gmail.com

>     <mailto:itprofjacobs at gmail.com>>

>     *To:* game_edu at igda.org <mailto:game_edu at igda.org>

>     *Sent:* Friday, May 4, 2012 10:19 AM

>     *Subject:* Re: [game_edu] Firing Team Mates

>

>     I like Corvus' approach.  I've always set myself up as "executive

>     producer" of all teams in a game and met with the student

>     producer/project manager on a weekly basis who provides me with an

>     update on what milestones everyone is (or isn't) hitting.  If

>     someone's slacking then, depending on what their role is in the

>     team, they could be reassigned or fired.  If they're fired,

>     depending on the situation and the time in the academic quarter, 

>     I might reassign them or just fail them for that part of the course.

>

>     Note that I our intro game design and development classes are two

>     quarter courses where the teams change anyway between first and

>     second quarter as we run multiple sections of game design and

>     development most quarters. Sometimes we've run them as just the

>     natural team changes from quarter to quarter.  Sometimes we've

>     just walked in the third week of the second quarter and reassigned

>     teams except the lead designer and/or producer to different

>     projects, pointing out that when they get out in the industry they

>     won't own the projects they work on, they'll be hired in and/or

>     shuffled as the needs for given projects evolve.

>     _______________________________________________

>     game_edu mailing list

>     game_edu at igda.org <mailto:game_edu at igda.org>

>     http://seven.pairlist.net/mailman/listinfo/game_edu

>

>

>

>     _______________________________________________

>     game_edu mailing list

>     game_edu at igda.org <mailto:game_edu at igda.org>

>     http://seven.pairlist.net/mailman/listinfo/game_edu

>

>

>

>

> -- 

> Another Missive from a Desk at Zakelro!

> Zakelro! <http://zakelro.com>, Bhaloidam <http://bhaloidam.com>, 

> Facebook <http://zakelro.com/facebook>, Google+ 

> <http://zakelro.com/google+>

>

>

>

> _______________________________________________

> game_edu mailing list

> game_edu at igda.org

> http://seven.pairlist.net/mailman/listinfo/game_edu


-- 
*Sheri Rubin*
Founder and CEO

*Design Direct Deliver*
Website: http://www.designdirectdeliver.com
Email: sheri at designdirectdeliver.com <mailto:sheri at designdirectdeliver.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/game_edu/attachments/20120504/e5e730ea/attachment.html>