Apache OpenOffice (AOO) Bugzilla – Issue 57608
Prototype Requirement: Personal task plan for project members
Last modified: 2017-05-20 09:12:09 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
This topic can be regarded as summary of - 57609: Personal calendar for project members - Combine todo lists with priority and tasks (issue 57642) - Calendar for appointments/time planning (issue 57645) A team member (=resource) must be able to extract his tasks (of all the projects he is involved in) to his calendars or as print-out. Difficult to realize will be updates, i.e. changes of his tasks in the project have to update (and not just add) existing dates in the calendar. I see the synchronization as in 1-way only, so from the project management tool to the calendar. Maybe the techniques, PDAs are using could be helpful. It should be possible to perform this extraction of tasks not per project but to select all the projects one is involved in. As minimal initial implementation (also for the "easy" application) just a print-out of tasks in a calendar could be useful. This was also already mentioned under reporting. Data should be: - project name, ID - task name, -ID - work load - start, end - custom defined fields (e.g. comments by project manager)
In addition I would like to also personal interest/capability based prioritization of individual tasks in a project, regardless of what the PM has defined. That is, the PM defined that a single person's assignment to one task is of priority 8. However, since the person has multiple of such assignments, she might choose to re-prioritize those assignments based on both personal capability and availability. This, however, should not be reflected in the general project plan, but on a personal plan for that person alone. The PM might then be interested into when a given person thinks that he might solve or at least invest some time into a given task. We should definitely allow the PM to (re)view the personal plan of a given person towards a given task or multiple tasks thereof. To sum it up, a single person might re-prioritize individual assigned tasks and allocated (start/end) time durations based on personal requirement needs. Such re-prioritizations are considered natural and thus will not be reflected in the project's overall schedule and plan. Yet, the PM might always take a look into a person's personal plan for solving (i.e. investing some of the available WorkPower expressed by the time available to that person) a given task and to whence she has re-scheduled the solving of a given task assignment. Re-scheduling a given task assignment by a single person must be within the scheduled time boundaries set forth by the PM. Re-scheduling beyond that time requires re-scheduling on the global project basis and thus intimidate communication with the PM. This basically means that we will not provide for automation of such processes, we still require personal communication here. This is due respect of separation of concern, in that case, delegation of responsibilities.
Damn, why does this tool not provide oneself to edit previous comments posted by oneself? Previous post by me includes a rather disastrous typo: it misses a very important word in the initial paragraph: Where it reads > In addition I would like to also personal interest/capability based > prioritization of individual tasks in a project, regardless of what the PM has > defined. it should read > In addition I would like to __add__ also personal interest/capability based > prioritization of individual tasks in a project, regardless of what the PM has > defined.
the above is actually about multi tasking, which is actually considered harmful, see existing studies. one needs to make sure that she does not become overloaded by the tasks assigned, therefore one should be able to reassign personal priorities to all of the assigned tasks, even in an across-project way. of course, escalation of a task should still and definitely be based on the initial priority assigned by one of the available project managers, however personal ordering based on personal prioritisation should still overrule existing PM prioritisation. We could solve this using colours a/o static annotations, but, please, no more bubble pop-ups).
Reset assignee on issues not touched by assignee in more than 1000 days.
obsolete