emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mike McLean <mike.mclean@pobox.com>
To: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Cc: SW <sabrewolfy@gmail.com>
Subject: Re: if both schedule and deadline, appear only once in agenda
Date: Tue, 5 Jun 2012 18:31:29 -0400	[thread overview]
Message-ID: <6E5FF140-D01E-4BD3-87CA-4C15D17676A1@pobox.com> (raw)
In-Reply-To: <87ehpzpi68.fsf@ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 2353 bytes --]


On Jun 1, 2012, at 4:09 AM, Eric S Fraga wrote:

> SW <sabrewolfy@gmail.com> writes:
>> However, this is not what my question is about. My question relates to advance
>> warning that an item is scheduled in the future. I want to know on Friday that I
>> have scheduled a large project to start on Monday. That is, I would like to know
>> beforehand that I need to start working on a large project in a few days time.
> 
> One approach is to consider that "thinking about a large project about
> to start" is itself a task so you could look at adding a task for the
> Friday, when you first scheduled the large task for the Monday, to tell
> you start thinking...
> 
> This might sound silly but it can actually be quite useful if you get
> into the habit of thinking about such aspects when you schedule tasks.

I agree with this sentiment wholeheartedly. My default “project” org-capture template has a sub task for defining the project. You could setup your template in whatever way works for you. 

I used to use a version of the GTD Natural Planning model with bullets for Purpose, Principles, Vision, Outcome, etc. I have since simplified to a MadLibs user story format: http://www.mountaingoatsoftware.com/blog/advantages-of-the-as-a-user-i-want-user-story-template

If I know the broad outlines of project at the time of capture, I fill it all in with the capture template. If I do not yet have the project fully thought out, I add a TODO keyword to the “Project Definition” subheading. Depending on the project I add scheduled and/or deadline dates to the project itself and/or the Project Definition TODO. The relevant snippet from my org-capture is:

#+begin_src emacs-lisp
(setq org-capture-templates (quote (
	("P" "project" entry (file "~/Documents/OrgMaster/org/refile.org") "* %?       :Project_Backlog: \n  %U\n** Project Definition\n- Summary\n  + As <personal role>, I want <goal> so <reason>\n- Completion Criteria (Don't do too much)\n  + \n" :clock-in t :clock-resume t)
)))
#+end_src

Since I have clocking as part of my capture template, I also record the time I spend writing the project requirements against the project -- when I refile the project that time moves with the refile to be charged against the broader desired outcome. I get quite a bit of quantified self information this way :)



[-- Attachment #2: Type: text/html, Size: 3299 bytes --]

      reply	other threads:[~2012-06-05 22:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12  5:28 if both schedule and deadline, appear only once in agenda Gijs Hillenius
2007-10-12 13:05 ` Bastien
2007-10-12 12:21   ` Gijs Hillenius
2007-10-12 13:36     ` Bastien
2012-01-10 10:15       ` Detlef Steuer
2012-05-30  9:12       ` SW
2012-05-30  9:46         ` suvayu ali
2012-05-30  9:52           ` SW
2012-06-01  8:09             ` Eric S Fraga
2012-06-05 22:31               ` Mike McLean [this message]

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=6E5FF140-D01E-4BD3-87CA-4C15D17676A1@pobox.com \
    --to=mike.mclean@pobox.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sabrewolfy@gmail.com \
    /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).