1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
Here are some ideas for future enhancements, in no particular order:
- Alter text and tex reports to handle milestones
- See why start doesn't work
- tidy up source code
- make it handle first week when start date not a monday
* Add some rational approach to comparing an original schedule
to a current (early? late?) schedule.
(some stuff is already done here)
* Support time overruns. (some stuff is already in place here)
* Add a GUI to edit project files, and display scheduling results.
* Add support to grouping tasks together. This will help with:
- fewer dependencies need to be listed
- groups of tasks may depend on other groups
- GANTT charts can be simplified, showing only groups
* Allow GANTT charts to be printed for individual resources or
groups of resources; and for groups of tasks.
* Task groups -- can be used to simplify dependencies, and perhaps
to reduce detail in a print-out.
* Milestones -- draw a line when a task group is done.
* Show slack in the GANTT charts (time from task end to dependency start)
* Different work schedules (not just Mon-Fri):
some people work Mon-Fri, some work Mon-Sat, etc. Right
now the system just assumes everyone works on the same days.
Days number 0-N represent only Mon-Fri, so it's impossible
to schedule weekends.
The current system can be changed as follows:
- Have days 0-N represent Sun-Sat.
- Model weekends as vacations
- Have a statement in the project file that lets us set recurring
vacations (weekends and such) for resources, using day names,
date ranges and wildcard expressions for resource IDs.
- Modify scheduling of "block" tasks so that they can span
one or more holidays.
----------------------------------------------------------------------
Any volunteers?
|
