emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Milan Zamazal <pdm@zamazal.org>
To: emacs-orgmode@gnu.org
Subject: Re: How do you manage complex project with Org-mode
Date: Tue, 01 Mar 2022 22:06:55 +0100	[thread overview]
Message-ID: <87lextgz68.fsf@zamazal.org> (raw)
In-Reply-To: <87tuci9zp6.fsf@k-7.ch>

>>>>> "SG" == Sébastien Gendre <seb@k-7.ch> writes:

    SG> But, as a student, I regularly have big and important projects
    SG> to do for the school. The kind of project who need several days
    SG> to be done, with deadlines too soon, and if you fail one them
    SG> the consequences can be disastrous. And generally, I have to
    SG> many of these project in the same time and not enough time to do
    SG> all the work. So, I also need to follow the progress of each
    SG> project to choose which is sufficiently advanced to be stop for
    SG> the benefit of another less advanced project.

    SG> And I don't know how to manage this kind of projects with
    SG> Org-mode. How to do it, without failing a 6 days project because
    SG> I spent to much time on something else and I have only 3 days
    SG> left with 3 half-day important appointment I cannot cancel. I
    SG> can't risk failing a single one of these project by trying. So,
    SG> when I am in a period with a lot of these projects, I stop using
    SG> Org-mode and concentrate on doing these project as fast as I
    SG> can. And because I often have this kind of project, I spend most
    SG> of the year without being able to use Org-mode.

Hi, I’d join the suggestion to keep things simple in the beginning.  My
task flow is different from yours but in order not to miss really
important things, I use the following:

- Deadlines, with longer in-advance warnings when needed (e.g. “-3w” in
  DEADLINE).

- I use priority A for and only for stuff that is on risk of really bad
  consequences if not handled ASAP.  And I schedule such stuff to a
  future date if it doesn’t make sense to work on it now for any reason.

As for progress, I’d say that if you don’t know how far are you with
your short-term tasks and which of them require attention currently then
you might have a problem with your workflow.  Maybe you are too
overloaded or you don’t split your time among the tasks appropriately.
Org mode is a good tool to implement support for different workflows but
cannot help if a used workflow doesn’t work very well for you.  Again,
starting simple with Org mode and paying attention first to how you work
and how it could be improved generally might be a good idea (and a
life-long process for many of us).

Regards,
Milan



  parent reply	other threads:[~2022-03-01 21:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  1:43 Sébastien Gendre
2022-03-01  4:03 ` Matt
2022-03-02 19:44   ` Sébastien Gendre
2022-03-01  6:43 ` Dr. Arne Babenhauserheide
2022-03-02 20:00   ` Sébastien Gendre
2022-03-01  7:12 ` Tim Cross
2022-03-02 20:33   ` Sébastien Gendre
2022-03-02 21:55     ` Tim Cross
2022-03-20  5:16       ` Ihor Radchenko
2022-03-20 21:24         ` Tim Cross
2022-03-21  9:25           ` Ihor Radchenko
2022-03-20  5:06     ` Ihor Radchenko
2022-03-01 19:26 ` Antonio Carlos Padoan Junior
2022-03-02 20:53   ` Sébastien Gendre
2022-03-01 21:06 ` Milan Zamazal [this message]
2022-03-02 20:58   ` Sébastien Gendre
2022-03-02 16:29 ` Quiliro Ordóñez
2022-03-02 21:05   ` Sébastien Gendre
2022-03-01  4:38 Eric Abrahamsen
2022-03-02 21:26 ` Sébastien Gendre
2022-03-02 23:35   ` Eric Abrahamsen

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=87lextgz68.fsf@zamazal.org \
    --to=pdm@zamazal.org \
    --cc=emacs-orgmode@gnu.org \
    /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).