emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Francesco Pizzolante
Cc: mailing-list-org-mode <public-emacs-orgmode-mXXj517/zsQ@hugh.gmane.org>
Subject: Re: Time computation errors
Date: Wed, 08 Apr 2009 10:48:55 -0400	[thread overview]
Message-ID: <87zler2obs.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: ur603skvy.fsf@missioncriticalit.com

"Francesco Pizzolante"
<fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org> writes:

> Bernt Hansen wrote:
>> I'm not sure what the answer to this is.  I use the clocking features to
>> summarize time spent working on tasks in clock reports only and I've
>> never had the need to deal with negative values or summing clocked
>> values manually in a table.
>> Maybe other users have experience with summing times in tables outside
>> of clock reports?
> On example could be to determine the difference between the
> estimated effort and the time really spent. You would
> necessarily end up with negative durations (supposing that some
> asks took less time than the estimated effort).
> Does it make sense?

I don't personally use the clocking information like that.  I just make
3 columns - one for the quoted time (estimated effort) I sent to the
customer, one for the estimated effort which may changed during work on
the project and one for clocked time side by side.

I also snapshot the estimate for the project before starting work with 
C-c C-x i.  This gives me a local subtree table that looks something
like this:

#+BEGIN: columnview :hlines 1 :id local
| Task                             | Quoted | Estimated | CLOCKSUM |
| * PROJECT Some Project           |        |      0:40 |     1:40 |
| ** Details (not a todo item)     |        |           |          |
| *** More details                 |        |           |          |
| ** DONE Task to be done          |        |      0:10 |     0:27 |
| ** DONE Review project materials |        |      0:30 |     1:13 |
| *** DONE Review document         |        |           |     1:13 |

It's pretty obvious to me when they don't match.

The actual number of minutes they're off by isn't important to me since
the effort estimate is normally a rough guess anyway and clocking is
exact (to the minute).  Doing a difference on these two columns doesn't
really make sense to me.

When comparing clocked time to estimates I'm more interested in
  - this task was overestimated alot
  - this task was underestimated alot


  reply	other threads:[~2009-04-08 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 12:29 Time computation errors Francesco Pizzolante
2009-04-07 13:24 ` Bernt Hansen
     [not found]   ` <87skkktx4n.fsf-EZCVE/ZCkfKiJtKbxSCZYZ53EReGIhmS@public.gmane.org>
2009-04-07 14:12     ` Francesco Pizzolante
2009-04-07 15:32       ` Bernt Hansen
     [not found]         ` <87d4botr7v.fsf-EZCVE/ZCkfKiJtKbxSCZYZ53EReGIhmS@public.gmane.org>
2009-04-08  6:46           ` Francesco Pizzolante
2009-04-08 14:48             ` Bernt Hansen [this message]
2009-04-07 22:37 ` Daniel Clemente

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:

  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=87zler2obs.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=public-emacs-orgmode-mXXj517/zsQ@hugh.gmane.org \
    --cc=public-fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@hugh.gmane.org \


* 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


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).