From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f43e6,d71a6822cd2fec5 X-Google-Attributes: gidf43e6,public X-Google-Thread: 103376,5ea968aeb8c7f10d X-Google-Attributes: gid103376,public From: malak@access1.digex.net (Michael Malak) Subject: Re: Do I Really Need A Supervisor? Date: 1997/03/27 Message-ID: <5heai3$lsh@access1.digex.net>#1/1 X-Deja-AN: 228779164 References: <5g7u24$1jeg@uni.library.ucla.edu> <5h8i3q$ni5$2@trsvr.tr.unisys.com> Organization: Express Access Online Communications, Greenbelt, MD USA Newsgroups: comp.software-eng,comp.lang.ada Date: 1997-03-27T00:00:00+00:00 List-Id: In article , Robert Dewar wrote: >iDarriel says > >Well terminology can get in the way of this discussion, but to me the >technical lead *is* a manager, because they need to make management >decisions. Someone has to make technical decisions on overall design >and style. Sure these decisions can be reached by a consensus process, >but that is always part of a good management style, but someone does >ultimately have to make the decisions! There is overlap between the roles of the project manager and the technical lead. For a complete discussion, see Steve McConnell's _Rapid Development: Taming Wild Software Schedules_ (Microsoft Press, (c) 1996, ISBN 1-55615-900-5), p.314. The technical lead makes the technical and design decisions as you said. But the project manager has different responsibilities: communicating with upper management, allocating physical resources. Depending on the situation, there are responsibilites which are shared by the two roles, such as generating and enforcing schedules. -- Michael Malak Magic forwarding e-mail address: Washington, DC malak@acm.org