Interesting reading. A "project", in the planning sense, is a
framework of dependant tasks and sub projects. Some tasks must wait
until another task is finished before they can begin. Other tasks can
be done in parallel. The project may have many dependancies,
milestones, things which must be done by a given date and usually a
"critical path" on which the end date of the whole project depends.
That is what you guys are leaning towards. But a "project" in the GTD
sense is just a personal goal. If you have to run a full-blown
project, like building a bridge, get some proper project management
software and do it through that. Meanwhile use GTD techniques to
manage your personal goals, one of which might be "Buy project
management software package" and later "update project plan in
<software package>" or "publish new milestone dates with <software
package>".
Sometimes I know even a GTD project will have several steps that you
know about at the outset. As Hugh says, you can create a Next Action
for each step, but this can make your Next Actions list long and
overwhelming to the eye. I tackle this by not creating Next Actions
for every step. I create the Next Action only, and occasionally a
second action for the Waiting Actions list. If I think there is a
danger I will forget those 5 future actions I just thought of, I put
some text in the Project notes section to remind myself later,
sometimes using bullets. Making notes in a project is a good way to
get thinking about actions required. I have learned though, that you
don't forget the future actions. Focussing on the Next Action, and
seeing it done, tends to make the next step obvious.
I use the project notes section mainly to record what I have done in a
project. When I context-switch back into the project at some future
date, the project notes section reminds me what happened. I find it
useful to make a notes starting with e "{t}", so they are
timestamped. Linking to outside documents is another good feature.
Eg. I have to install some software on 29 servers. I create a
spreadsheet and link to it from the notes. After that I can click the
link anytime and update the spreadsheet.
Anyway that turned out to be a right ramble. It's good to share.
On Sep 22, 3:55 am, Jeff <[EMAIL PROTECTED]> wrote:
> An interesting wrinkle is that not every project has dependent tasks.
> How would one track multiple dependent task "lines"? Multilple
> projects?
>
>
>
> On Sun, Sep 21, 2008 at 3:38 PM, Franck <[EMAIL PROTECTED]> wrote:
>
> >> What I have seen before, is where you have a bunch of actions
> >> associated with a project, but only the next action (in a pre-defined
> >> order) would appear on any of the views. Then when that task is
> >> completed, the next action on the list would be displayed. Again,
> >> this would allow you to deal with just the project per se, and not
> >> everything to do with the project.
>
> > Yes, that's exactly what I would need too. This would enhance project
> > management so much. In my view, the action directly depending on a
> > Next action being finished could appear among Waiting Actions, and the
> > next one among Future Actions. Then once the Next Action is ticked,
> > all subsequent actions would move one step forward. This way, if you
> > think your project through just once, everything will follow
> > automatically.
>
> > I've searched the forum and apparently such a feature has been
> > discussed before a few months ago:
> >http://groups.google.com/group/GTD-TiddlyWiki/browse_thread/thread/c1...
> > Let's hope this time we can get Simon motivated to do something about
> > it, that would be so terrific.
>
> > Franck
>
> --
> Jeff
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GTD
TiddlyWiki" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/GTD-TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---
