Hi guys,
follow up to this item. With a bit of lateral thinking I came up with a solution. This was to nest the tasks not by project but by time frame. So, day was a subtask of week, week a subtask of month etc.
Then when tasks were supposed to be done for today they would be added as a day subtask. ToDoList then summed those estimated times to come up with the total committed time for that day. Same goes for week, month etc.
I think quite an elegant solution and certainly simpler than an MS Project approach but a bit more complexity comes when ones want to maintain the hierarchy of large projects etc. But again, ToDoList could provide a solution using the reference task feature.
In the end I think a reasonable way to estimate resources committed for a certain time frame and thus the time available for new tasks.
The article describing the approach is (
http://donebeforebrekky.com/matryoshka-todo-list-task-planning/)I think it could also be a good approach for sprint planning and I will cover this at some point - In this case though I think a filtered view would be needed and so the issue of the estimated time calculations would again be a consideration.
thanks
Brendan
On Monday, November 2, 2015 at 7:57:29 AM UTC+8, .dan.g. wrote: