Issue 57601 - Requirements specification for project management tool prototype
Summary: Requirements specification for project management tool prototype
Status: CLOSED OBSOLETE
Alias: None
Product: oopm
Classification: Unclassified
Component: www (show other issues)
Version: current
Hardware: All All
: P3 Trivial
Target Milestone: AOO PleaseHelp
Assignee: AOO issues mailing list
QA Contact: issues@oopm
URL:
Keywords:
Depends on: 57602 57603 57604 57605 57606 57607 57608 57609 57610 57623 57624 57625 57626 57627 57628 57629 57630 57631 57632 57633 57634 57635 57636 57637 57638 57639 57640 57641 57642 57643 57644 57645 57650 57651 75158 99317 99321 99460 99464
Blocks:
  Show dependency tree
 
Reported: 2005-11-09 22:00 UTC by ooo
Modified: 2017-05-20 09:12 UTC (History)
1 user (show)

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


Attachments
Additional wishes (76.14 KB, application/vnd.sun.xml.writer)
2007-01-03 17:56 UTC, officista
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description ooo 2005-11-09 22:00:19 UTC
The document to end this task is the requirements specification for the  
prototype of OpenOffice.org Project Management Tool.  
  
The requirements will be based on the wishlist at   
http://oopm.openoffice.org/initial_analyze/wishes.html  
  
Each requirement will be discussed in its own issue. 
 
This task is finished when all the suggested requirements (wishes) has been 
stated either finished or the target milestone sat to "OOo later", and the 
document Requirements Specification for Project Management Tool Prototype is 
finished.
Comment 1 ooo 2005-11-09 22:08:08 UTC
Assigned the task to myself 
Comment 2 bobharvey 2005-11-24 21:08:08 UTC
I would like to add a suggestion to
http://oopm.openoffice.org/initial_analyze/wishes.html

Hierarchical sub-tasks

I think that it should be possible to plan each task of a plan as though it were
a project in its own right.  For example, a new industrial control system would
have as component tasks the design of PCBs for IO, user interaction,
interconnection.  But the developement of each PCB is a project with resources,
milestones, tasks and procedures.  This would require a plan of the same form.

The resource pool should, of course, be inherited from the master project. 
Resource levelling and conflicts would have to be followed recursively
Comment 3 bobharvey 2005-11-24 21:12:31 UTC
I would like to add a suggestion to
http://oopm.openoffice.org/initial_analyze/wishes.html

Document management and control

The creation of tasks in a plan frequently implies or requires a raft of
associated documents:  A functional spec is required to define design
sub-components, each component needs a design spec before starting and test spec
at the end, and integration tests are implied by merging sub-components back
into the final path.

I think that a project planning tool that allows documents to be archived and
accessed would be very useful.
Comment 4 gilh 2005-11-25 15:21:00 UTC
Regards sub-projects -- absolutely.

More technically, a task should either be a node in a directed graph or a itself
be a directed graph.
Comment 5 bobharvey 2005-12-05 22:23:43 UTC
I would like to add a suggestion to
http://oopm.openoffice.org/initial_analyze/wishes.html

Email updating of progress

It should be possible to record progress on a task (hours spent, milestones
achieved, completion or delay insertion) by email to the planning server.  This
would allow simple unix scripts to update tasks by name or reference in an
automatic manner from other accounting, time keeping, or project recording systems.

Email query of status

It should be possible to send a simple query to the planning server by email
requesting the latest status on a task, sub-task, or other progress metric.
Comment 6 flibby05 2006-01-15 09:51:44 UTC
please also have a look at IZ 60554
Comment 7 leelee41 2006-02-21 20:31:23 UTC
Hello.  I saw your oopm project and I am interested in it.  I searched through 
your issues archive for the words Earned Value and EVM.  I didn't find 
anything so I would like to suggest that this project include Earned Value 
calculations.  The organization I work for is very big on EVM as a way to 
control projects.

Thanks a lot.

Lee Farquharson
lfarquharson@gmail.com
Comment 8 supermario 2006-04-22 18:47:26 UTC
I'd like to suggest supporting project management using the Theory Of
Constraints (TOC), and it's "Critical Chain".

http://en.wikipedia.org/wiki/Theory_of_constraints
http://en.wikipedia.org/wiki/Critical_Chain
Comment 9 officista 2007-01-03 17:56:54 UTC
Created attachment 41862 [details]
Additional wishes
Comment 10 igor_cali 2007-08-03 01:14:19 UTC
I think a good PM tool should provide, furthen than classical Gantt charts etc 
following features:
- to link external or embedded documents to each task;
- to link resources to the system Address Book (for example Thunderbird);
- to edit organization charts;
- to set alarms/reminders/check-point for any task;
- to submit/evaluate and then approve/reject planning revisions;
- to version/baseline the project status.
Comment 11 wendyamos 2007-10-17 19:38:24 UTC
Can an OooPM tool have a more 'intuitive' user interface i.e. graphic point & 
click rather than the rigorous table driven interfaces.  A user simple 
interface would enable the tool to be used by various PM skill levels making 
the tool more useful in more scenarios - home, hobby, business, creative 
community projects... and more usable as a tool to collabortively & 
interactively develop project plans with a creative team.
Comment 12 ooo 2009-02-06 12:09:25 UTC
During the next couple of days I will create new issues with the wishes you all
have written to this issue.

Thank you.

Claus Agerskov, co-lead/owner, OOPM subproject
Comment 13 Rob Weir 2013-07-30 02:35:51 UTC
Reset assignee on issues not touched by assignee in more than 1000 days.
Comment 14 Marcus 2017-05-20 09:11:36 UTC
obsolete