Hi Folks,
I agree with Bruce.
In my mind, the team lead role does not capture all of the
responsibilities of the project manager.
Even small, stand-alone projects require a project
manager with the full suite of responsibilities defined in OpenUP/Basic for
that role. If the project is large, we may add additional management roles
(team leads) to maintain a reasonable span of control.
The term project
manager is well known and I believe we should stick with it in the base
OpenUP/Basic. If we rename this role I think we will be
continually explaining "The Team Lead role is commonly called
the Project Manager role" in order to clarify the intent of the role, and I
don't see a lot of value added.
The argument for the name change was based on the premiss
that projects that execute OpenUP/Basic will do so within the context of a
larger project. I guess it boils down to our intent for
OpenUP/Basic. Do we really want to impose the constraint that OpenUP/Basic
can only be used within the context of a larger project (in which case
I assume the project manager would be someone playing the OpenUp/Basic role
of Stakeholder)?
My $0.02.
Cheers,
Chris
What we name the role should be
based on the scope of responsibility. A subproject of a large project probably needs a development lead who
only performs a subset of management responsibilites. Some things that may not be done by the development lead
are: - scope management - decisions on processes - decisions on staffing -
etc. The development lead's main
responsibilities are planning and reporting status. This is different from a small project that is
standalone. In this case, the "manager"
has the same scope of responsibilities of a large project manager.
I believe a good solution is to preserve
the current name of project manager for the small project, but as part of
scaling up OpenUP to deal with subprojects, we add this specialized role
Development Lead or perhaps Subproject Lead or Component Lead.
Bruce MacIsaac
Manager - RUP/OpenUP
Content
bmacisaa@xxxxxxxxxx
phone: (408)863-8718
Donald Firesmith
<dgf@xxxxxxxxxxx>
Sent
by: epf-dev-bounces@xxxxxxxxxxx
06/25/2006 12:30 PM
|
Please respond
to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
|
To
| Eclipse Process Framework Project
Developers List <epf-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [epf-dev] Proposed name change
for Project Management elements |
|
There are other reasons for the name change. Projects can be rolled
together into Programs of related projects (e.g., product lines). You
may not want to be too restrictive.
On the other hand, development lead
may be confused with technical
leader, when you seem to be more oriented for
an administrative
manager. Also, why lead rather than leader?
Don
Firesmith
Mark.Dickson@xxxxxxxxx wrote:
> Hi all
>
>
Following on from the discussions at the Reading F2F, I would like to
>
suggest that we change the names of the PM elements to reflect the small
>
team nature of OpenUP/Basic.
>
> OpenUP/Basic Name Proposed
Change
> ====================================
> Project Manager
Development Lead
> Project Plan
Development Plan
>
> The premise is that the scope of Open/UP
basic small, so really represents
> the development effort inside a larger
project management framework. This
> suggests that our PM role isn't
really a Big-Boss Project Manager but more
> of a development team leader.
Similarly, the OpenUP/Basic Project Plan is
> also going to be pretty
narrowly scoped, so is possibly more of a
> Development Plan
(covering the software development effort) rather than a
> full-blow
project plan.
>
> This approach leaves the door open to creating a
Project Management plug-in
> for OpenUP in the future whilst reflecting
the lightweight nature and
> development focus of OpenUP/Basic for the
initial release.
>
> cheers
>
>
Mark
>
>
> Mark Dickson
> Principal Solution
Architect
> SAE Practice
> m 0780 1917480
> w
www.xansa.com
> e mark.dickson@xxxxxxxxx
>
>
> Whilst
this email has been checked for all known viruses, recipients should undertake
their own virus checking as Xansa will not accept any liability
whatsoever.
>
> This email and any files transmitted with it are
confidential and protected by client privilege. It is solely for the use
of the intended recipient.
> Please delete it and notify the sender if you
have received it in
> error. Unauthorised use is
prohibited.
>
> Any opinions expressed in this email are those of
the individual and not
> necessarily the organisation.
>
Xansa, Registered Office: 420 Thames Valley Park Drive,
>
Thames Valley Park, Reading, RG6 1PU, UK.
>
Registered in England No.1000954.
> t
+44 (0)8702 416181
> w
www.xansa.com
>
_______________________________________________
> epf-dev mailing
list
> epf-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/epf-dev
>
_______________________________________________
epf-dev mailing
list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
--------------------------------------------------------------------------------
Telelogic Lifecycle Solutions:
Helping You Define, Design & Deliver Advanced Systems & Software
Learn More at www.telelogic.com
Chris Sibbald
Vice President, Standards and Technology
Telelogic North America Inc.
255 Albert Street, Suite 600
Ottawa
Ontario
K1P 6A9
Canada
Phone: +1 (613) 266 5061
Fax: +1 (613) 482 4538
Mobile phone: +1 (613) 266 5061
Chris.Sibbald@xxxxxxxxxxxxx
http://www.telelogic.com
Telelogic - Requirements-Driven Innovation!
-------------------------------------------------------------
The information contained in this e-mail, including any attachment or enclosure, is intended only for the person or entity to which it is addressed and may contain confidential material. Any unauthorized use, review, retransmissions, dissemination, copying or other use of this information by persons or entities other than the intended recipient is prohibited.
