[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epf-dev] Proposed name change for Project Management elements
|
Hi Don
re: Lead/Leader - I don't mind. "Leader" is grammatically correct, I guess.
On the point of Development Lead(er) vs Technical Leader;
On the surface, there isn't a distinction between the two in my mind - both
could represent "the person in charge of the development team." I guess
it's worth clarifying that it is an administrative role. The tasks &
products remain the same as the current OpenUP/Basic PM, so I don't see
this role as defining a "Lead Developer" for example. Of course, if the
circumstances are right we could feasibly see the role being played in
combination with other roles by a single person in the team.
There is a finer point that would tempt me towards "Development Leader"
however. Which is that the development team could contain both technical
and non-technical members (such as business representatives), so adopting
the label "Technical Leader" wouldn't really get that point across for me.
The main thrust of the point is that defining a "Project Manager" role in
OpenUP/Basic seems misleading, as the scope of the method and the intended
audience doesn't really address the territory that I would typically
associate with PM's. Maybe we should be defining a lighter role and then
scale up to project management?
regards
Mark
Mark Dickson
Principal Solution Architect
SAE Practice
m 0780 1917480
w www.xansa.com
e mark.dickson@xxxxxxxxx
Donald Firesmith
<dgf@xxxxxxxxxxx>
Sent by: To
epf-dev-bounces@e Eclipse Process Framework Project
clipse.org Developers List
<epf-dev@xxxxxxxxxxx>
cc
25 June 2006
15:30 AST Subject
Re: [epf-dev] Proposed name change
for Project Management elements
Please respond to
Eclipse Process
Framework Project
Developers List
<epf-dev@eclipse.
org>
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
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
