From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike McLean Subject: Re: if both schedule and deadline, appear only once in agenda Date: Tue, 5 Jun 2012 18:31:29 -0400 Message-ID: <6E5FF140-D01E-4BD3-87CA-4C15D17676A1@pobox.com> References: <87k5psaom7.fsf@hillenius.net> <87641ca3gh.fsf@bzg.ath.cx> <87y7e81q1t.fsf@hillenius.net> <87lka88nf9.fsf@bzg.ath.cx> <87ehpzpi68.fsf@ucl.ac.uk> Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: multipart/alternative; boundary="Apple-Mail=_3A90ECD8-F5C7-4E84-BDDE-C4A763DFCF9F" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34529) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sc2Ht-0003uJ-6Q for emacs-orgmode@gnu.org; Tue, 05 Jun 2012 18:31:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sc2Hn-0008Fu-AC for emacs-orgmode@gnu.org; Tue, 05 Jun 2012 18:31:40 -0400 Received: from a-pb-sasl-sd.pobox.com ([74.115.168.62]:54023 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sc2Hn-0008Ei-0S for emacs-orgmode@gnu.org; Tue, 05 Jun 2012 18:31:35 -0400 In-Reply-To: <87ehpzpi68.fsf@ucl.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode Mode Cc: SW --Apple-Mail=_3A90ECD8-F5C7-4E84-BDDE-C4A763DFCF9F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Jun 1, 2012, at 4:09 AM, Eric S Fraga wrote: > SW 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. >=20 > 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... >=20 > 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 =93project=94 = org-capture template has a sub task for defining the project. You could = setup your template in whatever way works for you.=20 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-wan= t-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 =93Project Definition=94 = 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 , I want = so \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 :) --Apple-Mail=_3A90ECD8-F5C7-4E84-BDDE-C4A763DFCF9F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
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 =93project=94 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/ad= vantages-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 =93Project = Definition=94 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 = :)


= --Apple-Mail=_3A90ECD8-F5C7-4E84-BDDE-C4A763DFCF9F--