Managing projects with multiple tasks within
mcandea says:
One of the complaints I had myself when starting to use RTM was the absence of a way to group tasks in a hierarchical manner, as in a project, which is typically made of multiple tasks.
That way one would had the next action in the project at hand (as GTD recommends) while still keeping together the following actions. I found the tagging feature not intuitive enough for the purpose.
I also remember finding somewhere the response of RTM team why they didn't consider this feature necessary, and understood the reasons - although I don't remember them right now :).
The way I came around this might actually be better than the real thing. I have a single task for the project, and in its name I list all the actions in the project separated by "->". The first action in the list is the next actions, and the due date of the "big" task is the due date of the action. When I complete the first action I erase it from the task list, and set a due date for the big task, and therefore for the new next action.
Example:
For my trip to Sziget festival the things I had to do were like:
Ask for vacation at work -> Book hotel room in Budapest (with no cancellation fee if possible) -> Inquiry about festival tickets -> Buy train ticket -> Buy festival ticket
I completed them one by one, always setting a new due date to progress with my personal project. When there was nothing left in the list I was set to go. Woohoo!
That way one would had the next action in the project at hand (as GTD recommends) while still keeping together the following actions. I found the tagging feature not intuitive enough for the purpose.
I also remember finding somewhere the response of RTM team why they didn't consider this feature necessary, and understood the reasons - although I don't remember them right now :).
The way I came around this might actually be better than the real thing. I have a single task for the project, and in its name I list all the actions in the project separated by "->". The first action in the list is the next actions, and the due date of the "big" task is the due date of the action. When I complete the first action I erase it from the task list, and set a due date for the big task, and therefore for the new next action.
Example:
For my trip to Sziget festival the things I had to do were like:
Ask for vacation at work -> Book hotel room in Budapest (with no cancellation fee if possible) -> Inquiry about festival tickets -> Buy train ticket -> Buy festival ticket
I completed them one by one, always setting a new due date to progress with my personal project. When there was nothing left in the list I was set to go. Woohoo!
tforst says:
Nice idea! And it surely works, but I would prefer hierarchical lists, to be honest. Especially for more sophisticated projects than a trip to anywhere. But thank you for the good workaround.
sebastiaankop says:
I want this feature also.
A way to group a bunch of tasks together like in a project. And with the push of one button a list of that project and its tasks.
A way to group a bunch of tasks together like in a project. And with the push of one button a list of that project and its tasks.
pauljacobson says:
I would also like to see hierarchical lists or perhaps even a way to group projects for the same clients together under a single tab. Something like that. I have multiple projects for multiple clients and creating lists for each project may be the way to go as far as GTD goes (I like the methodology and I am working on implementing GTD myself) but it does clutter up my task lists.
mcandea, your suggestion doesn't seem to allow for much flexibility when it comes to checking off some of the items for each task and not others. I know that I would just not get stuff done because it isn't granular enough for me. The act of checking off tasks towards a project's completion gives me a sense that I am getting somewhere. Just a thought.
mcandea, your suggestion doesn't seem to allow for much flexibility when it comes to checking off some of the items for each task and not others. I know that I would just not get stuff done because it isn't granular enough for me. The act of checking off tasks towards a project's completion gives me a sense that I am getting somewhere. Just a thought.
jans.roeber says:
Why not creating a tag with the name of the project, scheduling all tasks with a due date and evt. contexts and then working them off sequentially ?
Projects tags might start with a dot and context tags with an @ ....
This methodology has been published first by David Hellmann in his (german) blog.
Give it a try, it works too!
Projects tags might start with a dot and context tags with an @ ....
This methodology has been published first by David Hellmann in his (german) blog.
Give it a try, it works too!
Log in
to post a reply.