Issue 57631 - Prototype Requirement: Following the steps in the Project Management Book of Knowledge (PMBOK)
Summary: Prototype Requirement: Following the steps in the Project Management Book of ...
Status: CLOSED WONT_FIX
Alias: None
Product: oopm
Classification: Unclassified
Component: www (show other issues)
Version: current
Hardware: All All
: P3 Trivial
Target Milestone: AOO PleaseHelp
Assignee: ooo
QA Contact: issues@oopm
URL: http://oopm.openoffice.org/initial_an...
Keywords:
Depends on:
Blocks: 57601
  Show dependency tree
 
Reported: 2005-11-10 08:32 UTC by ooo
Modified: 2010-06-27 15:10 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description ooo 2005-11-10 08:32:28 UTC
This task is a part of issue 57601 "Requirements specification for project   
management tool prototype":   
   
http://www.openoffice.org/issues/show_bug.cgi?id=57601
Comment 1 officista 2006-01-15 18:12:47 UTC
Clear sepertion between a task's duration (how much time will the task take) 
and the effort for a resource. E.g. the shipment of a parcel takes 5 days but 
my effort for tracking etc is just 2 hours. This function is not provided to 
many project management tools.
Comment 2 kwest 2006-07-22 00:36:35 UTC
PMBOK is not a methodology, so one can't "follow the steps" as such. Perhaps it
would be better to specify at any point in time which aspects of the PMBOK the
current OOPM implements - or use the PMBOK as a roadmap for explaining the
development of the OOPM to project managers.
Comment 3 j6502 2006-07-29 02:45:29 UTC
This request simply doesn't make sense as kwest pointed out.  However, I would
strongly advise against put anything in the product that tightly couples it to
PMBOK.  The PMBOK will change and you don't want PMI causing your product to be
out of date.  Also, realize that PMBOK is *not* the be-all and end-all of
project management.  There are real methodologies and other approaches that will
come into favor.  Perhaps you could take some vocabulary from PMBOK, and maybe
use its concepts in the help or documentation (?) for the product.  But that's
as far as it should go.
Comment 4 gilh 2006-08-01 23:47:24 UTC
Should we then close this requirement?
Comment 5 j6502 2006-08-02 12:53:33 UTC
Close it.
Comment 6 pwheel 2006-10-13 04:12:56 UTC
Maybe a PMBOK 'template' option (plus a PRINCE2 one and any others that can be 
added for that matter). Tying the app to any one approach or methodology would 
be counter-productive, but out-of-the-box support for established methods would 
be a good thing.
Comment 7 chekristo 2007-10-23 06:27:47 UTC
I agree with pwheel, bulding the tool around PMBOK would not be sensible. 
Perhaps some sort of method plugin option should be avilable upon project 
creation (PMBOK, Prince2, ITIL) which will shape how the project is defined 
within the application.
Comment 8 ooo 2009-02-17 15:10:22 UTC
I will create some derived whishes/criterias and close this one.

- Support for different project methods which can be selected when creating a
project (examples: PMBOK, Prince2, ITIL ...)
- Separate task duration and ressource effort
Comment 9 ooo 2009-02-17 17:49:52 UTC
"Support for different project management methods" is now issue 99317 and

"Separate task duration and ressource effort" is now issue 99321.

Closing this task as WONTFIX because it can't be done - see comments above.
Comment 10 Mechtilde 2009-07-12 19:03:43 UTC
wontfix -> closed
Comment 11 wgutches 2010-06-27 15:10:22 UTC
Although this issue is CLOSED, I recommend considering the following:

Project Management (PMBOK, PRINCE2, etc.) propose "Deliverables" that are 
recommended dependent on situations or expectations for a given project.  These 
deliverables could be used to create a "OOPM Template" that gives each Project 
Manager a targeted End POint for a segment of their project schedule without 
pre-defining the tasks necessary to achieve that "Deliverable", nor does this 
template mandate that each section and subsection of these templated 
deliverables are needed for each project.

System Development Life Cycles (SDLCs) like MERISE, Agile / Scrum, Software 
ENgineering and Object Oriented published materials also 
recommend "Deliverables" when following their processes.  And, THESE 
deliverables are also premised on the expected Scope and Objectives of each 
project.  Templates of these Deliverables could also be made available to 
Project Managers for use similar to the PMLC artifacts above.