Pages

Search

How do I change the duration from hours to days Microsoft Project

How do I change the duration from hours to days Microsoft Project

How do I change the duration from hours to days

Posted: 10 Aug 2004 11:07 AM PDT

That macro does not appear in the drop down list. Do you know if I can
download it somewhere? Thanks for your response.

"JulieS" wrote:
 

replacing resources across multiple tasks and projects

Posted: 10 Aug 2004 10:12 AM PDT

This is one excellent use of the Resource Assignment box. On the
standard toolbar is a tool with 2 human heads on it. Click on that,
and the Resource Assignment box appears. Select all tasks with the
resource you want to replace assigned to them (if there are a lot,
apply the "using resource" filer). Select as many of these as you can
(this will be limited by available memory, so closing other apps may
help do more at once). Select the resource's name in the Resource
Assignment box, the click on the "Replace" button. A dialog box will
appear, with the same list of resources you just had in the Resource
Assignment box. Select the resource you want to replace the other
with. Click OK.
One of the nice parts of using this method is that any partial
assignments on the original resource will be replicated for the
replacement resource.
Best of luck.

David G. Bellamy
Bellamy Consulting

"Greg" <microsoft.com> wrote in message news:<387101c47efd$317dcc10$gbl>... 

Duration and finish date

Posted: 10 Aug 2004 08:43 AM PDT

Also, in addition to the other comments, you need to reflect that the 20
hours was obtained from 16 hours regular work and 4 hours overtime work.
--
Steve House [MVP]
MS Project Trainer/Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs


"Muks" <microsoft.com> wrote in message
news:com... 
resource 
which 
to 

Filtering for Critical Path of Specific Task

Posted: 10 Aug 2004 08:20 AM PDT

You have several problems. A major one, IMHO, is your use of Must Finish
On constraints for your key deliverables. A constraint in the scheduling
engine is not the same thing as a constraint in the world of your project.
You are using Must Finish On to mean "this is when we have to have this done
by or we are in deep trouble" but that's NOT what a constraint means in
Project. To Project, a "constraint" means that this task will ALWAYS be
shown happening per the constraint, even if it is physically impossible for
it do do so according to the durations and links of the preceeding tasks.
Consider task A and B, each 5 days duration, starting next Monday. That
task sequence will finish 10 days later. They lead to a finish milestone.
Simple FS links A->b->Finish. If I put a MFO constraint on the milestone of
1 September, indicating that's when the contract says we have to finish,
guess what Project shows? It shows task A running from 16 Aug to 20 Aug,
task B from 23 Aug to 27 Aug and then a gap until the milestone occurs,
scheduled on 01 Sep. But when did the milestone REALLY occur? 27 Aug!
Using the constraint caused the milestone to be shown occuring at a date
that is patently in error. So we take another tack. Let's put a Must
Finish No Later Than constraint of 01 Sep on it instead. Now Project shows
the milestone occuring 27 Aug, the correct date. But we still have a
problem. We blew it and task B was grossly under-estimated and actually
takes 10 days instead of 5. Now task B finishes on 03 Sep. But wait,
looking at our milestone it shows finishing the project 01 Sep, right on
schedule!!!!! Again, obviously an error - we CAN'T be finishing on time
because the predecessor that MUST be finished for us to really be done with
all the work actually isn't finished until 2 days later!

A second problem is the use of the term "critical path." It seems like you
are using the term to mean "the important task sequence for producing a
deliverable." But that's not it. As Project (and CPM in general) uses the
term, the critical path is the sequence of events that determines the
overall duration of the entire project. There is no such thing as a
"critical path to a deliverable" unless that particular deliverable just
happens to lie on the critical path of events to the end of the project.
There may be lots of deliverables in a project whose delay to some extent
would not result in a delay of the overall completion of the project and by
definition they are not critical. For instance, I have an application
development project that requires 1 month design, 4 months programming and
testing, and 1 month rollout. I can write the user's manual any time after
design is done because at that point the functionality is locked down and
the programmers write to the design specs. Training is a part of rollout
and I won't actually use the user's manual until we begin training. Writing
the manual is not a critical task or deliverable, even though it's really
really really important, unless it's delayed into the 6th month and the
delay causes training and thus completion of rollout to be delayed,. It is
not a critical deliverable, does not lie on the critical path, and there is
no critical path leading up to it UNLESS it gets delayed more than 4 months
from when it could have been started. At that point, its schedule becomes
the determining factor in the date of the conclusion of all the project work
and so it becomes critical and the critical path shifts to include the
sequence leading to and from it.

--
Steve House [MVP]
MS Project Trainer/Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs



"Jeff" <microsoft.com> wrote in message
news:371901c47eed$896a23c0$gbl... 

Over-allocation indicator - for specific task duration.

Posted: 09 Aug 2004 11:31 PM PDT

Hi Steve and thanks for response!

There is no importance which task was 'first' - if there is an
over-allocation on specific day - all tasks that take place in that place are
'suspicious' - and I want them to be marked (by the indicator field for
example).

My problem is to recognize onle these tasks that 'involved' in the
over-allocation.

"Steve House" wrote:
 

The 60 day trial period ended after 2 hours of use!

Posted: 09 Aug 2004 01:02 PM PDT

Could be either of a couple of things

Here is the first:
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q285/3/43.asp&NoWebContent=1

If you haven't installed previous versions as described above, then
sometimes the trail version has a hardcoded expiration date (this might
happen if you are installing off a cd). Try
http://www.microsoft.com/office/project/prodinfo/trial.mspx to see if that
will work for you.

-Jack



"johnnycrash" <microsoft.com> wrote in message
news:2f3f01c47e85$4fa8cff0$gbl... 

Linking multiple projects

Posted: 09 Aug 2004 07:25 AM PDT


Jenn,
Wow, at first I though that answer might be too obvious but it just
shows to go ya.

John
P.S. You're welcome

Copy Picture does not include Legend

Posted: 09 Aug 2004 06:02 AM PDT

Hi,

I use those Print Screen shots in my courses (PPT)

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/index.htm
32-495-300 620
"jimcal" <microsoft.com> wrote in message
news:28fb01c47e26$a8c8b780$gbl... 

Date Range Filter

Posted: 08 Aug 2004 07:31 PM PDT

Thanks for that Steve, using custom auto filters has opened up a pile of
possibilities for me.

"Steve House" wrote:
 

Timescale Macro

Posted: 08 Aug 2004 07:07 PM PDT

I'd simply assign a cost of $1 for each hour of work, then use BCWS
-Jack

"gbeav" <rr.com> wrote in message
news:234601c47db5$9628b7e0$gbl... 

Prj2002: Project more that 20yrs old?

Posted: 07 Aug 2004 08:29 PM PDT

I did a similar timeline, but I used Excel, partly because of the
reason you encountered.

"Mike" <reidrik_von(AT)hotmail.com> wrote in message news:<phx.gbl>... 

Calendar and Change Working Time (Use default)

Posted: 07 Aug 2004 10:15 AM PDT

Use set the "default" start and end times on the Tools, Options, Calendar
page. Those defaults do NOT change anything in the working times calendar
or modify its defaults. In fact, nothing on that entire page has any effect
on the working time calendar at all, contrary to what the names of the
fields appear to indicate.

Here's what it does do. First of all, make note that ALL date fields are
actually date/time fields. You may choose whether to display the times or
not but they're always going to be there. When you enter a task name and
duration, normally Project calculates its start and end date/time for you
based on the Project calendar, predecessor relationships, and resource
availability. But you may, for some particular reason, wish to set a
constraint on the task and one easy way to do it is to over-ride the
calculated start or end date with your own entry (and that's the only time
you should EVER enter something in those two columns). If you enter
something in the Start field, Project sets a Start No Earlier Than
constraint of the date you entered. But it also needs to know what time to
include in that entry as well. If you click in the Start field and select a
date from the little popup calendar, it uses your Project Calendar's working
hours to determine what time on the selected date to use. But if you
manually type in the date without explicitly including a time in your entry,
it uses whatever you've set as the "Default Start Time" on the calendar
options page.
--
Steve House [MVP]
MS Project Trainer/Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs



"Regis" <microsoft.com> wrote in message
news:com... 
when 
time. 

Out of hours start and finish

Posted: 06 Aug 2004 09:59 PM PDT

You are very welcome Maureen. It is a puzzler about the
resource calendar though.
Glad to have helped.
Julie 
assigning 
what's 
re- 
of