emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sven Bretfeld" <sven.bretfeld@gmx.ch>
To: "Hellekin O. Wolf" <hellekin@cepheide.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: AutOrg, and practice of GTD in a group
Date: 23 Jun 2010 08:41:22 +0200	[thread overview]
Message-ID: <87wrtqqmi5.fsf@gmx.ch> (raw)
In-Reply-To: <20100622211941.GF520@now.cepheide.org> (Hellekin O. Wolf's message of "Tue, 22 Jun 2010 21:19:41 +0000")

Hi Hellekin

"Hellekin O. Wolf" <hellekin@cepheide.org> writes:

> How do you guys use CATEGORIES, PROPERTIES and TAGS in combination
> with TODO states and Org-Agenda to optimize your GTD workflow?

I'm also into GTD. This is a typical entry I use for a project.

* Misc Office
** Rewrite study course documents               :PROJECT:
*** NEXT Rework Text                           	:HOME:
    :PROPERTIES:
    :TRIGGER:  chain-siblings(NEXT)
    :END:
*** Mail Text to Volkhard			:OFFICE:
*** Discuss Text with Volkhard                  :OFFICE:
    :PROPERTIES:
    :dowith:   volkhard
    :END:
*** Mail Text to other Profs			:OFFICE:

Explanation:

First level is for divisions of my life (here: Misc Office, others are
Family, Teaching, Research etc.). 

The second level I use to denote projects (in the GTD meaning) or for
some small tasks which include only one physical action. In the first
case I use no todo keyword and only the PROJECT tag (to create a list of
projects and to define what a stuck project is). In the second case, I
would give the NEXT keyword already on the second level (not shown
here).

The third level is for the physical actions of the project. As you see,
only the first has a todo keyword (NEXT). The others are dependent from
the first (cannot be done before the first is done) and have only a
context tag. My context tags include things like HOME, OFFICE, SHOPPING,
TRAIN etc. When the first NEXT action is done, the next NEXT action in
the list gains the NEXT todo keyword automatically; this is what the
TRIGGER property cares for. In that way my Agenda Views (defined as
NEXT/HOME, NEXT/OFFICE etc.) display only next actions that can be done
immediately. 

As I'm working in a team, I have long searched for a way to tell Orgmode
who is with me at a certain moment and display the things that have to
be done together with the(se) person(s). I have recently discovered
org-secretary for that purpose. For the above case, if Volkard enters my
office, I tell Emacs that he is now with me, and a special agenda view
displays all the things I want to do with him. This is what the "dowith"
property is for.

Apart from PROJECTS and contexts I have two more tags defined: BIGROCK
and MIT. The first is given to projects that I want to concentrate on
this week (never more than 3 projects contain that tag). MIT means "Most
Important Thing (of the day)". I use this tag to mark three to four NEXT
actions every night. These are the first things I care for on the next
day. 

> What strategy do you take when you have a personal SEQ_TODO and need
> to work with other people, using a different SEQ_TODO?

Have a look on org-secretary.

Greetings,

Sven

  parent reply	other threads:[~2010-06-23  6:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 21:19 AutOrg, and practice of GTD in a group Hellekin O. Wolf
2010-06-22 22:09 ` Bernt Hansen
2010-06-23 17:41   ` Hellekin O. Wolf
2010-06-23  6:41 ` Sven Bretfeld [this message]
2010-06-24 13:00   ` Hellekin O. Wolf
2010-06-24 13:21     ` Jason McBrayer
2010-06-27 20:16     ` Sven Bretfeld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wrtqqmi5.fsf@gmx.ch \
    --to=sven.bretfeld@gmx.ch \
    --cc=emacs-orgmode@gnu.org \
    --cc=hellekin@cepheide.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).