Modify

Opened 4 years ago

Last modified 4 years ago

#10580 new enhancement

Optimized resource leveling (if there are ticket dependencies)

Reported by: falkb Owned by: Chris Nelson
Priority: normal Component: TracJsGanttPlugin
Severity: normal Keywords:
Cc: Trac Release:

Description

Do you see a chance to improve the resource leveling this way?:

This is a sketch one of my users gave me. He says the red ticket should rather be scheduled like the green ticket. This would extremely help to improve the planning he says.

Attachments (1)

optimRessourceLeveling.PNG (8.5 KB) - added by falkb 4 years ago.

Download all attachments as: .zip

Change History (3)

Changed 4 years ago by falkb

Attachment: optimRessourceLeveling.PNG added

comment:1 Changed 4 years ago by Chris Nelson

If I understand correctly, you're saying tickets 3 and 4 are both assigned to user X and since ticket 2 (assigned to user Y) blocks 3, ticket 4 could begin earlier. I don't see that as a resource leveling issue, I see it as a scheduling/prioritizing issue. The rule I'd invoke would be that all other things being equal, a ticket without predecessors should be scheduled before one with. That would accomplish what you want and I'll add that to the list of valuable rules.

My notes at http://trac-hacks.org/wiki/ProjectManagementIdeas#IProjectSchedule are a bit dated but the principle outlined there about complex rules for sequencing tasks still hold. I've implemented this in the existing schedulers which defer sorting decisions to the task sorter (ITaskSorter). There are two implementations in the distribution (SimpleSorter (sort only by priority) and ProjectSorter (an attempt to have priority percolate through a ticket hierarchy)). I have plans for a more sophisticated sorter but if you can't wait, you could develop and enable your own ITaskSorter which prioritized tickets without predecessors. Note that the BaseSorter provides some useful utilities when implementing your own sorter.

comment:2 in reply to:  1 Changed 4 years ago by falkb

Replying to ChrisNelson:

... ticket 4 could begin earlier...

Yes, simply, if they want to plan a milestone, it doesn't make sense to leave X without work when Y is working on 2.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain Chris Nelson.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.