From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id qE7gMtskHmIaWwAAgWs5BA (envelope-from ) for ; Tue, 01 Mar 2022 14:51:23 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id aOlWL9skHmLFRgAAauVa8A (envelope-from ) for ; Tue, 01 Mar 2022 14:51:23 +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 38E8742271 for ; Tue, 1 Mar 2022 14:51:23 +0100 (CET) Received: from localhost ([::1]:43624 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nP2uQ-0002oU-A7 for larch@yhetil.org; Tue, 01 Mar 2022 08:51:22 -0500 Received: from eggs.gnu.org ([209.51.188.92]:59238) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nP2sK-0002aP-T6 for emacs-orgmode@gnu.org; Tue, 01 Mar 2022 08:49:14 -0500 Received: from [2607:f8b0:4864:20::531] (port=42766 helo=mail-pg1-x531.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nP2sI-0007rD-ID for emacs-orgmode@gnu.org; Tue, 01 Mar 2022 08:49:12 -0500 Received: by mail-pg1-x531.google.com with SMTP id o8so14444810pgf.9 for ; Tue, 01 Mar 2022 05:49:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:user-agent:from:to:cc:subject:date:in-reply-to :message-id:mime-version:content-transfer-encoding; bh=TzWkz0fDbahJ20vJ3Qlr8MT99EwwYRQHq01dSQEIxOE=; b=QrVt08GQa9DA7enBddZwqbOvvzHBoJTe+2L5af809ZYMzT5bW3KAIc0DTN3uTD8Sbf Bm2ewpH9AwEp53yAIM5e7TzNSL3xSq5+pBPMYu1qguzzcWxB/fYDnGZgV7VAFYjgz1Bk gCuHfzpgSpxTYH34f1Cz6KYR9Q4kjUaMI2n0SQEpCbXRTKiy5U8ZcGsLyjWU1GHVTF66 d78iTfD6XR789s1rfxvLCrIGA3AkxKutpuhg3U4Si//evrtWT0Xi43OzBZQF5vtd7qEa MYErC334N10XquOaudjzJIMCp1us/+0RJbYPNoOLZy7/YoXJHD4LwoeHZoM7iRnBJXtS Vx+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:references:user-agent:from:to:cc:subject:date :in-reply-to:message-id:mime-version:content-transfer-encoding; bh=TzWkz0fDbahJ20vJ3Qlr8MT99EwwYRQHq01dSQEIxOE=; b=0bZ2Wk4wfjktyDZsd0v0dr/8iaHsHECh/xkz0ld9YJ0dxnvlDSRfiv64eu9XHPB0LI ytA9tq0VhzHZPbidLMWQwVVJrXDBxH5hNohPbtYb7tk/vAqDqIXhwDt9f35HQrNQnbre 6cxBzXqsEFTVzlTizcYxoG7mV/bT2sgKKN1SCbaZbYtQXVAwZ2vff6uWNplA5K8+zo8Y tMDSzCuZU0yW3nq8mNGnrIoSwGwsoBXjajMj+Akv7K4KxWWORbW+PBl5yrsuAeKbDl31 a7TRv94r1CWAqKH7MuWbYu9Vm3Dw4bJKmoMwEIma8EVrSrZ/Y6G4/AWhaKUX1kZ4f1uz mvog== X-Gm-Message-State: AOAM531ovdbP9pIbdW+Y2KuIWjnkVkltHORuWn+cow/Rbw8HmxhcBQfT nLKW/ZJ/W+TonBXuwsdT0HkDMlpPZZY= X-Google-Smtp-Source: ABdhPJyH5h8dl7S4OXAypg2dgJszhZvFGKu9dUQixoF1zIUntARzhW2Vb0pICHrLXnhtrsmJjYWJdw== X-Received: by 2002:a05:6a00:238a:b0:4f3:fbf3:e611 with SMTP id f10-20020a056a00238a00b004f3fbf3e611mr14294762pfc.11.1646142548272; Tue, 01 Mar 2022 05:49:08 -0800 (PST) Received: from dingbat (106-69-94-169.dyn.iinet.net.au. [106.69.94.169]) by smtp.gmail.com with ESMTPSA id w16-20020a056a0014d000b004e12fd48047sm18640282pfu.35.2022.03.01.05.49.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 01 Mar 2022 05:49:07 -0800 (PST) References: <87tuci9zp6.fsf@k-7.ch> User-agent: mu4e 1.7.9; emacs 28.0.50 From: Tim Cross To: =?utf-8?Q?S=C3=A9bastien?= Gendre Subject: Re: How do you manage complex project with Org-mode Date: Tue, 01 Mar 2022 18:12:06 +1100 In-reply-to: <87tuci9zp6.fsf@k-7.ch> Message-ID: <87h78hrdf8.fsf@gmail.com> 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::531 (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::531; envelope-from=theophilusx@gmail.com; helo=mail-pg1-x531.google.com X-Spam_score_int: 9 X-Spam_score: 0.9 X-Spam_bar: / X-Spam_report: (0.9 / 5.0 requ) BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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: 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=1646142683; 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=TzWkz0fDbahJ20vJ3Qlr8MT99EwwYRQHq01dSQEIxOE=; b=cEQs8WVFWkYe9HyntEgWev6nJf9Esavog+rWEOWB2QjbqRRhIaN22J8IKAEks9T7guMVsS L26MwH1E3NjF3BoJpzo6Io/vucM8eOIZMlXonZHZtAoc+aL7OttpjsT/KrYmQlD5Iu+PM5 zltl7qj3eattvBGcv3uazIMi7USZ/kcX56RCB9yJCp6J9ZOeGL/Mhftbm5mbHA3I95Djqa MUT8UF/LWHtuWy3lfKUMXZzUHls8hBQfId3Phq+kFmH3ZryEJiZ0pbyhQezP7cHUZZBQa0 IHqeYLO0CI6SDXTJQDocSSmzOlXePKLwao8lpy7NypC/JnKM0k38xbpXJqyEZg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1646142683; a=rsa-sha256; cv=none; b=MKeoha1qWQkquBVoQzpllXwp34iGMBl7M8805Y6O81ZHaiNrWa43e6Cj1ENc+Xp9OHbCSh OwHf6AlyA+gIdWBY1RKGJ8AcJOYbNllWFRN6YNZoGIEpX61wgaOZzbSf9AJsUj66/TfJZy P/eaeByObH4oEPHGtKb/5RMnZjW0yW7NyMg0AgM3d7IrDoOGO9Mi98sljHdcg3EQWMg+7K j7yVSMdhr5XXOeCcrpydGuOKBW8oqjKusLqfs6EI+p6SPUoiQ8brLcyYm6wwrWGjgGr5Hk BBQR1IfvU7wI3u+wHQ93fwFbSAdahd3CcZQgiBfawCXNRn4w4YfGiGFiB/gViA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=QrVt08GQ; 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: -4.29 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=QrVt08GQ; 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: 38E8742271 X-Spam-Score: -4.29 X-Migadu-Scanner: scn1.migadu.com X-TUID: ZqRBjNwTofPc 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. > I think it is the correct place. This is a list for general org mode discussions. Such discussions can be technical or about how to use org mode. > 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. > The first thing I would say is that org mode is NOT going to solve your problems of too many tasks with competing priorities in too short a time period or mitigate the impact from missed deadlines etc. In fact, no project management software can do this. Org mode is merely a tool which can help you manage tasks, deadlines, schedules, priorities and project information. It can help you track your tasks so fewer are overlooked/forgotten, it can help you manage your deadlines and scheduling of time and it can help you manage priorities and provide you with an overview of things that can alert you to issues earlier, allowing for a wider range of mitigation strategies. However, it is just a tool and how well you use that tool will come down to experience and self discipline. > 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 > That list is almost an exact match for the job criteria on the last job I applied for, which highlights the point these are individual skills which need to be learned, primarily through experience and not something which can be solved by a software tool. Such tools can help ensure things don't fall through the gaps during busy stressful projects, can help you assess how much work needs to be done and where corners will need to be cut or deadlines changed, scope reduced or quality decreased. At some point, you have to make a call as to what you will manage in your org-mode files. Too much or too detailed and too much time will be spent gathering and managing the data. Too little or insufficient detail and decisions on what has to be sacrificed are likely to be misguided or wrong. Unfortunately, there is no formula to calculate this. It will depend on the environment, types of projects and individual experience and preferences. The key to using org mode to manage projects is largely about incremental refinement. You start by defining a plan on how to use org mode, you then implement that plan and start using it. You then review how well it is working at some point and take the experience to that point, both positive and negative, into a new cycle, starting with a new plan (refined plan), implement, use review and continue this cycle (probably indefinitely, but likely with longer cycles). In general, I would recommend the following - Start simple. Don't try to do everything all at once. Org is extremely flexible with a lot of built-in functionality. Trying to use all of it all at once is likely going to make it a burden rather than an aid. - Start with a default org-mode configuration. A mistake I've seen people make many times is to immediately start by configuring new and complicated TODO states or complicated capture templates or extensive tag hierarchies and complex priority levels. Avoid the temptation to over engineer your requirements. Use the default configuration for a time and then evaluate things and decide where to make some small changes. - Don't let the tail wag the dog. Remember, org mode is there to make your life easier. If you find your now spending all your time trying to capture tasks, set priorities, clock in/out of tasks, fill in capture templates etc, your doing it wrong. Org mode should be saving you time, not consuming it. - Be broad in your research. When trying to develop a better way to manage your projects/workflow/tasks, don't just look at how people do it in org. Look at more general solutions and then see how org can be used to support whatever approach you want to use. For example, many people like the Getting Things Done (GTD) approach, others prefer an approach based on Agile project management methodologies and others use org mode based on a PRINC2 PM model. - Don't try to put all your projects into org at once. Pick a project and use org to manage it. This will be your initial test case. The project which will help you learn about org mode and apply your project management sills using org mode as your primary management tool. My own approach is probably best described as a hybrid or maybe Frankenstein model. I have cherry picked bits from various approaches to come up with something that works for me. It probably wouldn't work for anyone else, but I find it has improved my ability to get projects done, to track the critical information associated with a project and reduce the number of tasks I overlook or forget. It took me a while to get to this point and there were a fair number of mistakes made on the way. Many of my original tweaks and configuration changes have been removed and my setup is probably closer to a default configuration than it ever has been before. The main objectives for my own configuration were - Make it easy to capture information and deal with it later. When your working on a task, other things will intrude and work to distract you. I try to minimise these by having a minimal set of capture templates which will allow me to capture some bit of information, some random, but possibly important idea, some phone call from a client, a task my wife wants done etc., which will be captured into a file which I will go through later. This allows me to get back to what I'm trying to focus on with minimal distraction. - Keep active tasks to a minimum. There is no point having a task list with hundreds of entries to select from when your trying to decide what to do next. So many tasks will cause stress and make it difficult to decide which tasks should be worked on next. I treat my list of tasks in a TODO state as my backlog of tasks. Many of them will probably never be acted upon. Every fortnight or so, I will go through the list and flag some as 'NEXT' tasks. The aim is to ensure there are sufficient STARTED and NEXT tasks to keep me fully allocated for the next 'sprint'. When I start a task, its state moves from NEXT to STARTED. It will then transition to DONE, DELEGATED, HOLD or CANCELLED as necessary. Only tasks wiht a STARTED/NEXT/HOLD state appear in my agenda. Typically, there are never more than 10 tasks in a STARTED/NEXT state. - When working, I use a pmodoro approach. I work in 20 - 40 minute periods with a 5 minute break between periods and a 15 minute break after every 3 or 4 periods. During a period, I will not respond to or read email, will not answer the phone and will pretty much ignore everything except the task I'm working on. - I always check in and check out when I'm working on a task. This is partially because I want to track where I'm spending time, but mainly to help me improve my effort estimation skills. The ability to make accurate effort estimations is an important skill, but one which is hard to develop. Comparing effort estimates with actual completion effort can help improve effort estimate reliability. - I tend to only use SCHEDULED times for things which have a definite scheduled time (like a meeting) and only use DEADLINE when there is a real and definite deadline. I sometimes use priorities, but not often and only use the standard #A, #B and #C. I don't see the point in having more than 3 levels of priority.