Apache OpenOffice (AOO) Bugzilla – Issue 57601
Requirements specification for project management tool prototype
Last modified: 2017-05-20 09:12:08 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.
Assigned the task to myself
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
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.
Regards sub-projects -- absolutely. More technically, a task should either be a node in a directed graph or a itself be a directed graph.
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.
please also have a look at IZ 60554
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
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
Created attachment 41862 [details] Additional wishes
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.
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.
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
Reset assignee on issues not touched by assignee in more than 1000 days.
obsolete