Calendars (how to add weekends) ?

[Rodney]

I am trying to create a new base calendar that utilizes 365 days a year.
I need to show calendar days for my projects, not just working days.
When I try to change the calendar by holding down the SHIFT key and
selecting 'S' & 'S' for Sat. & Sun., it changes everything EXCEPT JUNE 1999
thru JULY 2005 Saturdays & Sundays !!!

Why is this happening?
How Can I create a 365 day project calendar ????

Sincerly,
ASAP

 

[Steve House [Project MVP]]

It works for me using Project 2003. In Tools, ChangeWorkingTime for the
calendar of interest click the Sat and Sun column heading. Select the
"Non-default Working Time" radio button and it will make all Sat and Sun
past and future into working days. (Selecting the Use Default radio button
makes them non-working days since that's the default calendar.)

That being said, are you really really sure you want to do that? Making
them working days in the calendar says that if a task starts on Monday and
takes 15 days of work to complete, the resource doing it isn't going to have
a day off for those 15 days until its done. Remember, the WBS isn't fully
decomposed until its down the the level of one task equals the work done by
one resource. The project schedule is a description of all the individual
assignments each worker on the project is going to do and exactly when they
are supposed to take place. A task requires 30 days of work? The poor
schnook or team you put on it will have to go for a solid month without a
day off. I doubt that is an accurate description of reality, most people
get a couple of days off a week and work doesn't proceed on their tasks
while they're not on the property. A task requiring 120 man-hours of effort
will really take 3 weeks to complete, not the 2 weeks plus a day your method
would show it at. As a result, doing it your way is going to show the
project ending far sooner than it actually will in reality, not exactly a
career enhancer.

 

[Rodney]

Steve thanks for the input, Our group is really not using "Project" to its'
full potential, rather they have asked me to create a quick & dirty schedule
of say... 18 to 25 projects that are in the works. These project have not
been final designed yet, and or have not been bid to construct, but in the
mean time we need some sort of monitoring tool to indicate that we may need
to staff up if projects hapen to get cut loose earlier than expected or
others may run into snags.

Basically each project is represented by one bar, for example a duration of
420 days needs to be calendar days, not working days.

We are barely scratching the surface of the software for our intended use.