Re: [epf-dev] Proposed name change for Project Management elements

[Per Kroll <pkroll@xxxxxxxxxx>]

Hi,

I think Bruce makes a good argument.
If we say that OpenUP should be usable for an independent project, which
I think we do, it makes sense to call it Project Manager and Project Plan.
I could see calling Project Manager instead Project Lead, to make a point
that this more of a leader than a command & control manager, but that
may add some confusion, since most of the world is calling this Project
Manager. Maye the solution is to stick with Project Manager, and call out
in the description that a good Project Manager needs to be a leader that
shows the direction and help build momentum, not just a manager that shuffles
starus reports back and forth.
On a larger project, the Project Manager
role will have more specialized role such as 'Component Lead" or "Development
Lead", and the Project Manager will be increasingly focusing on just
the schedule, finance, resource mgmt issues, and less on leading day-to-day
development.
So, I hence has changed my mind since
the Reading meeting... and would like to go with Project Manager and Project
Plan.

On Development Backlog, I think I am
fine with that term.
Product Backlog (which is the Scrum
term) is not a good name for people people regular IT applications. They
do not think about what they are building as a Product....
Projetc Backlog would be misguided,
because many of the things in their are not, and will never be, intended
for the current project. So, I think Development Backlog is a good neutral
name....

Cheers

Per Kroll
STSM, Manager Methods: RUP / RMC
Project Lead: Eclipse Process Framework
Rational Software, IBM Corp
408-342-3815

Bruce Macisaac/Cupertino/IBM@IBMUS
Sent by: epf-dev-bounces@xxxxxxxxxxx

06/28/2006 11:51 AM

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

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
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev