Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!uvaarpa!vger.nsu.edu!g_harrison
From: g_harrison@vger.nsu.edu (George C. Harrison, Norfolk State University)
Newsgroups: comp.edu
Subject: Re: Group projects
Message-ID: <919.28232ab4@vger.nsu.edu>
Date: 5 May 91 01:42:11 GMT
References: <1991Apr29.212148.15481@rodan.acs.syr.edu> <12806@uhccux.uhcc.Hawaii.Edu>
Distribution: na
Lines: 77

In article <12806@uhccux.uhcc.Hawaii.Edu>, jlong@uhunix1.uhcc.Hawaii.Edu (John Long) writes:
> In article <1991Apr29.212148.15481@rodan.acs.syr.edu> anand@top.cis.syr.edu (Rangachari Anand) writes:
> 
>>................deleted
>>While it is true that the intent of group projects is to prepare
>>students for the real world, the students are, it would seem, expected
>>to pick up the techniques of group interaction on their own. 
> 
> Ouch! You hit a nerve... Last semester I took a course in system analysis
> which consisted of some lectures on theory and one group project for the
> class of 7 students. I do not feel that it prepared me *at all* for the 
> so called real world. 
> 
> The instructor would give new job assignments or titles to the various members
> of the group every few weeks, but basically we were each doing our own thing,
> because we had no real leadership. As a result, I jumped ship when I couldn't
> convince the group that we were headed for trouble by ignoring a certian 
> aspect of the problem. I do that in the real world, too!

Did you EVER speak to the instructor about this??

> I recommend that if you give a group project, you should be an active member
> of the group, or possibly incorporate another more advanced class into the
> group, so that there is some sort of leadership recognized by the members.
> In other words, *teach* group activity, don't just assign it.

The instructor MUST act as the project manager.  A team of totally
unexperienced students will almost certainly fail to meet the minimum
requirements for ht project.

> In the real world, there is corruption, incompetence, and all sorts of b.s.
> I don't see the value of a course which gives hands-on experience with it.
> But, then again, maybe it would be... 

It is of real value if taught correctly.  I have taught several courses over
the past five years with large group projects (with requirements
specifications, designs, source code, users' manual, testing documents,
configuration management, quality control, etc....) to undergraduates.  I have
received several post-graduate responses that the course was extremely
valuable.

Here are some "Fundamental Truths of Teaching Software Engineering" that I use:
1:  Have the students keep a LOG of EVERYTHING they do in the course.
2:  Never lecture more than two hours a week (like a 3-credit 2/lecture - 2/lab
    course).
3:  Require the student team to hand in a final report RANKING their each 
    individual's effort relative to the rest of the team.  Have them all
    sign it.
4:  Encourage the students to report IMMEDIATELY any problems they are
    having.
5:  loop  PUT_LINE("Stick to a Schedule"); end loop;
6:  The instructor must assume the role of project manager.  S/he must also
    be available at STRANGE times to answer question (weekends, nights, etc.)
    via mail, etc.
7:  The instructor needs to read, read, and read several software engineering
    books.  (I've found that it really doesn't matter if the students have 
    a book or not.)
8:  Lecture for at least a week (perhaps two) on team organization, group 
    psychology (perhaps some of the most important computer science 
    lectures you'll ever give).
9:  Don't require the students to program in a nonfamilar language.
10: Remember that the students have other courses.  Don't require them to
    develop software you can't do in a 40-hour week.
11: Use COCOMO or some other appropriate cost metric for a "reality check."
12: Toss out all old notes.  They are a crutch.  Trust your experiences and
    recent readings.

The above lessons were learned from past errors and not from any native 
feelings.

George...

-- George C. Harrison                              -----------------------
----- Professor of Computer Science                -----------------------
----- Norfolk State University                     -----------------------
----- 2401 Corprew Avenue, Norfolk, Virginia 23504 -----------------------
----- INTERNET:  g_harrison@vger.nsu.edu ---------------------------------