RE: One person multiple tasks (newbie)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks everybody for your prompt feedback.

The suggestion about a daily recurring task sounds good, except that it's a
pain when my employee fills out the PWA timesheet. She'll see a huge list of
copies of the daily task (one for each work day), and she'll have to pick the
correct one for that day to enter her time into. But maybe this is the best
I can do.

The bill/nonbill calendars suggestion is interesting. I don't understand it
completely but I'll experiment and see what I can accomplish. Sometimes a
pointer to the right strategy is all you need.

Mike

"Mike Gilbert" wrote:

Hi,

This question relates to Project Pro 2007/Project Server 2007/PWA.

I have a working mom who works a total of 30 hours/week, with different
hours each day. I've set up a resource calendar for her; so far so good.

Her primary job is billable work for a customer; the current contract totals
a fixed number of hours (say 3000), so when those hours have been expended
the job is done. If it helps I know about how many months the work should
take, but it's really more of an effort driven job.

Now for the wrinkle. For every day that she puts any time into this project
at all, there's 1 hour of non-billable overhead time.

So what I would like levelling to do is:
- Allocate the first hour each day to the non-billable task
- Allocate the remainder each day to the billable task

I can almost pre-plan this in a spreadsheet and import it, but I'd like the
future plan (the end date) to adjust automatically if she takes vacation
time, works a weekend, or whatever.

I can almost do this with allocating a percent of her time to each task, but
that doesn't work because her schedule varies daily. For example if I
allocate 25% of her time that would come out to 1 hour on days she works 4
hours, but it would incorrectly allocate 2 hours on days she works 8 hours.

I thought task priority (schedule the non billable at 5 hours/week as a high
priority recurring task) might do it. That's close, but it puts all 5 hours
on Monday each week instead of spreading them out at one hour each day.

I plan to have her use PWA timesheets to record her time, so we can both see
how close she is to the 3000 hours. It would be nice if the PWA plan
suggested a "normal" week, so she could just move plan to actual unless she
had some sick time or something.

How can I make Project understand these scheduling requirements so levelling
will do the right thing?

Ideally somebody will tell me a way to make Project do exactly what I want.
If I can't get Project to handle this perfectly, what would you do as a
"close enough" practical solution to track this sort of contract in Project?

Thanks,
Mike
.

Relevant Pages

  • Re: Populating an IDentity and and timestamp field?
    ... Thanks for the recommenations. ... My plan was to create archive tables that were a superset of the original ... Similar to John H's suggestion, I had already started to think that The ... to populate the archive tables from the live tables. ...
    (microsoft.public.sqlserver.server)
  • Re: How to use relative period instead of actual dates?
    ... Based on your suggestion, I changed ... Plan the duration of each task with absolute dates ... and hopefully MS Project will show a proper Grantt Chart? ... Is there a way to use relative periods (days, ...
    (microsoft.public.project)
  • Re: Dumpexe.
    ... In my view that suggestion is a red ... Enquire, plan and execute ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Malcolms new book - Chapter 1 review
    ... of memory I allocate to some "reasonable" size; ... think of this as a friendly suggestion for a new and useful ... feature, not necessarily as a bug report. ...
    (comp.lang.c)