emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] What do you use to identify projects (in the GTD sense)


From: Viktor Rosenfeld
Subject: Re: [O] What do you use to identify projects (in the GTD sense)
Date: Mon, 12 Dec 2011 19:29:55 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

Hi Bernt,

sorry, I wasn't more specific. My problem is with projects that consist
of subprojects and simple tasks. Consider the following scenario:

* TODO Project
** TODO Subproject A
*** NEXT Task A1
*** TODO Task A2
** NEXT Task B
** TODO Task C
** TODO ...

Task B and C have to be done in order. However, Subproject A is somewhat
independent and can be done in parallel, while working on Task B and C.

When I mark Task B as DONE, the Project is still unstuck because of the
a NEXT task in Subproject A. Meaning that I never get to schedule Task C
or any following tasks until I'm done with Subproject A.

One solution to this problem would be to trigger a state change in Task
C automatically when Task B is done. But I'm afraid that is too much
setup and also not flexible enough. Often, when I consider a stuck
project I schedule next actions that I haven't thought of before or even
put the project on a someday list.

Another solution would be to implement a stale projects list, i.e. a
list of projects that have defined next actions, but haven't seen any
work in the last X days.

Cheers,
Viktor

PS: Your org-mode site is generally the bomb!

Bernt Hansen wrote:

> Viktor Rosenfeld <address@hidden> writes:
> 
> > I use Bernt's approach with a few modifications. Basically I don't use
> > subprojects. I think Bernt's handling of subprojects is broken, because
> > a NEXT keyword burried in a subproject keeps the entire project off the
> > stuck projects lists. (Please correct me if I'm wrong.)
> 
> It's possible it's broken :) but subprojects are considered separately
> for the stuck project list.  It is true that if any subproject has a
> NEXT task then the overall project is not stuck (but doesn't that makes
> sense?)
> 
> * TODO Project
> ** TODO SubProject A
> *** NEXT Task One
> ** TODO SubProject B
> *** TODO Task Two
> 
> In the above layout Project is not stuck (it has Task One as a NEXT
> task) but SubProject B is stuck (it has no next task and shows up on the
> stuck project list)
> 
> Also as soon as Task One is DONE than both SubProject A and Project are
> both stuck until a new NEXT task is identified (or they are in turn
> marked DONE)
> 
> Regards,
> Bernt
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]