From: Daniel Bausch <DanielBausch@gmx.de>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: What do you use to identify projects (in the GTD sense)
Date: Tue, 11 Oct 2011 08:20:02 +0200 [thread overview]
Message-ID: <201110110820.03243.DanielBausch@gmx.de> (raw)
In-Reply-To: <CACHMzOFxgeudq+HkLitYM0T-iLYj0_XKgAbom6YnsEwCH2wmNA@mail.gmail.com>
Hi Marcelo,
its nothing special:
* Working Area (the order of these models some kind of global priorization)
:PROPERTIES:
:CATEGORY: CAT-A (<- some identifier to be displayed on the left of agenda)
:END:
** PROJ outcome or project title
*** DONE something done
*** NEXT the next action
*** TODO something currently not actionable (because of dependencies or so)
**** PROJ some subproject
***** ... you get it
Often I prefix the individual action items with short identifiers for the
containing project to give me some context in the agenda. Instead of
extending the strings it helps to keep them shorter.
For example:
TODO software-x: talk to Fred about the missing requirements
instead of
TODO talk to Fred about the missing requirements of software-x
In english its not very efficient, but in German it can save you a lot of
letters and you have a fixed position to look for the context. A tag may fit
the same needs but they are located less prominently and I think one needs the
context first.
Daniel
Am Montag 10 Oktober 2011, 20:44:46 schrieb Marcelo de Moraes Serpa:
> Hi Daneil,
>
> Looks interesting. Could you share a sample tree with projects and actions?
>
> Cheers,
>
> - Marcelo.
>
> On Mon, Oct 10, 2011 at 6:30 AM, Daniel Bausch <DanielBausch@gmx.de> wrote:
> > Hello,
> >
> > I use a todo keyword "PROJ" and a custom block agenda, that filters
> > different
> > interesting groups for review.
> >
> > (setq org-agenda-custom-commands
> >
> > '(("g" "My GTD Agenda"
> >
> > ((agenda "" ((org-agenda-ndays 1)
> >
> > (org-agenda-start-on-weekday nil)
> > (org-agenda-entry-types '(:timestamp :sexp))
> > (org-agenda-overriding-header "Appointments")))
> >
> > (agenda "" ((org-agenda-ndays 1)
> >
> > (org-agenda-start-on-weekday nil)
> > (org-agenda-entry-types '(:deadline))
> > (org-agenda-overriding-header "Upcoming Deadlines")
> > (org-agenda-sorting-strategy '(priority-down
> >
> > time-down))
> >
> > (org-agenda-skip-function '(org-agenda-skip-entry-if
> >
> > 'todo
> > 'done))))
> >
> > (agenda "" ((org-agenda-ndays 1)
> >
> > (org-agenda-start-on-weekday nil)
> > (org-agenda-entry-types '(:scheduled))
> > (org-agenda-overriding-header "Scheduled")
> > (org-agenda-sorting-strategy '(priority-down
> >
> > time-down))
> >
> > (org-agenda-skip-function '(org-agenda-skip-entry-if
> >
> > 'todo
> > 'done))))
> >
> > (todo "WAIT" ((org-agenda-sorting-strategy '(priority-down))
> >
> > (org-agenda-overriding-header "Waiting For")))
> >
> > (todo "NEXT" ((org-agenda-sorting-strategy '(priority-down
> > effort-
> >
> > down))
> >
> > (org-agenda-skip-function
> > '(org-agenda-skip-entry-if
> >
> > 'scheduled 'deadline))
> >
> > (org-agenda-overriding-header "Next actions not
> >
> > being
> > scheduled nor having a deadline")))
> >
> > (todo "TODO" ((org-agenda-sorting-strategy '(priority-down
> > effort-
> >
> > down))
> >
> > (org-agenda-skip-function
> > '(org-agenda-skip-entry-if
> >
> > 'scheduled 'deadline))
> >
> > (org-agenda-overriding-header "Future actions not
> >
> > being scheduled nor having a deadline")))
> >
> > (todo "PROJ" ((org-agenda-overriding-header "Active
> >
> > Projects")))))))
> >
> >
> > Along with colors
> >
> > '(org-todo-keyword-faces (quote (("PROJ" :foreground "Orange" :weight
> >
> > bold)
> > ("MSTN" :foreground "VioletRed" :weight bold) ("WAIT" :foreground "Blue"
> >
> > :weight bold) ("CNCL" :foreground "MediumSeaGreen" :weight bold))))
> >
> > and
> >
> > '(org-enforce-todo-checkbox-dependencies t)
> > '(org-enforce-todo-dependencies t)
> >
> > this works really well for GTD.
> >
> > Kind regards,
> > Daniel
> >
> > Am Montag 10 Oktober 2011, 08:21:57 schrieb Marcelo de Moraes Serpa:
> > > Hey list,
> > >
> > > I'm wondering if you make the distinction between projects and
> > > actionable items. If you stop to think about it (specially if you read
> > > GTD by David Allen), you see that you can't really "do" a project, but
> > > only actions related to it. It's a powerful and underestimated
> > > concept. Of course, a todo list is still a reminder of things, and any
> > > list can be useful, but the more specific you are, the less you have
> > > to think (process) and the more you can actually execute.
> > >
> > > Anyway, I was wondering how you guys differentiate between projects and
> > > next actions (todo's) in your org lists. I myself use a :project: tag
> > > for projects and todos have todo keywords before them. Projects never
> > > have a todo keyword, except when DONE. I used to use a PROJECT keyword
> > > before, but I felt that a tag seems to work better (and allows you to
> > > actually filter todos without mixing projects). So, a typical list
> > > looks like
> >
> > this:
> > > * New feature :project:
> > > ** TODO Create a mockup for the index page
> > > ** TODO Convert the mockup to html
> > > * Renew passport :project:
> > > ** DONE Call for appointment
> > > ** TODO Interveiw
> > >
> > > SCHEDULED <...>
> > >
> > > ** DONE Buy groceries :project: ...
> > >
> > > How do you do it?
> > >
> > > Thanks in advance,
> > >
> > > - Marcelo.
next prev parent reply other threads:[~2011-10-11 6:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 6:21 What do you use to identify projects (in the GTD sense) Marcelo de Moraes Serpa
2011-10-10 11:30 ` Daniel Bausch
2011-10-10 18:44 ` Marcelo de Moraes Serpa
2011-10-11 6:20 ` Daniel Bausch [this message]
2011-10-11 1:28 ` Bernt Hansen
2011-10-11 8:16 ` Sven Bretfeld
2011-12-11 16:49 ` Viktor Rosenfeld
2011-12-11 22:18 ` Bernt Hansen
2011-12-12 18:29 ` Viktor Rosenfeld
2011-12-12 19:58 ` Bernt Hansen
2011-12-15 14:41 ` Defining dependencies (was: What do you use to identify projects (in the GTD sense)) Karl Voit
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=201110110820.03243.DanielBausch@gmx.de \
--to=danielbausch@gmx.de \
--cc=celoserpa@gmail.com \
--cc=emacs-orgmode@gnu.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).