From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id uBqxK4G2NmJQBQAAgWs5BA (envelope-from ) for ; Sun, 20 Mar 2022 06:07:13 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id EIJjKIG2NmKVwwAAauVa8A (envelope-from ) for ; Sun, 20 Mar 2022 06:07:13 +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 F3484A684 for ; Sun, 20 Mar 2022 06:07:12 +0100 (CET) Received: from localhost ([::1]:60868 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nVnmZ-0004CC-ED for larch@yhetil.org; Sun, 20 Mar 2022 01:07:11 -0400 Received: from eggs.gnu.org ([209.51.188.92]:39862) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nVnlo-0004C2-86 for emacs-orgmode@gnu.org; Sun, 20 Mar 2022 01:06:24 -0400 Received: from [2607:f8b0:4864:20::1034] (port=33300 helo=mail-pj1-x1034.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nVnlm-000875-Hs for emacs-orgmode@gnu.org; Sun, 20 Mar 2022 01:06:23 -0400 Received: by mail-pj1-x1034.google.com with SMTP id q1-20020a17090a4f8100b001c6575ae105so8100619pjh.0 for ; Sat, 19 Mar 2022 22:06:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version:content-transfer-encoding; bh=x7zZQJfiA7RSAJr2CXkDc75kOcZ4wt4AmW7UY06EhNI=; b=Ta4uWow7EOiMaGk+2vy1CWky1/azGPXhGbX+g/T0t6MrODSK/fC2EW5qDz1mb9ityY tz95fXFgkTpm097yfg7Mk5whz1rM4T0vpuyRInvEFcZqaM1gJMmaYgQrOSx0LB6cWsey +Eh+TdNnVqz7wcE8Cd6AP3xQ3URgEaIru2/hpX6j1zhcGjWBm2dmdetpSNGgZZeU5Odb b5qove9q7lRmYMxY7A2BXQYoXyQOiMAv+YmGIDcyaSxiwUR11j4BfDccb+zokU19a5tO uQjuGrPWO1xUxutbvluP86Jb1oek0rbensVQiWwgTGfMQ939gRkqJ906fLAfJ25sa9Y5 mw7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=x7zZQJfiA7RSAJr2CXkDc75kOcZ4wt4AmW7UY06EhNI=; b=paENkH8K29BmKp2j4GhvkAnPStErBtfB3nof/AiM8LnAnNwr4KMJCVDJO6Z3caRQ4F +vTT6Kcq/QGxXCpadX//mmZrErrdj6bFQLZ69l338xUxp3K5/snMxg2CfDoK2sImODSF OnslGPD72BqQF4hm8nUryB1Kc7lP0ujTOPupV5KrtPL7nw/+2Tr/CKZiQsZE+Fs/vph4 h1mJPpMgiB5B6hDXhW2OUCBqeuK2k2Z621lFkYJKuXya6oUAbvkGc0PI4fISSHP67X/g wwT/dnKlcEGP6jUmkWKXH6FGj8/xWJiqJ36vlt33PPfzJenKdsM7ZBiozYlPL0YMPg7G ffsQ== X-Gm-Message-State: AOAM532ZXcIQiBl9OFmSnDK1DQXGKQJnTjclVkcc2KyZDxpamuGx/56B /dbx1LYv0OfDhMo8cWcHknE= X-Google-Smtp-Source: ABdhPJw7C5dE/52AC3TZPK1s1zsBmh/oXXC3nVtlSeUcx7sHcb10IurWmtqLWtlnXdmKC1jouTwSgg== X-Received: by 2002:a17:902:bcc2:b0:14f:23c6:c8c5 with SMTP id o2-20020a170902bcc200b0014f23c6c8c5mr6933571pls.131.1647752780868; Sat, 19 Mar 2022 22:06:20 -0700 (PDT) Received: from localhost ([45.128.72.3]) by smtp.gmail.com with ESMTPSA id bh3-20020a056a02020300b00378b62df320sm11135084pgb.73.2022.03.19.22.06.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 19 Mar 2022 22:06:20 -0700 (PDT) From: Ihor Radchenko To: =?utf-8?Q?S=C3=A9bastien?= Gendre Subject: Re: How do you manage complex project with Org-mode In-Reply-To: <87czj4t6yc.fsf@k-7.ch> References: <87tuci9zp6.fsf@k-7.ch> <87h78hrdf8.fsf@gmail.com> <87czj4t6yc.fsf@k-7.ch> Date: Sun, 20 Mar 2022 13:06:48 +0800 Message-ID: <87wngpdxg7.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::1034 (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::1034; envelope-from=yantar92@gmail.com; helo=mail-pj1-x1034.google.com X-Spam_score_int: -3 X-Spam_score: -0.4 X-Spam_bar: / X-Spam_report: (-0.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, PDS_HP_HELO_NORDNS=0.659, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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: Tim Cross , emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1647752833; 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:dkim-signature; bh=x7zZQJfiA7RSAJr2CXkDc75kOcZ4wt4AmW7UY06EhNI=; b=kDoNl47yX6dJwWqBmA+fqWnNSOh74fSShtlTsxe+jFEYTkRvUMr0JSgETjLI1P8WpE0U6S 8I6gXCJLpVFb3nbqDsQf1Qg9kmNLxhpN0pElP3tRKn/zcflS+kk1JEEu/9sqz5J1UMTe0v jMAziBXL1MKCqnJwkzcufMhMbczPb+rA3E3xj1vZmCgPpNhR2t3H6vVca9GPpd+E40p/Oa kYdl9bT8fm3qH/8SHi0UC+v70Y/S6cWBeWuL/4MQj+B0NeTozEgbxvzRoXoFF/rxrcKguh wOVWsxHfx3mZd9KgDEQ8ZHf1D0JA3+4uGArILCmsUu7PlXY8hEjfiSsCS6dIqw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1647752833; a=rsa-sha256; cv=none; b=U/J7pkq8QLtyK2rO9idkyRlwFXgWFWCJxaH97h3txscgH+F98n/2aG6kBfDfbU4FCjzcF9 bjKYUKJwd9xH67/7jqbtpxtAZN+Qv2xACPzqoxh5eEEJnS4vgzec8MKexpn+XhO4m7lLpZ RUqi+2RVjsbWFGOqq7TIVmB2B8bAZXqN/2SQ5RFb/WZHmhJeZBnR/fel+D8XJV2tlj452f v99bOOBMMiTjWMAAw7kPABCr4tX6YdXd8r9TKlIl9ov4Xi+ug8J51vGsakG1k4EFK5HAAX 8ielJRQ9z1x5epYx4hkJpt+/Pkhi8Bv93QyyH5swPOfOgG1Tl5JdO51CpnPrlA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Ta4uWow7; dmarc=pass (policy=none) header.from=gmail.com; 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: -7.13 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Ta4uWow7; dmarc=pass (policy=none) header.from=gmail.com; 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: F3484A684 X-Spam-Score: -7.13 X-Migadu-Scanner: scn0.migadu.com X-TUID: /Jzp52mTaqtq S=C3=A9bastien Gendre writes: > 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 I think that your existing system is already a good starting point. I would not recommend changing it drastically. Every possible time management workflow must be based on existing workflow habits (like daily inbox review) and only introduce new habits one by one and slowly. For your specific situation with many simultaneous important projects, you are not alone. Every student meets similar issue. My recommendations for managing multiple projects: 1. Similar to daily inbox review, do weekly/bi-weekly project progress review. You are already doing this. However, I am not sure about the details. When doing project review, I find it useful to create a custom agenda listing all the ongoing projects. Every time I review the project list, I select up to 3 projects I plan to work on from now till the next project review. All other projects are marked "HOLD" and their tasks will never be listed in agenda (unless there is some hard deadline or unskippable meeting). Review is the time when you decide which projects to sacrifice if you have insufficient time. Coming back to those HOLD projects after the review time is a no-no, unless you complete the planned projects and still have remaining time. 2. If you cannot complete a project within initially planned time, it may be tempting to continue until completion. Do not do this. It is better to try finishing the other planned project work first and come back to the partially completed projects if time permits. In Org, there are several tools you can use to address this: - You may dedicate each single day to no more than a single project. The project tasks will be scheduled to specific days and you can create a custom agenda that does not show tasks scheduled in past days. - You may use effort estimates for projects/tasks shorter than a day + non-nil org-clock-sound. If you create a habit to clock-in regularly, Emacs will play a sound when you run out of time. - You may create a rule to have at least a single easy 2-3 min task as "entry" point to a project you plan to switch to. Having a simple task really makes it easier to switch from working on current and already familiar project to other one. *This rule sounds obvious and simple, but I cannot stress more how much it changed my workflow once I got to follow this regularly* =20=20=20 The above suggestions are simple to list and somewhat obvious, but not-so-easy to master. It is important to stick to them as much as possible until they become a habit. They may take months to master. > To manage school big work, I think of managing them as projects. > > I want to apply a simple "Project" workflow: > > * Each project is a headline with the status "PROJECT" > * Each project have the deadline defined by the school work deadline > * Each project have a complete description with every info needed to work > * Each project have one or many tasks (as sub headlines with a status) > * Each task have a importance, time and effort estimation > * Each task have its own deadline, distributed along the remaining time > * When I set a task deadline, I look at its estimations and also other pr= ojects tasks > * To create a new project, I use Org-capture with a template Just one comment. If you tend to have a large number of tasks in your agenda, you are likely overusing deadlines and scheduling. I would avoid setting deadlines for every single task. Too long agenda lists are *counterproductive* in many ways. I recommend scheduling the whole project (or subproject, it the main project is huge) + 1-2 individual tasks. When you complete the 1-2 individual tasks, it is more productive to look inside the project, and select next tasks depending on the new results from the first tasks. Hope my comments are useful. Best, Ihor