[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[epf-dev] Renaming "Project Plan"
|
Nate
I have submitted a bug explaining my reasons (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=178365) ... I understand
your comment if our "target" is RUP practitioners ... but is it? I think
that "regular PMBOK" project managers or the agile community would
understand better a "project brief" concept than a "Project Plan" that
is not a "complete plan" ... like this we would have a GO (a project
brief) and Iteration plans
Please post your comments on this bug ... I would appreciate your feedback
Thanks
Ana
Nate Oster wrote:
Ana raises an interesting point about the OpenUP "Project Plan" and
changing its name to be more informal, much like we did with the
Architecture Notebook.
However, it seems like "Project Plan" is a pretty well understood
artifact within iterative development. It also creates as much
one-to-one alignment of artifact names as possible with RUP, so it's
easier for RUP practitioners to make the transition.
I don't think I favor changing the name unless we're also significantly
altering its scope or purpose.
Thanks,
Nate
-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ana Valente Pereira
Sent: Tuesday, March 06, 2007 11:51 AM
To: Eclipse Process Framework Project Developers List; Per Kroll
Subject: [epf-dev] PM & Deployment Plan
Per ... I have taken a look at all the bugs in PM package and meeting
minutes from November and December to get a sense of what is left to to
...I have distributed all the existing bugs for the next 3 milestones...
with higher priority for tasks and work products... I have made the same
for deployment bugs
I can't change the bug target milestone to 1.0 M6 (because i am not a
committer?) so I have put a link for every bug in composer to produce
this plan ... the plan will be published and updated on
*http:www.whatever.pt/epf *
I also would like to propose some changes to project management ... for
instance, replace project plan for project charter (or project notebook
... to follow the architecture discussion) ... what is the usual
procedure? ... raise a new bug and discuss changes in bugzilla?
thanks
Ana
Per Kroll wrote:
Hi,
attached you find yesterdays iteration assessment for the content
side.
Note that we need to close out E2 defects, which will be reviewed by
next Wednesday. I would like to see all bugs closed or deferred by
then....Please make sure to close out (Brian, Ricardo and Jim will
help with reviews) or move to M6 (=C1).
All package owners was asked to produce a plan for the remainder of
the project for their area, so we have a better idea on how we are
doing. We need that plan before next Wed so we can produce a realistic
iteration plan and update project plan in next wed package owner
call...
-----------------------------------------------------------------------
-
_______________________________________________
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
