From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id 8IuQJdDlH2IdrgAAgWs5BA (envelope-from ) for ; Wed, 02 Mar 2022 22:46:56 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id 2D0DI9DlH2IZygAA9RJhRA (envelope-from ) for ; Wed, 02 Mar 2022 22:46:56 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 32C9E29583 for ; Wed, 2 Mar 2022 22:46:56 +0100 (CET) Received: from localhost ([::1]:60330 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nPWoA-0007Pu-UH for larch@yhetil.org; Wed, 02 Mar 2022 16:46:55 -0500 Received: from eggs.gnu.org ([209.51.188.92]:52858) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nPWXO-0003pm-PV for emacs-orgmode@gnu.org; Wed, 02 Mar 2022 16:29:36 -0500 Received: from 96-100-31-185.ftth.cust.kwaoo.net ([185.31.100.96]:58364 helo=gandalf.k-7.ch) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nPWXM-0002KN-T9 for emacs-orgmode@gnu.org; Wed, 02 Mar 2022 16:29:34 -0500 Received: from sherazad-lan (alfred.lan [192.168.1.1]) (Authenticated sender: seb) by gandalf.k-7.ch (Postfix) with ESMTPSA id B094F109961; Wed, 2 Mar 2022 22:29:28 +0100 (CET) References: <87k0dee17l.fsf@ericabrahamsen.net> User-agent: mu4e 1.6.6; emacs 27.2 From: =?utf-8?Q?S=C3=A9bastien?= Gendre To: Eric Abrahamsen Subject: Re: How do you manage complex project with Org-mode Date: Wed, 02 Mar 2022 22:26:01 +0100 In-reply-to: <87k0dee17l.fsf@ericabrahamsen.net> Message-ID: <87pmn4rqkn.fsf@k-7.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: permerror client-ip=185.31.100.96; envelope-from=seb@k-7.ch; helo=gandalf.k-7.ch X-Spam_score_int: -6 X-Spam_score: -0.7 X-Spam_bar: / X-Spam_report: (-0.7 / 5.0 requ) BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.187, PDS_RDNS_DYNAMIC_FP=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, TVD_RCVD_IP=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1646257616; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=m/HDQbwuZwCnDTQUQfaUQCa4oZ4TKZmOsjE4KD3ahRY=; b=J1lhMNFpxrchakNro8hY+cRAqskuRupc6YMExBOPK4bCOMqx0AU9x4YA7l5Sw9xE/+GlEu MogXIloYMmoV9BnwcWSDj4tUxpqigqFbqzf0dunJI5+lgG73bs6hB8PBznVLP1haDAo53r ARmFNQ65OxJpClhZX+mUHvPOwoRkAjFkeNEXqLe+hKrqclRP10iB4AnlwPjsm+BxytxLQZ sBWOUXFK40+x5TW+SGDRMKn1INTjL6JNXf7uIruBbbthT+/8BlmgDzZgPHnjddNaGdefgu buUvDxEkKpk662FJBRCkBDIYZT+N3YzwYPgTWpmAFUR99gt3ppxZxnuMZlVN1A== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1646257616; a=rsa-sha256; cv=none; b=EwT0ze+xq2rMxgUy7gzgc19I7mXIx106uKyrq764u9rEG1nLwwjlhQKoI3uW2Bed7/7dJF HfXYB8cKPZ3hq+N5ZWLylxdskVNJ6YO1faYAAUKn2r8rRJWmvyWZKtwO1AzYVfv1BwXdQ7 dNBrusyDQ6kG7XDTHyKwf6yfDPKhpNlA59RGjh0hlRNX8HjkZNsmZ9dacGNGrGW/pZXTkG h5vQ4nEIsWD0uCTulZ9CILiJeCg2PSiDd0fdAfolGIJ7OULaMkF9eJSGI0ei44+bZZKPwh iLCi2/ymHNjQqn7VcwiPmQaWuABLZeGFp5cP+jomaJ9DH3LRdZXF7F8+0pNY6w== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -3.87 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 32C9E29583 X-Spam-Score: -3.87 X-Migadu-Scanner: scn0.migadu.com X-TUID: yoYJPzi4Dprt Hello Eric, Thanks for your reply and advice. I will look at custom agenda view and clocking. But I have bad memory of clocking tools because of the way previous jobs used it (It was not Emacs). Eric Abrahamsen writes: > S=C3=A9bastien Gendre writes: > >> Hello, >> >> I don't know if it's the correct place to ask it. If not, sorry to ask in >> the wrong place. >> >> How do you manage complex project with Org-mode=C2=A0? >> >> I used Org-mode for several periods of time in recent years. It worked >> very well for short and day to day tasks. When only a few of theme have >> deadlines and when you have plenty of time to do them. >> >> But, as a student, I regularly have big and important projects to do for >> the school. The kind of project who need several days to be done, with >> deadlines too soon, and if you fail one them the consequences can be >> disastrous. And generally, I have to many of these project in the same >> time and not enough time to do all the work. So, I also need to follow >> the progress of each project to choose which is sufficiently advanced to >> be stop for the benefit of another less advanced project. >> >> And I don't know how to manage this kind of projects with Org-mode. How >> to do it, without failing a 6 days project because I spent to much time >> on something else and I have only 3 days left with 3 half-day important >> appointment I cannot cancel. I can't risk failing a single one of these >> project by trying. So, when I am in a period with a lot of these >> projects, I stop using Org-mode and concentrate on doing these project >> as fast as I can. And because I often have this kind of project, I spend >> most of the year without being able to use Org-mode. >> >> So, if you have any suggestion on how to manage, in Org-mode, projects >> with: >> * Lot of work to do (many days) >> * Short deadline (not enough time) >> * High importance (disastrous consequences in my future in case of fail) >> * Many of them in the same time >> * Progression need to be followed to chose where to sacrifice time to >> limit the damages > > Interesting questions! I have the same general problem of, when things > heat up too much, I stop using the Org agenda. It's quite the opposite > of how it's supposed to work, but I guess it's something about human > psychology. I'll be interested to see what people say in this thread. > > Some suggestions that come to mind: > > - Create custom agenda views for each project, providing an overview of > that project only, but use a single unified agenda view for each day's > schedule. Look at the per-project agenda to decide if/how to complete > it, but draw the action items into the unified schedule when deciding > how to spend your day. It should become evident pretty quickly what > you actually have time for. Projects are many, but there is only one > of you. > - Maybe consider using `org-trigger-hook' and `org-blocker-hook' to cut > down on TODO overwhelm. > - Use time estimates and then TODO clocking to more swiftly disabuse > yourself of unrealistic expectations. This plus a schedule agenda can > also help you make sure you stop work at a reasonable time and go do > something else. > - Say no to more work :) Looking at your solid-packed agenda for the > next day works wonders for saying no. > > Good luck!