From: Axel Kielhorn <org-mode@axelkielhorn.de>
To: Org-Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Testers / Feedback wanted: Gantt charts via org-gantt.el
Date: Sun, 31 May 2015 15:13:19 +0200 [thread overview]
Message-ID: <A8E885FC-3E83-43AE-B21B-2EADD602DCC1@axelkielhorn.de> (raw)
In-Reply-To: <1432985621669.70644@vis.uni-stuttgart.de>
[-- Attachment #1: Type: text/plain, Size: 2707 bytes --]
> Am 30.05.2015 um 13:33 schrieb Bernhard Schmitz <Bernhard.Schmitz@vis.uni-stuttgart.de>:
>
> Hi,
>
> my org-gantt.el is now in a usable state. It creates gantt charts via pgfgantt directly from headlines in org mode, using deadlines, schedules, effort estimates and (optionally) clocked time.
Sounds like a good idea.
I tried writing pgfgantt manually but once I finished updating the chart, it was already out of date.
Getting the information from org would be fine.
I tried org-gantt on a current project and ran into one problem:
I track progress with
* Task [%]
and
* Task [/]
Of course the % causes a problem when exporting to LaTeX.
I suggest to either ignore [%] and [/] or use them as an alternative to show how much is completed.
It is probably a better metric than hours worked.
pgfgantt doesn’t handle \ganttbar commands without start and end date.
Therefor I can’t export an incomplete chart.
You may want to set the entries with missing scheduling information to the first day of the chart.
(Maybe mark the task or label with a color to indicate that they are incomplete.)
(See below for some different ideas.)
A two month chart doesn’t fit into \textwidth.
I wrapped it into a sideways environment (provided by rotating.sty), maybe a sideways option?
For a project with 2000 person hours[1] I’ll probably need a separate export and print it on A0 paper[2].
Some kind of scaling would be fine (show weeks / month instead of days).
For a huge project it may be nice to limit the levels printed:
Just Module 1 - 8 for the Management and each Module with the submodules for the project leader.
Similar to maxlevel in the clocktable.
I’m not sure about inheritance:
If I have a deadline for a task, should the subtasks inherit that deadline unless an explicit deadline is given?
If I have a deadline for a task and efforts for all subtasks, should the task inherit that effort?
That way I can give a deadline to the task and estimate efforts to get an initial chart.
Using this chart I can divide the subtasks between workers, rearrange the deadlines for the subtasks and finally define a scheduled date for the main task.
This gives me another idea:
Filter / color by tag.
Print only tasks tagged :Axel: to show my workload, and print tasks tagged :Sam_One: to show tasks I have delegated.
Color tasks by tags to show who is assigned, white for unassigned tasks.
Axel
[1] A 2000 PH project is not my usual project size, a few hundred is more common.
[2] I have access to an A0 printer but I usually draw with felt markers on (literal) wallpaper.
Much faster for an initial design and I can use „real“ cut and paste:-)
[-- Attachment #2: Gantt-ECM.org --]
[-- Type: application/octet-stream, Size: 3518 bytes --]
#+LANGUAGE: de-de
#+OPTIONS: toc:nil
#+OPTIONS: tags:nil
#+OPTIONS: todo:nil
#+LATEX_HEADER: \usepackage{pgfgantt}
* Module [75%]
DEADLINE: <2015-05-31 Sun>
:PROPERTIES:
:ID: gantt
:END:
** DONE Modul 1
CLOSED: [2015-05-31 Sun 11:49]
** DONE Modul 2
CLOSED: [2015-05-31 Sun 11:49]
** DONE Modul 3
CLOSED: [2015-05-31 Sun 11:49]
** DONE Modul 4
CLOSED: [2015-05-31 Sun 11:49]
** DONE Modul 5
CLOSED: [2015-05-31 Sun 11:49]
** DONE Modul 6
CLOSED: [2015-05-31 Sun 11:50]
** STARTED Modul 7 [40%] :Axel:
:LOGBOOK:
- State "STARTED" from "" [2015-05-31 Sun 11:50]
:END:
*** DONE Submodule 1
CLOSED: [2015-05-31 Sun 11:50]
:LOGBOOK:
- State "DONE" from "" [2015-05-31 Sun 11:50]
:END:
*** DONE Submodule 2
CLOSED: [2015-05-31 Sun 11:50]
:LOGBOOK:
- State "DONE" from "" [2015-05-31 Sun 11:50]
:END:
:PROPERTIES:
:Effort: 40:00
:END:
:PROPERTIES:
:Effort: 0:10
:END:
*** STARTED Submodule 3 [3/4]
:LOGBOOK:
- State "STARTED" from "" [2015-05-31 Sun 11:50]
:END:
:CLOCK:
CLOCK: [2015-05-31 Sun 10:00]--[2015-05-31 Sun 14:18] => 4:18
:END:
:PROPERTIES:
:Effort: 80:00
:END:
- [X] Task 1
- [X] Task 2
- [X] Task 3
- [ ] Task 4
*** STARTED Submodule 4
:LOGBOOK:
- State "STARTED" from "" [2015-05-31 Sun 11:50]
:END:
:PROPERTIES:
:Effort: 8:00
:END:
*** TODO Submodule 5
:PROPERTIES:
:Effort: 8:00
:END:
** STARTED Modul 8 :Sam_One:
:LOGBOOK:
- State "STARTED" from "" [2015-05-31 Sun 11:50]
:END:
* Zeitplan
#+BEGIN: org-gantt-chart :id "gantt"
\begin{ganttchart}[time slot format=isodate, vgrid={*1{black},*4{dashed},*2{black}}]{2015-05-31}{2015-05-31}
\gantttitlecalendar{year, month=name, day}\\
\ganttgroup[group left shift=1.5604166666666666, group right shift=-0.0]{Module [75%]}{}{2015-05-31}\\% -- 5d 17:00 -(0d 17:00)- -- 2015-05-31,08:00
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Modul 1}{}{}\\% -- --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Modul 2}{}{}\\% -- --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Modul 3}{}{}\\% -- --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Modul 4}{}{}\\% -- --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Modul 5}{}{}\\% -- --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Modul 6}{}{}\\% -- --
\ganttgroup[group left shift=1.5604166666666666, group right shift=0.5604166666666666]{Modul 7 [40%]}{}{}\\% -- -(0d 12:29)- --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Submodule 1}{}{}\\% -- --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Submodule 2}{}{}\\% -- 1d 17:00 --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Submodule 3 [3/4]}{}{}\\% -- 3d 09:00 -(0d 09:00)- --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Submodule 4}{}{}\\% -- 0d 09:00 --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Submodule 5}{}{}\\% -- 0d 09:00 --
\ganttbar[bar left shift=1.5604166666666666, bar right shift=0.5604166666666666]{Modul 8}{}{}\\% -- --
\end{ganttchart}
#+END:
[-- Attachment #3: Type: text/plain, Size: 2 bytes --]
next prev parent reply other threads:[~2015-05-31 13:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 11:33 Testers / Feedback wanted: Gantt charts via org-gantt.el Bernhard Schmitz
2015-05-31 13:13 ` Axel Kielhorn [this message]
2015-06-01 12:51 ` Bernhard Schmitz
2015-06-01 15:26 ` Axel Kielhorn
2015-06-01 18:38 ` Axel Kielhorn
2015-06-02 8:42 ` Bernhard Schmitz
2015-06-01 11:16 ` Karl Voit
2015-06-02 8:15 ` Bernhard Schmitz
2015-06-03 15:13 ` Karl Voit
2015-06-02 8:38 ` Eric S Fraga
2015-06-03 15:17 ` Karl Voit
2015-06-05 8:20 ` Bernhard Schmitz
2015-06-20 12:46 ` Bernhard Schmitz
2015-06-25 8:04 ` Eric S Fraga
2015-11-09 15:02 ` Karl Voit
2015-08-05 0:00 ` Bastien Guerry
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A8E885FC-3E83-43AE-B21B-2EADD602DCC1@axelkielhorn.de \
--to=org-mode@axelkielhorn.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.