[quoting Morrison, 30 Sep 96] The major flaw was the split role of the instructional designer between doing design and project management (budgets in 1975 ranged from $150,000 to $500,000 for a project). Often, the decision was to either finish the task on time or to design the instruction properly to avert later problems...
If you did it again, what would you change? Separate the role of the designer and project manager. Give the designer all the authority, but no responsibility!
Yes, I know of one particular large project where the programmer assumed responsibility for project management. His programming inclinations overcame his project management responsibilities and he overruled important instructional design issues for the sake of easier programming. A side effect was lack of respect and trust by the instructional design and content sides of the team.
However, in smaller projects with teams of three or four, it is effective and appropriate for people to take several roles, as long as effective channels of communication are set up.
[quoting Cornell, 30 Sep 96] They [the students] were intimately involved helping me to develop the course materials and so, saw the extreme frustration I faced in trying to match my style with that of a colleague (whose idea of preplanning was to get together the week prior and decide what was to be covered).
Yes. To be involved in any educational technology project requires a large amount of logistical skill. Project management, in other words. About 10% of any development effort needs to be sent in project management. The larger the project, the higher the percentage. If you think a project will just manage itself, you are wrong. Lack of attention to management has been mentioned in a number of posts.
[quoting Morrison, 1 Oct 96] I have experienced both situations where everyone was involved in the design as well as when only limited individuals were involved. The 1970's scenario involved everyone which tended to slow down the process (when time was critical) and cause some problems within the team. Agreed, ideas from different perspectives can enhance a project, different perspectives (based on my experience at the University of Mid-America and having worked for three Fortune 500 companies) by large team design efforts. I have also seen some very creative ideas come from inclusive team efforts.
Clark Quinn's comment below confirms my contentions that all team members should be involved. However, I take your point about large teams, as well. Perhaps there is a distinction between large projects and small projects?
[quoting Quinn, 1 Oct 96] Reflections on another project indicate problems from handing off to some others to change graphics who were not involved in the design, and they made other changes inconsistent with the overall design goals.
[quoting Morrison, 1 Oct 96] The major lesson I have learned about chemist is that they have all agreed to disagree and to never agree.
Watch it Gary! I can't agree with you on this. I used to be a chemist too!